Domain 6Security Assessment & TestingCORE

Security Assessment & Penetration Testing

Designing security assessment strategies, vulnerability scanning vs penetration testing methodologies, rules of engagement, code reviews, and SOC 1/2/3 report types.

Domain: Domain 6: Security Assessment and Testing•Updated: 2026-08-26
#Assessment#Penetration Testing#Vulnerability Assessment#Rules of Engagement#Black/White/Gray Box#SOC Reports

CISSP Domain 6: Security Assessment & Penetration Testing — Mindmap Review Study Guide

mindmap
  root((Vulnerability Assessment<br/>and Penetration Testing))
    Core Concepts
      Vulnerability Assessment
      Penetration Test
      Purpose and Goals
    Process Steps
      Reconnaissance
      Enumeration
      Vulnerability Analysis
      Execution
      Document Findings
    Testing Perspective
      Internal
      External
    Testing Approach
      Blind
      Double-blind
    Knowledge Levels
      Zero Knowledge Black-box
      Partial Knowledge Gray-box
      Full Knowledge White-box
    Scan Types
      Credentialed Authenticated
      Uncredentialed Unauthenticated
    Identification Techniques
      Banner Grabbing
      Fingerprinting
    Interpreting Results
      CVE
      CVSS
      SCAP
    Challenges
      False Positive
      False Negative

Core Concepts

Vulnerability Assessment — A testing process to identify, classify, and prioritize vulnerabilities for remediation. After identifying potential vulnerabilities, the assessment skips straight to reporting without attempting exploitation. Tends to be faster and more automated but generates far more false positives.

Penetration Test — A testing process that identifies potential vulnerabilities and then attempts to exploit them to verify if the vulnerability truly exists and can be exploited, thus eliminating false positives. Slower and more manual than vulnerability assessments, with a much higher likelihood of negatively impacting the system, but provides a much clearer picture of security.

Purpose and Goals — Both vulnerability assessments and penetration tests aim to identify potential vulnerabilities, report on them, understand the potential impact to the organization, and prioritize remediation.

Process Steps

Reconnaissance — A passive activity where the assessor gathers publicly available information from sources like job postings, LinkedIn profiles, and DNS records. The organization being assessed cannot detect anything at this step.

Enumeration — An ACTIVE step that can potentially be detected by the organization. Involves systematically walking through IP address ranges and ports to look for live systems that are offering services.

Vulnerability Analysis — The step where the exact version of a system is determined and potential vulnerabilities that could be exploited are identified. Uses techniques like banner grabbing and fingerprinting to identify system versions.

Execution — In a vulnerability assessment, this step is skipped and the process goes straight to reporting. In a penetration test, this is where the tester attempts to exploit any identified vulnerabilities and actually breaks into a system.

Document Findings — The reporting phase covering vulnerabilities identified, the potential impact to the organization, prioritization, and tailoring reports to various audiences.

Testing Perspective

Internal — Testing performed from within the organization’s network, simulating an attacker being inside the network.

External — Testing performed from outside the organization’s network, simulating an attacker being outside the firewall, typically out on the internet.

Testing Approach

Blind — The ethical hacker is given very limited information on the system to be tested, perhaps just an IP address. The ethical hacker is “blind” to the system details.

Double-blind — Not only is the ethical hacker given no information, but the organization’s security operations team is also not told that the test is occurring. This tests not only what the hacker can get into, but also how effectively the organization can detect and respond to the attack.

Knowledge Levels

Zero Knowledge (Black-box) — The tester is given zero knowledge of the system and must rely on publicly available information and whatever they can deduce. Simulates an outsider trying to break in. Zero knowledge and blind tests are the same thing.

Partial Knowledge (Gray-box) — The tester is given the knowledge of a user, potentially even elevated privileges on the system, and some basic info on system and network architecture. This makes testing more efficient.

Full Knowledge (White-box) — Also called open-box or clear-box testing. Testers are given full access to source code, full credentials, and detailed architectural documentation. Much more focused on going through the source code in detail.

Scan Types

Credentialed (Authenticated) Scan — The scanning tool is given the credentials necessary to log into the system(s) being scanned. Can take a deeper look into the exact configuration of a system, helping eliminate false positives and assisting with baseline compliance.

Uncredentialed (Unauthenticated) Scan — The scanning tool is not given credentials to log in. This is more a simulation of an external attacker and what vulnerabilities can be identified from the outside.

Identification Techniques

Banner Grabbing — Intentionally getting the system to generate something like an error message (e.g., error 404 file not found on a web server) and looking at the error message to see if the version number of the system is listed. Systems should be configured not to show this information.

Fingerprinting — A far more subtle technique than banner grabbing. Involves either passively monitoring network traffic going to a system, or actively sending a few specially crafted packets, then carefully evaluating the exact structure and contents of packets. Different versions of systems craft packets in subtly different ways, allowing fingerprinting of the exact version.

Interpreting Results

CVE (Common Vulnerabilities and Exposures) — A unique identifier for each vulnerability. A public database of all these vulnerabilities is maintained, and each discovered vulnerability has a unique CVE number assigned to it.

CVSS (Common Vulnerability Scoring System) — A standard for assessing the severity of a vulnerability on a scale from zero to ten.

⚠️ EXAM TIP: CVSS ranges from 0 (meh) to 10 (everyone should be running around screaming).

SCAP (Security Content Automation Protocol) — A collection of interoperable specifications to help organizations automate vulnerability management and policy compliance evaluation.

Challenges

False Positive — A potential vulnerability is identified, but upon further investigation, there is no actual vulnerability. Time is wasted chasing something that wasn’t there.

False Negative — A vulnerability exists but is not identified. The organization remains blind to the vulnerability.

⚠️ EXAM TIP: False negatives are far worse than false positives because the organization remains unaware of an actual vulnerability.