DOCSLIB.ORG

1121877957.Pdf (Escaneo De Vulnerabilidades)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
1121877957.Pdf (Escaneo De Vulnerabilidades) ESCANEO DE VULNERABILIDADES AL SERVIDOR PRINCIPAL DE LA EMPRESA CASO DE ESTUDIO JORGE LEONARDO RAMIREZ RESTREPO WILLIAMS AVILA PARDO UNIVERSIDAD NACIONAL ABIERTA Y A DISTANCIA – UNAD ESCUELA DE CIENCIAS BÁSICAS TECNOLOGÍA E INGENIERÍA ESPECIALIZACIÓN EN SEGURIDAD INFORMÁTICA SANTIAGO DE CALI 2018 1 ESCANEO DE VULNERABILIDADES AL SERVIDOR PRINCIPAL DE LA EMPRESA CASO DE ESTUDIO JORGE LEONARDO RAMIREZ RESTREPO WILLIAMS AVILA PARDO Proyecto de Grado para optar por el título: Especialista en Seguridad Informática Director Proyecto Esp. Ing. Freddy Enrique Acosta UNIVERSIDAD NACIONAL ABIERTA Y A DISTANCIA – UNAD ESCUELA DE CIENCIAS BÁSICAS TECNOLOGÍA E INGENIERÍA ESPECIALIZACIÓN EN SEGURIDAD INFORMÁTICA SANTIAGO DE CALI 2018 2 Nota de Aceptación: __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ Firma del presidente del jurado __________________________________ Firma del jurado __________________________________ Firma del jurado Santiago de Cali, 02 de mayo de 2018 3 Dedico este proyecto de grado fundamentalmente a Dios, quien en su infinita bondad y amor, me brindo la fuerza y sabiduría necesaria para cumplir una meta más en mi vida y los objetivos de este proyecto. A mi madre Tulia Elvira Pardo Rodríguez, por brindarme apoyo en cada instante de mi vida, por enseñarme los valores que necesita un hombre para salir adelante y ser una persona de bien, por darme una razón para lograr mis metas, pero más que nada, por brindarme su inmenso amor. A el señor Agustín Emilio Contreras Morales, quien en algún momento de mi vida me dijo “Tu puedes lograr todo lo que te propongas”, por confiar en mí y por enseñarme a confiar en mí, por tantos valiosos consejos a lo largo de mi vida y por ser como un padre para mí. Y por último pero no menos importante, a mí esposa Diana Carolina Arciniegas Rojas, quien me ha acompañado en mis triunfos y derrotas, en aquellas noches largas de estudio arduo, quien me brinda su amor, gracias a ella que con su compañía me permite retarme cada día, en búsqueda de alcanzar mis metas y recompensar su amor. Williams Ávila Pardo 4 Dedico este proyecto de grado principalmente a nuestro creador Dios, quien me permite vivir cada día con las mejores condiciones de salud y darme la sabiduría de tomar las mejores decisiones en cada momento. A mis padres Humberto Ramírez y Elizabeth Restrepo por su apoyo constante y comprensión en cada etapa de mi vida, educándome e inculcándome los valores necesarios para ser una persona con ética personal y profesional, quienes con su ejemplo de perseverancia y respeto han edificado quien soy hoy en día. A cada uno de los tutores de la Universidad Nacional Abierta y a Distancia en los cursos que tome a nivel de pregrado y posgrado, de cada uno de ellos tome las mejores orientaciones y conocimientos, que forjaron cada una de las bases necesarias para adquirir el conocimiento necesario, el cual hoy en día me lleva a dar desarrollo a este proyecto. Finalmente, a mi novia Eliana Julieth Sánchez Torres, por brindarme el apoyo, motivación suficiente en los momentos difíciles e impulsarme a nunca dejar atrás mis metas. Jorge Leonardo Ramírez Restrepo 5 AGRADECIMIENTOS Williams Avila Pardo y Jorge Leonardo Ramírez Restrepo agradecen a: La empresa caso de estudio por permitirnos desarrollar este proyecto en tan importante entidad, por brindarnos los recursos y disponibilidad para aplicar los conocimientos adquiridos en este programa académico. La Universidad Nacional Abierta y a Distancia por brindar educación para todos, donde desde su plataforma tecnológica y equipo docente, puso a nuestra disposición todo lo requerido para realizar un correcto desarrollo del proyecto. A tutores e Ingenieros Luis Fernando Zambrano y Salomón González quienes nos brindaron la orientación desde sus conocimientos en los cursos Proyecto de Seguridad Informática I y II respectivamente, sin sus observaciones y apoyo tutorial no hubiese sido posible desarrollar a cabalidad este proyecto. Esp. Ing. Freddy Enrique Acosta quien fue nuestro asesor de proyecto, con su orientación metodológica y su gran disponibilidad logramos cumplir todos los objetivos propuestos. De igual manera agradecemos a todas aquellas personas que de una u otra forma permitieron la realización de este proyecto. 6 TABLA DE CONTENIDO pág. GLOSARIO ............................................................................................................ 19 RESUMEN ............................................................................................................. 23 ABSTRACT ............................................................................................................ 24 INTRODUCCIÓN ................................................................................................... 25 1. DEFINICIÓN DEL PROBLEMA ..................................................................... 27 1.1. PLANTEAMIENTO DEL PROBLEMA ........................................................... 27 1.2. FORMULACIÓN DEL PROBLEMA ............................................................... 27 1.3. OBJETIVOS .................................................................................................. 28 1.3.1. Objetivo general ........................................................................................... 28 1.3.2. Objetivos específicos ................................................................................... 28 1.4. JUSTIFICACION ........................................................................................... 28 1.5. ALCANCE Y DELIMITACION DEL PROYECTO ........................................... 30 1.5.1. Alcance ........................................................................................................ 30 1.5.2. Limitaciones ................................................................................................. 30 1.6. METODOLOGIA DE INVESTIGACION ......................................................... 31 1.6.1. Unidad de análisis ........................................................................................ 31 1.6.2. Población y muestra .................................................................................... 31 1.6.2.1. Población .................................................................................................. 31 1.6.2.2. Muestra ..................................................................................................... 31 1.6.3. Estudio metodológico ................................................................................... 31 1.6.3.1. Fase 1: Identificación de las vulnerabilidades del servidor ....................... 32 1.6.3.2. Fase 2: Evaluación las vulnerabilidades del servidor y propuesta de procedimientos para mitigar las vulnerabilidades encontradas .............................. 32 1.6.4. Instrumentos de recolección de información ................................................ 32 1.6.5. Producto resultado a entregar ...................................................................... 32 7 1.6.6. Tipos de investigación ................................................................................. 32 1.6.6.1. Investigación Descriptiva .......................................................................... 33 1.6.6.2. Investigación Proyectiva ........................................................................... 33 1.6.6.3. Investigación Evaluativa ............................................................................ 33 2. MARCO REFERENCIAL ............................................................................... 34 2.1. MARCO TEORICO ........................................................................................ 34 2.1.1. Estado del arte de la seguridad informática en Colombia ............................ 34 2.1.2. Metodologías de análisis de riesgos ............................................................ 36 2.1.3. Conveniencia del escaneo de vulnerabilidades en la empresa .................... 37 2.2. MARCO CONCEPTUAL ................................................................................ 38 2.2.1. Metodología de Análisis y Gestión de Riesgos de los Sistemas de Información - MAGERIT ......................................................................................... 39 2.2.1.1. Amenazas ................................................................................................. 39 2.2.1.2. Vulnerabilidades ....................................................................................... 40 2.2.1.3. Criterios de valoración del riesgo .............................................................. 41 2.2.2. ¿Qué es el escaneo de vulnerabilidades? ................................................... 42 2.2.3. Tipos de escaneo ......................................................................................... 42 2.2.4. Herramientas más conocidas para el escaneo de vulnerabilidades ............ 43 2.3. ANTECEDENTES ......................................................................................... 44 2.4. MARCO LEGAL ............................................................................................. 46 2.4.1. Normatividad nacional.................................................................................
Load more

Recommended publications
  • Fast, Accurate, Vulnerability Assessments
    SOLUTIONS / MANAGED SECURITY / VULNERABILITY SCANNING Managed Vulnerability Scanning FAST, ACCURATE, SOLUTION VULNERABILITY ASSESSMENTS AT-A-GLANCE • Scanning options include Identify and Mitigate Vulnerabilities that OS, database, application, Threaten Compliance and host • Credentialed Patch Vulnerability scanning is a critical component of protecting any hybrid Audit Scans IT infrastructure system, especially those that need to meet strict • Host/Network FedRAMP, HIPAA, and PCI-DSS compliance requirements. Managing Discovery Scans vulnerabilities helps identify software flaws, missing patches, malware, • CIS Hardening Scans misconfigurations across operating systems, devices and applications. • Web Application Scans Knowledge is Power • Auditing and scanning DataBank’s Managed Vulnerability Scanning solution leverages for WannaCry, Spectre, Meltdown, Bash Shellshock, hundreds of configuration and compliance scanning templates to Badlock, and Shadow audit against industry benchmarks and best practices while powerful Brokers reporting and visibility tools help you to make sense of the findings. DataBank’s Managed Vulnerability Scanning helps you accomplish your goals of identifying and mitigating vulnerabilities before they become a problem. DataBank’s solution is supported by a dedicated staff of security engineers and a seasoned Chief Information Security Officer. KEY BENEFITS LAYERED DEFENSE PROACTIVE SERVICE EXPERT GUIDANCE CONTINUOUS MONITORING HOW IT WORKS ASSET VULNERABILITY VULNERABILITY VULNERABILITY DISCOVERY SCANNING ASSESSMENT
    [Show full text]
  • Circus Scam 1.9 0.5 UY Milford, Alison (Ls) Circu
    Author Title AR Book AR Interest Joyce, Melanie (Ls) Billy's Boy 1.6 0.5 MY Milford, Alison (Ls) Circus Scam 1.9 0.5 UY Milford, Alison (Ls) Circus Scam 1.9 0.5 UY Milford, Alison (Ls) Circus Scam 1.9 0.5 UY Pearson, Danny (Ls) Escape From The City 1.9 0.5 MY Pearson, Danny (Ls) Escape From The City 1.9 0.5 MY Pearson, Danny (Ls) Football Smash 1.9 0.5 MY Pearson, Danny (Ls) Football Smash 1.9 0.5 MY Pearson, Danny (Ls) Football Smash 1.9 0.5 MY Powell, Jillian (Ls) Cage Boy: Level 5 1.9 0.5 MY Gray, Kes Oi Goat!: World Book Day 2018 2 0.5 LY Hurn, Roger (Ls) Too Hot: Level 3 2 0.5 MY Thomas, Valerie Winnie Flies Again 2 0.5 LY Thomas, Valerie Winnie Flies Again 2 0.5 LY Adams, Spike T. (Ls) Evil Ink 2.1 0.5 UY Adams, Spike T. (Ls) Snap Kick 2.1 0.5 UY Clayton, David Hell-Ride Tonight! 2.1 0.5 MY Cullimore, Stan (Ls) Bubble Attack 2.1 0.5 UY Cullimore, Stan (Ls) Bubble Attack 2.1 0.5 UY Cullimore, Stan (Ls) Robert And The Werewolf 2.1 0.5 UY Cullimore, Stan (Ls) Robert And The Werewolf 2.1 0.5 UY Higson, Charlie Silverfin: The Graphic Novel 2.1 1 MY Lee, Janelle (Ls) Badu Boys Rule! 2.1 0.5 MY Orme, David Boffin Boy And The Emperor's Tomb 2.1 0.5 MY Powell, Jillian (Ls) Chip Boy 2.1 0.5 UY Tompsett, C.L.
    [Show full text]
  • How to Handle Security Flaws in an Open Source Project
    How to Handle Security Flaws in an Open Source Project Jeremy Allison / Google / Samba Team All new products use Open Source • Economics drive this. – Underlying OS is Linux (usually) or FreeBSD. • Unless you employ Linus or other notable names, you don’t have full control over what goes into your product. • You must have a process to coordinate with Open Source upstream developers in order to ship secure products. – At the very least, you need to know about vulnerabilities in the code you’re using, even if you don’t (or can’t) fix it yourself. Dealing with upstream vulnerabilities • Ensure the upstream project takes security seriously. – This is not as common as you might think – do you have a contact point if someone reports a security flaw to you ? – https://www.linuxfoundation.org/blog/2018/04/software-security-is- a-shared-responsibility/ • Even projects that do security well themselves have dependencies. – Know what is going into your storage solution. • If you get this wrong, it can be a disaster. Process, process, process • Put a process in place to handle all security reports uniformly. – Start with an email alias: [email protected] – Can be hard to do with a pure volunteer organization, but without it you’re not professional. • Ability to get Common Vulnerability and Exposure (CVE) number is essential for tracking. – Linux distributions are your friends here, their security Teams can handle this for you. • The process doesn’t have to be perfect, but it does have to be consistent. The reputation game • Use gpg encrypted email to communicate with vulnerability reporters.
    [Show full text]
  • Security Report
    PwC Weekly Security Report This is a weekly digest of security news and events from around the world. News items are summarised and web links are provided for further information. Cyber-execs: Expect a cataclysmic cyber-terror event within 2 years When it comes to the growing threats of global The findings accordingly show that 72% cyber-terrorism, the current state of security actually feel that the topic isn’t hyped within the US and the ability of organizations to enough, and that education and awareness prevent such attacks, information security is critical to foment a re-examination of executives feel deeply at risk. In fact, many the type of security technology used to expect a catastrophic incident to occur within protect both the US government and the next 24 months. private sectors. The majority of those surveyed (89%) believe that both military A survey from Thycotic, a provider of privileged and businesses need to focus more on account management (PAM) solutions, found developing capabilities to defend against that 63% of respondents feel that terrorists are terrorist-inspired cyber-attacks. capable of launching a catastrophic cyber- attack on the US, and could do so within the upcoming year. “Over two-thirds of respondents stated they did Source: http://www.infosecurity- magazine.com/news/cyberexecs- feel that terrorists were this close, and over 80 expect-a- percent agreed they could strike within two cataclysmic/http://www.symantec years,” said Nathan Wenzler, executive director .com/connec of security at Thycotic. “A consensus like this is not unusual these days, as more and more terrorist organizations have demonstrated increasing sophistication in their use of technology to communicate, social media to recruit new members, and of course, technical exploits and direct attacks against websites, corporate networks and government entities.” Even so, 92% of respondents believe that a majority of US companies either need more security or are way behind the security curve to defend against cyber-terrorism attacks.
    [Show full text]
  • Iot Vulnerabilities Easily 5
    • Babak D. Beheshti, Associate Dean of the School of Engineering and Computing Sciences at NYIT. • Clyde Bennett, Chief Healthcare Technology Strategist at Aldridge Health. • Ross Brewer, VP and MD of EMEA at LogRhythm. • Ben Desjardins, Director of Security Solutions at Radware. • Eric O'Neill, National Security Strategist at Carbon Black. • Jeff Schilling, Chief of Operations and Security at Armor. • Karl Sigler, Threat Intelligence Manager at Trustwave. • Sigurdur Stefnisson, VP of Threat Research at CYREN. • Amos Stern, CEO at Siemplify. • Ronen Yehoshua, CEO at Morphisec. ! Visit the magazine website at www.insecuremag.com Feedback and contributions: Mirko Zorz, Editor in Chief - [email protected] News: Zeljka Zorz, Managing Editor - [email protected] Marketing: Berislav Kucan, Director of Operations - [email protected] (IN)SECURE Magazine can be freely distributed in the form of the original, non-modified PDF document. Distribution of modified versions of (IN)SECURE Magazine content is prohibited without permission. ! Copyright (IN)SECURE Magazine 2016. www.insecuremag.com Are all IoT vulnerabilities easily 5. Insecure or no network pairing control op- avoidable? tions (device to device or device to net- works). Every vulnerability or privacy issue reported 6. Not testing for common code injection ex- for consumer connected home and wearable ploits. technology products since November 2015 7. The lack of transport security and encrypt- could have been easily avoided, according to ed storage including unencrypted data the Online Trust Alliance (OTA). transmission of personal and sensitive in- formation including but not limited to user OTA researchers analyzed publicly reported ID and passwords. device vulnerabilities from November 2015 8. Lacking a sustainable and supportable through July 2016, and found the most glaring plan to address vulnerabilities through the failures were attributed to: product lifecycle including the lack of soft- ware/firmware update capabilities and/or insecure and untested security patches/ 1.
    [Show full text]
  • Red Hat Insights Mitigate Risk & Proactively Manage Your Infrastructure
    Red Hat Insights Mitigate Risk & Proactively Manage Your Infrastructure William Nix Technical Product Marketing Manager Red Hat Management Business Unit Will Nix @ Red Hat Public Sector Information Systems Management ● Reduce complexity in hybrid secure environments ● Automate workflow and streamline management Red Hat Strategic Customer Engagement ● Work closely with customers like you ● Design and implement proactive solutions for some of the largest deployments in the world Red Hat Insights ● Develop service used for predictive and prescriptive analytics on infrastructure #redhat #rhsummit Insights Lab Hench-helpers The team will be assisting you during this lab. If you need assistance, grab our attention by raising your hand or calling us out by name. Chris Henderson, Insights Rules Product Manager Rex White, Insights Senior Software Engineer Summit Labs made possible by Red Hat Training Check out Red Hat’s online and classroom based labs and exams! #redhat #rhsummit LAB OBJECTIVES 1. Register SERVERA, SERVERB, SERVERC, SERVERD to Insights. 2. Login to Satellite and use Insights interface 3. USE Lab Manual PDF on Desktop for instructions or if you get lost. 4. Ask Will, Rex, or Chris for help by raising hand. 5. After registering and identifying risks in demo environment, resolve all issues leading to ZERO actions for your POD. #redhat #rhsummit ANALYZING INFRASTRUCTURE RISK RESPONSE - Are you confident that you can quickly respond when vulnerabilities strike? TOOLS - Are you comfortable that your tooling and processes will scale as your environment scales? COMPLIANCE - Are you certain that your systems are compliant with various audit requirements such as PCI, HIPAA, SOX, DISA STIG, etc? #redhat #rhsummit WHY WE BUILT A NEW PRODUCT #redhat #rhsummit COMPLEXITY IS RISK 80% Commercial application outages are caused by software failure and operational complexity.
    [Show full text]
  • Aws Guardduty Unusual Protocol
    Aws Guardduty Unusual Protocol trappeanandIneducable chronologize and Alexis isohyetal gelidlysometimes Jud while answer petting herpetologic some his hot-press shadoofs? Theodor suspiciously wive and arguing. and imbruted How snod so more! is Yigal Erik when is dead-on Aws filebeat module must use this unusual aws config notifies you visibility Select all the value from the world renowned security weekly crew accompanied by the ideal for an australian pms trying many aws guardduty unusual protocol on the findings. Josh Lefkowitz and Chris Camacho of Flashpoint join us for an interview. Ip address will be challenging because once the aws guardduty unusual protocol on the bucket from this behavior they can produce. Xray is aws guardduty unusual protocol are different than seven years old school paper, we kick it detects removeable media installed? What immediate use several for? Horusec is where open source glare that improves identification of vulnerabilities in your brother with smart one command. Special operations in firebase are important to count, and failed aws environment to be careful about bug bounty is aws guardduty unusual protocol traffic. Secrets after a function to perform automatic predictive prioritization to aws guardduty unusual protocol. Force space and resolved at the aws config managed service interface when aws guardduty unusual protocol depending on drone hardware security and five years have updates the guys in our second lieutenant in. Plus sound board really happening in aws guardduty unusual protocol for anomalies and passwords, and john discuss developer tools for each group where are stores each segment about why securing our approach. She was soundly mocked even in plain english, we have to discover haxorthematrix love stories podcast that bucket involved in aws guardduty unusual protocol depending on this.
    [Show full text]
  • The CERT Guide to Coordinated Vulnerability Disclosure
    The CERT® Guide to Coordinated Vulnerability Disclosure Allen D. Householder Garret Wassermann Art Manion Chris King August 2017 SPECIAL REPORT CMU/SEI-2017-SR-022 CERT Division Distribution Statement A: Approved for Public Release; Distribution is Unlimited http://www.sei.cmu.edu Copyright 2017 Carnegie Mellon University. All Rights Reserved. This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineer- ing Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other docu- mentation. This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100 NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. [DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution. Internal use:* Permission to reproduce this material and to prepare derivative works from this material for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works.
    [Show full text]
  • St Luke's- 192.168.9.0 Vulnerability Scanner
    St Luke's- 192.168.9.0 Vulnerability scanner Report generated by Nessus™ Thu, 05 Dec 2019 13:15:24 GMT Standard Time TABLE OF CONTENTS Hosts Executive Summary • 192.168.9.20.........................................................................................................................................................7 • 192.168.9.23.........................................................................................................................................................8 • 192.168.9.52.........................................................................................................................................................9 • 192.168.9.53.......................................................................................................................................................10 • 192.168.9.56.......................................................................................................................................................11 • 192.168.9.59.......................................................................................................................................................12 • 192.168.9.60.......................................................................................................................................................13 • 192.168.9.61.......................................................................................................................................................14 • 192.168.9.62.......................................................................................................................................................15
    [Show full text]
  • Are We Exposed? Quickly Identify New Threats
    | SOLUTION STORIES Are We Exposed? Quickly identify new threats. Respond effectively. Do you dread seeing your CEO or auditor when a new security threat or vulnerability makes the news? You know their first question will be, “Are we exposed?,” which means you’re going to SecurityCenter Continuous View™ spend the rest of your week running scans to come up with the answer. And that is just the first of many steps you need to take to reduce your risk. Prioritizing remediation and making fixes Exposure Response Capabilities across endpoints typically takes even more time; the longer it takes to answer the question, the • Active Scanning – Periodically examining longer your organization is exposed. assets to identify vulnerabilities • Agent Scanning – Instantly examine assets New threats are constantly emerging and changes to the IT environment – including new without the need for credentials endpoints with the proliferation of mobile devices and BYOD policies – make it difficult to understand where you are exposed. So you need a new way to immediately answer • Intelligent Connectors – Leveraging other the questions, “Are we exposed?” and “Where are we exposed,” so your organization can systems of record and integrations for respond more effectively. data, context and analysis • Passive Listening – Monitoring network Greater Visibility traffic in real-time provides information Traditionally, IT security and compliance scanning was something you may have done on which assets are connected to the occasionally, perhaps a few times per year or once every quarter or month to identify possible network and how they are communicating security issues, such as malware, misconfigurations or vulnerabilities. When a new threat or • Host Data – Actively monitoring host vulnerability was identified, you would need to dig through archive scan data to determine your activities and events in real time, exposure.
    [Show full text]
  • Common Vulnerability Scoring System V3.0 Examples
    Common Vulnerability Scoring System v3.0 Examples Version 1.5 September 2017 The Common Vulnerability Scoring System (CVSS) is an open framework for communicating the characteristics and severity of software vulnerabilities. CVSS consists of three metric groups: Base, Temporal, and Environmental. The Base group represents the intrinsic qualities of a vulnerability, the Temporal group reflects the characteristics of a vulnerability that change over time, and the Environmental group represents the characteristics of a vulnerability that are unique to a user's environment. The Base metrics produce a score ranging from 0.0 to 10.0, which can then be modified by scoring the Temporal and Environmental metrics. A CVSS score is also represented as a vector string, a compressed textual representation of the values used to derive the score. This document provides a collection of examples of vulnerabilities scored using CVSS v3.0. CVSS is owned and managed by FIRST.Org, Inc. (FIRST), a US-based non-profit organization, whose mission is to help computer security incident response teams across the world. FIRST reserves the right to update CVSS and this document periodically at its sole discretion. While FIRST owns all right and interest in CVSS, it licenses it to the public freely for use, subject to the conditions below. Membership in FIRST is not required to use or implement CVSS. FIRST does, however, require that any individual or entity using CVSS give proper attribution, where applicable, that CVSS is owned by FIRST and used by permission. Further, FIRST requires as a condition of use that any individual or entity which publishes scores conforms to the guidelines described in this document and provides both the score and the scoring vector so others can understand how the score was derived.
    [Show full text]
  • Incremental Threat Modelling Irene Michlin Principal Security Consultant 8-12 May, 2017
    8-12 May, 2017 Incremental Threat Modelling Irene Michlin Principal Security Consultant 8-12 May, 2017 Never try to boil an ocean Who am I • Coming from software development and architecture • 20 years as software engineer, architect, technical lead • Variety of consulting and testing work • From corporations to start-ups • Favourite engagement type – threat modelling Agenda • STRIDE – quick recap • Introducing our example • Incremental modelling walk-through • Sting in the tail • Conclusions • Q&A Threat modelling - reminder • Decompose architecture using DFDs • Search for threats using STRIDE • Rank or quantify – out of scope for today Data Flow Diagrams External Entity Process Data Flow Data Store Trust Boundary • People • Logical • RPC • Database • Process • Other component • Network • File boundary systems • Service traffic • Queue/Stack • Network • Process in • File I/O boundary memory STRIDE Threat Property Definition Spoofing Authentication Impersonating something or someone else Tampering Integrity Modifying data or code Repudiation Non-repudiation Claiming to have not performed an action Information Confidentiality Exposing information to non-authorised party Disclosure Denial of Service Availability Deny or degrade service Elevation of Privilege Authorization Gain capabilities without proper authorisation Introducing our example • Explain the existing architecture and the feature we are planning to add • Pretend that threat model for the existing part does not exist • Model new feature A very simple architecture Now pretend to forget it We are going to use a 3rd party reporting and analytics technology. They are going to host Data Warehouse (DWH) and reporting server on their infrastructure. They will give us licences to use their web-based Analytics App, which can query the reporting server.
    [Show full text]