Security Assessment, Testing & Auditing
CISSP CISSP · Security Assessment and Testing
Assessment: proving controls work
Domain 6 is about verification: how do you know your security controls actually work? A control that has never been tested is an assumption, not a control. Security assessment and testing provides the evidence — for management, for auditors, for regulators, and for the security team itself — that controls are designed correctly, implemented properly, and operating effectively. The exam treats assessment as a continuous discipline, not a one-off event: threats change, systems change, and controls that worked last year may not work today.
Vulnerability assessment vs penetration testing
The exam's most fundamental distinction in this domain is between a vulnerability assessment and a penetration test. A vulnerability assessment identifies and reports vulnerabilities — typically using automated scanners that compare systems against databases of known weaknesses — and produces a prioritised list of findings. It answers the question "what weaknesses exist?" A penetration test goes further: a tester actively attempts to exploit vulnerabilities to determine whether they can actually be used to compromise the system, and how far an attacker could get. It answers the question "what can an attacker actually do?" The two are complementary: a vulnerability assessment is broad and automated; a penetration test is deep and manual. The exam also tests the knowledge levels of penetration testing: black box (the tester has no prior knowledge of the target, simulating an external attacker), white box (the tester has full knowledge, including source code and architecture, simulating an insider or a thorough audit), and grey box (partial knowledge, simulating an attacker with some inside information, such as a low-privileged user). The choice depends on the goal: black box tests detection and external defences; white box finds the most vulnerabilities in the least time.
Testing strategies and methods
Assessment methods vary by what is being tested. Network scanning discovers live hosts, open ports and services. Vulnerability scanning checks for known weaknesses. Penetration testing exploits weaknesses. Social engineering testing (phishing simulations, pretexting calls, physical intrusion attempts) tests the human element — and the exam notes that these tests require explicit authorisation and careful scoping, since they involve deceiving employees. Code review (manual or automated static analysis) examines source code for vulnerabilities. Security audits systematically evaluate whether controls comply with policy and standards. Red team / blue team exercises simulate real attacks: the red team attacks, the blue team defends, and the exercise tests detection and response, not just prevention. A purple team combines both, with the red and blue teams collaborating to improve defences. The exam also covers breach and attack simulation (BAS) — automated, continuous simulation of attack techniques — as a newer method. The key principle across all methods: testing must be authorised in writing, scoped clearly, and scheduled to avoid disrupting production systems.
Log review and security process data
Assessment is not only about active testing; it also involves analysing the data security processes generate. Log reviews examine system, application and security logs for anomalies — failed logins, privilege escalations, unusual access patterns. The exam expects you to know that log review must be systematic (not ad hoc), that logs must be protected from tampering (centralised collection, write-once storage, restricted access), and that log retention must meet legal and regulatory requirements. Security metrics turn raw data into management information: mean time to detect (MTTD), mean time to respond (MTTR), patch compliance rates, vulnerability remediation times, and phishing click rates. The exam's framing is that metrics must be meaningful to their audience: executives need trend and risk information, not raw counts. Key performance indicators (KPIs) measure how well a process performs; key risk indicators (KRIs) signal increasing risk before an incident occurs. A rising number of unpatched critical vulnerabilities is a KRI; the percentage of systems patched within the SLA is a KPI.
Testing security controls
Each type of control needs a testing approach. Technical controls are tested by scanning, penetration testing and configuration review. Administrative controls (policies, procedures, training) are tested by document review, interviews and observation — does the policy exist, is it current, do people follow it? Physical controls are tested by inspection and attempted bypass. The exam distinguishes control testing (does the control work?) from compliance testing (does the organisation follow its own policies and external requirements?). Security control assessments follow a structured approach, such as the one in NIST SP 800-53A: define the assessment plan, assess the controls, document findings, and recommend remediation. The exam also covers test data and test environments: testing should happen in non-production environments where possible, using masked or synthetic data, so that testing itself does not create risk.
Audits and assurance
An audit is a formal, independent examination of whether controls are adequate and operating effectively. The exam distinguishes internal audits (performed by the organisation's own audit function, reporting to management or the audit committee) from external audits (performed by independent third parties, providing assurance to regulators, customers or shareholders). Auditors must be independent of the function they audit — an auditor cannot audit their own work. Common audit frameworks and reports include SOC 1 (controls relevant to financial reporting), SOC 2 (controls relevant to security, availability, processing integrity, confidentiality and privacy — the Trust Services Criteria — widely used by service providers to assure customers), and SOC 3 (a public summary of a SOC 2 report). A SOC 2 Type I report assesses whether controls are suitably designed at a point in time; a Type II report assesses whether they operated effectively over a period (typically 3–12 months) — Type II provides much stronger assurance and is what customers should ask for. The exam also covers ISO 27001 certification audits and internal control frameworks such as COSO. The auditor's role is to report findings, not to fix them — remediation is management's responsibility, and the exam tests this separation.
| Report | Scope | Key distinction |
|---|---|---|
| SOC 1 | Controls over financial reporting | For user entities' financial auditors |
| SOC 2 Type I | Trust Services Criteria (security, availability, integrity, confidentiality, privacy) | Design at a point in time |
| SOC 2 Type II | Same criteria | Operating effectiveness over a period — stronger assurance |
| SOC 3 | Summary of SOC 2 | Public-facing, less detail |
Reporting and remediation
Assessment is only useful if its findings lead to action. Findings should be reported with severity ratings, evidence, business impact, and recommended remediation — and assigned to an owner with a deadline. The exam expects you to know that findings must be prioritised by risk, not by ease of fixing: a critical vulnerability on an internet-facing system outranks a low-severity finding on an internal system, even if the latter is easier to fix. Remediation verification — re-testing to confirm the fix works — is part of the cycle, not an optional extra. Findings that cannot be fixed immediately should be documented as accepted risks with a formal risk acceptance, not silently ignored. The exam also tests the handling of false positives (reported vulnerabilities that do not actually exist) and false negatives (real vulnerabilities the assessment missed): scanners produce both, and skilled testers validate findings before reporting them.
Exam mindset for assessment and testing
Assessment questions reward knowing what each method can and cannot do: a vulnerability scan finds known weaknesses but does not prove exploitability; a penetration test proves exploitability but is a point-in-time snapshot; an audit provides independent assurance but does not fix anything. And remember that all testing requires written authorisation and a defined scope — unauthorised testing is indistinguishable from an attack.
Exam traps to watch for
- Confusing vulnerability assessment with penetration testing: assessment identifies weaknesses; penetration testing exploits them to prove impact.
- Accepting a SOC 2 Type I report when Type II is needed: Type I is design at a point in time; Type II proves controls operated effectively over a period.
- Forgetting that testing requires written authorisation and scope — unscoped testing can disrupt production and create legal exposure.
- Treating the auditor as the fixer: auditors report findings; management owns remediation.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.An organisation runs an automated scan that identifies 200 known vulnerabilities across its systems, prioritised by severity. The security team wants to know which of these an attacker could actually exploit to reach the customer database. What should they do NEXT?
Explanation: A vulnerability scan identifies weaknesses but does not prove exploitability; a penetration test actively exploits them and traces the attack path, which is exactly the question being asked. Re-scanning produces the same list. A SOC 2 audit assesses control design and operation, not exploitability. Patching all 200 immediately is impractical without prioritisation and does not answer which vulnerabilities are actually exploitable.
Exam objective: CISSP Domain 6: Understand assessment and test strategies (vuln assessment vs pen test)
Q2.A company is evaluating a cloud service provider and asks for evidence that the provider’s security controls operated effectively over the past year. Which report should the company request?
Explanation: A SOC 2 Type II report evaluates whether controls operated effectively over a period (typically 3–12 months), which is precisely the evidence requested. A Type I report only assesses whether controls are suitably designed at a single point in time. A SOC 1 report covers controls relevant to financial reporting, not general security. A penetration test is a point-in-time exercise and cannot prove the absence of vulnerabilities.
Exam objective: CISSP Domain 6: Understand security audit concepts (SOC reports)
Q3.A penetration test is planned against a production web application. The testers have been given the source code, network diagrams and user credentials. What type of penetration test is this?
Explanation: White box testing gives the testers full knowledge — source code, architecture, credentials — simulating an insider or a thorough audit, and it finds the most vulnerabilities in the least time. Black box means no prior knowledge. Grey box means partial knowledge (such as a low-privileged account). Red team describes an adversarial exercise against defences, not a knowledge level.
Exam objective: CISSP Domain 6: Understand assessment and test strategies (pen test types)
Q4.An internal auditor discovers that the security team has not patched a critical vulnerability on an internet-facing server for 90 days. The security manager asks the auditor to help implement the patch. What is the auditor’s appropriate response?
Explanation: Auditors must remain independent: their role is to report findings with severity and recommendations, not to implement fixes. Helping to implement the patch would compromise the auditor's independence and their ability to later verify the remediation. Ignoring the finding violates the auditor's duty. Patching the server personally is both a breach of independence and outside the auditor's role.
Exam objective: CISSP Domain 6: Understand security audit concepts (auditor independence)
Q5.A vulnerability scanner reports that a server is missing a patch, but manual verification shows the patch is installed and the scanner misread the version number. What is this an example of?
Explanation: A false positive is a reported finding that does not reflect a real vulnerability — the scanner flagged a missing patch that is actually present. A false negative is the opposite: a real vulnerability the scanner missed. A true positive would be a correctly identified vulnerability. A zero-day is a vulnerability unknown to the vendor, which is unrelated to scanner accuracy.
Exam objective: CISSP Domain 6: Understand security process data (false positives/negatives)
Q6.A CISO wants a metric that warns the organisation when risk is increasing, before an incident occurs. Which is the BEST example of such a metric?
Explanation: A key risk indicator (KRI) signals increasing risk before an incident: a rising count of unpatched critical vulnerabilities beyond SLA means the organisation is becoming more exposed. Incident counts and MTTD are lagging indicators — they describe what already happened. Training completion is a process measure (KPI), not a forward-looking risk signal.
Exam objective: CISSP Domain 6: Understand security process data (KPIs vs KRIs)
Q7.Before conducting a penetration test against a client’s production systems, what is the MOST important prerequisite?
Explanation: Written authorisation with a defined scope is the essential prerequisite: without it, penetration testing is legally indistinguishable from an attack, and unscoped testing can disrupt production or exceed the client's consent. Tool selection matters but is secondary. Tester knowledge level is a scoping choice, not a prerequisite. Scheduling outside business hours is good practice but does not substitute for authorisation.
Exam objective: CISSP Domain 6: Understand assessment and test strategies (rules of engagement)
Q8.A red team exercise is planned to test the organisation’s detection and response capabilities. The blue team (defenders) will not be told when the exercise takes place. What is the PRIMARY purpose of keeping the blue team uninformed?
Explanation: An unannounced exercise tests the organisation's genuine detection and response capability under realistic conditions — real attackers do not schedule their attacks or warn the defenders. Cost reduction is not the purpose. Testing tool detection is a narrow technical goal, not the primary purpose of the exercise. There is no general regulatory requirement for unannounced red team exercises.
Exam objective: CISSP Domain 6: Understand assessment and test strategies (red team / blue team)