Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Everand Logo

Welcome to Everand!

  • Discover millions of ebooks, audiobooks, and so much more with a free trial

    From $11.99/month after trial. Cancel anytime.

    Asset Attack Vectors: Building Effective Vulnerability Management Strategies to Protect Organizations
    Asset Attack Vectors: Building Effective Vulnerability Management Strategies to Protect Organizations
    Asset Attack Vectors: Building Effective Vulnerability Management Strategies to Protect Organizations
    Ebook473 pages4 hours

    Asset Attack Vectors: Building Effective Vulnerability Management Strategies to Protect Organizations

    By Morey J. Haber and Brad Hibbert

    ()

    Read preview

    About this ebook

    Build an effective vulnerability management strategy to protect your organization’s assets, applications, and data.

    Today’s network environments are dynamic, requiring multiple defenses to mitigate vulnerabilities and stop data breaches. In the modern enterprise, everything connected to the network is a target. Attack surfaces are rapidly expanding to include not only traditional servers and desktops, but also routers, printers, cameras, and other IOT devices. It doesn’t matter whether an organization uses LAN, WAN, wireless, or even a modern PAN—savvy criminals have more potential entry points than ever before. To stay ahead of these threats, IT and security leaders must be aware of exposures and understand their potential impact.

    Asset Attack Vectors will help you build a vulnerability management program designed to work in the modern threat environment. Drawing on years of combined experience, the authors detail the latest techniques for threat analysis, risk measurement, and regulatory reporting. They also outline practical service level agreements (SLAs) for vulnerability management and patch management.

    Vulnerability management needs to be more than a compliance check box; it should be the foundation of your organization’s cybersecurity strategy. Read Asset Attack Vectors to get ahead of threats and protect your organization with an effective asset protection strategy.

    What You’ll Learn

    • Create comprehensive assessment and risk identification policies and procedures
    • Implement a complete vulnerability management workflow in nine easy steps
    • Understand the implications of active, dormant, and carrier vulnerability states
    • Develop, deploy, and maintain custom and commercial vulnerability management programs
    • Discover the best strategies for vulnerability remediation, mitigation, and removal
    • Automate credentialed scans that leverage least-privilege access principles
    • Read real-world case studies that share successful strategies and reveal potential pitfalls

    Who This Book Is For

    New and intermediate security management professionals, auditors, and information technology staff looking to build an effective vulnerability management program and defend against asset based cyberattacks

    LanguageEnglish
    PublisherApress
    Release dateJun 15, 2018
    ISBN9781484236277
    Asset Attack Vectors: Building Effective Vulnerability Management Strategies to Protect Organizations

    Related to Asset Attack Vectors

    Related ebooks

    Security For You

    View More
    View More

    Related podcast episodes

    Related categories

    Reviews for Asset Attack Vectors

    0 ratings

    0 ratings0 reviews

    What did you think?

    Tap to rate

    Review must be at least 10 words

      Book preview

      Asset Attack Vectors - Morey J. Haber

      © Morey J. Haber, Brad Hibbert 2018

      Morey J. Haber and Brad HibbertAsset Attack Vectorshttps://doi.org/10.1007/978-1-4842-3627-7_1

      1. The Attack Chain

      Morey J. Haber¹  and Brad Hibbert²

      (1)

      Heathrow, Florida, USA

      (2)

      Carp, Ontario, Canada

      As highlighted in many articles, breach reports, and studies, most cyber-attacks originate from outside the organization. The Verizon Data Breach Investigations Report (DBIR) for 2018 calculates this at 73%. While the specific tactics may vary, the stages of an external attack follow a predictable flow. This is illustrated in Figure 1-1.

      ../images/465640_1_En_1_Chapter/465640_1_En_1_Fig1_HTML.png

      Figure 1-1

      Cyber security attack chain

      First, threat actors attack the perimeter .

      Threat actors are less likely in a modern environment to penetrate the perimeter directly, but more than likely they execute a successful drive-by download or launch a phishing attack to compromise a user’s system and establish a foothold inside the network. They do this all the while flying under the radar of many traditional security defenses. (This assumes they did not penetrate the environment due to a misconfiguration of a resource on-premise or in the cloud.)

      Next, hackers establish a connection .

      Unless it’s ransomware or self-contained malware, the attacker quickly establishes a connection to a command and control (C&C) server to download toolkits, additional payloads, and to receive additional instructions.

      Social attacks were utilized in 43% of all breaches in the 2017 Verizon Data Investigations Report dataset. Almost all phishing attacks that led to a breach were followed by some form of malware, and 28% of phishing breaches were targeted. Phishing is the most common social tactic in the Verizon DBIR dataset (93% of social incidents).

      Now inside the network , the attacker goes to work.

      Attackers begin to learn about the network, the layout, and the assets. They begin to move laterally to other systems and look for opportunities to collect additional credentials, find other vulnerable systems, exploit resources, or upgrade privileges so they continue to compromise applications and data. Note that an insider can either become an attacker just by exploiting unpatched vulnerabilities already present within an environment. In 2018 the DBIR reports this occurs 28% of the time.

      Mission Complete .

      Last, the attacker collects, packages, and eventually exfiltrates the data.

      One product will certainly not provide the protection you need against all stages of an attack. And while some new and innovative solutions will help protect against, or detect, the initial infection, they are not guaranteed to stop 100% of malicious activity. In fact, it’s not a matter of if, but a matter of when you will be successfully breached. You still need to do the basics – firewalls, endpoint AV, and threat detection and so on. But you also need to identify and patch vulnerabilities throughout the environment. Properly managing these risks can help at all stages of the attack. From reducing the attack surface to protecting against lateral movement, to detecting breach progress, to actively responding and mitigating the impact of that breach, this book will examine how vulnerabilities, exploits, and remediation strategies can block progress for a threat actor through the cyber-attack chain.

      © Morey J. Haber, Brad Hibbert 2018

      Morey J. Haber and Brad HibbertAsset Attack Vectorshttps://doi.org/10.1007/978-1-4842-3627-7_2

      2. The Vulnerability Landscape

      Morey J. Haber¹  and Brad Hibbert²

      (1)

      Heathrow, Florida, USA

      (2)

      Carp, Ontario, Canada

      A vulnerability is the quality or state of being exposed to the possibility of an attack, degradation, or harm, either physically, electronically, or emotionally. While the first two translate easily into cyber security, emotion vulnerabilities can manifest themselves in hacktivism, nation-state attacks, and even cyber bullying. Understanding the vulnerability landscape is important in order to design a proper defense and in many cases, our physical and electronic worlds can be blurred when considering the potential threats.

      Vulnerabilities

      A vulnerability itself does not allow for an attack vector to succeed. In fact, a vulnerability in and of itself just means that a risk exists. Vulnerabilities are nothing more than a mistake. They are a mistake in the code, design, implementation, or configuration that allows malicious activity to potentially occur via an exploit. Thus, without an exploit, a vulnerability is just a potential problem and used in a risk assessment to gauge what could happen. Depending on the vulnerability, available exploit, and resources assessed with the flaw, the actual risk could be limited or a pending disaster. While this is a simplification of a real risk assessment, it provides the foundation for privileges as an attack vector. Not all vulnerabilities and exploits are equal, and depending on the privileges of the user or application executing in conjunction with the vulnerability, the escalation and effectiveness of the attack vector can change. For example, a word processor vulnerability executed by a standard user versus an administrator can have two completely different sets of risks once exploited. One could be limited to just the user’s privileges as a standard user, and the other could have full administrative access to the host. And, if the user is using a domain administrator account or other elevated privileges, the exploit could have permissions to the entire environment. This is something a threat actor targets as a low-hanging fruit. Who is running outside of security best practices and how can I leverage them to infiltrate the environment?

      With this in mind, vulnerabilities come in all shapes and sizes. They can target the operating system, applications, web applications, infrastructure, and so on. They can also target the protocols, transports, and communications in between resources from wired networks, Wi-Fi, to tone-based radio frequencies. Not all vulnerabilities have exploits, however. Some are proof of concepts, some are unreliable, and some are easily weaponized and even included in commercial penetration testing tools or free open source. Some are sold on the dark web for cybercrimes and others used exclusively by nation-states until they are patched or made public (intentionally or not). The point is that vulnerabilities can be in anything at any time. It is how they are leveraged that makes them important, and if the vulnerability itself lends to an exploit that can actually change privileges (privileged escalation from user’s permissions to another), the risk is very real for a privileged attack vector. To date, less than 10% of all Microsoft vulnerabilities patched allow for privilege escalation. A real threat considering hundreds of patches are released every year for their solutions alone.

      In order to convey the risks and identification of vulnerabilities, the security industry has multiple security standards to discuss the risk, threat, and relevance of a vulnerability. The most common standards are the following:

      Common Vulnerabilities and Exposure (CVE) – a standard for information security vulnerability names and descriptions.

      Common Vulnerability Scoring System (CVSS) – a mathematical system for scoring the risk of information technology vulnerabilities.

      The Extensible Configuration Checklist Description Format (XCCDF) – a specification language for writing security checklists, benchmarks, and related kinds of documents.

      Open Vulnerability Assessment Language (OVAL) – an information security community effort to standardize how to assess and report upon the machine state of computer systems.

      Information Assurance Vulnerability Alert (IAVA) – an announcement of a vulnerability in the form of alerts, bulletins, and technical advisories identified by DoD-CERT, a division of the United States Cyber Command; and they are a mandated baseline for remediation within the government and Department of Defense (DoD).

      Common Configuration Enumeration (CCE) – provides unique identifiers to system configuration issues in order to facilitate fast and accurate correlation of configuration data across multiple information sources and tools.

      Common Weakness Enumeration (CWE) – provides a common language of discourse for discussing, finding, and dealing with the causes of software security vulnerabilities as they are found in the code.

      Common Platform Enumeration (CPE) – a structured naming scheme for information technology systems, software, and packages.

      Common Configuration Scoring System (CCSS) –a set of measures of the severity of software security configuration issues. CCSS is a derivation of CVSS.

      Open Checklist Interactive Language (OCIL) – defines a framework for expressing a set of questions to be presented to a user and corresponding procedures to interpret responses to these questions that cannot be electronically automated or queried for a resource or environment. Essentially, they are questions that require human intervention to answer but are expressed in a standardized markup language.

      Asset Reporting Format (ARF) – a data model to express the transport format of information about assets and the relationships between assets and reports. The standardized data model facilitates the reporting, correlating, and fusing of asset information throughout solutions and governing or dependent organizations.

      Security Content Automation Protocol (SCAP) – a synthesis of interoperable specifications based on existing standards. For example, ratified version 1.2 of SCAP is comprised of XCCDF, OVAL, OCIL, ARF, CCE, CPE, CVE, CVSS, and CCSS at specific individual versions. This allows each standard to evolve separately but freezes versions in order to communicate them as a collection.

      Open Web Application Security Project (OWASP) – an online community that provides a not-for-profit approach to developing secure web applications by providing methodologies, tools, technology, and an assessment approach for vendors, organizations, and end

      Enjoying the preview?
      Page 1 of 1