CISSP domain - 12% of the exam

Security Assessment and Testing

Security Assessment and Testing is 12% of the CISSP exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

36
Practice questions
5
Objectives
29
Medium
7
Hard

Where people go wrong

  • Assigning an audit type to the wrong requester

    The wrong answers assign an audit type to the wrong requester or treat the types as interchangeable. A third-party audit is directed by a customer that depends on the provider's controls. An external audit gives regulators and boards an independent attestation, which internal audit cannot issue. A SOC 2 Type 2 examination by a public accounting firm covers design and operating effectiveness over a period, which a surveillance audit, a vulnerability assessment or an internal report does not.

    See it in a sample question
  • Crediting one assessment type with another's job

    The wrong answers credit one assessment type with another's job, or define them by surface traits. A vulnerability assessment enumerates and prioritises weaknesses across the estate, while a penetration test exploits selected ones, chaining findings and abusing business logic to show realised impact. Tooling, environment and written authorisation apply to both, so none of them separates the two. Breach and attack simulation replays catalogued techniques automatically between scheduled tests and does not replace independent penetration testing, which regulators typically still require.

    See it in a sample question
  • Ranking findings by one number or by whoever owns them

    The wrong answers rank findings on a single score or pass triage to each system owner. Sorting on CVSS alone ignores exposure, asset criticality and compensating controls, and delegating triage to system owners produces inconsistent decisions. The correct answers validate findings to remove false positives, map each to the affected business process and asset criticality, and prioritise on residual risk to the institution.

    See it in a sample question
  • Reporting activity where an outcome measure is needed

    The wrong answers report activity where the question asks for an outcome. Job completion logs, window adherence and backup volume do not show that data restores within the recovery time objective, so only a test restore or the percentage of systems restored and validated does. Account creation volumes and reset turnaround do not show governance health, whereas the share of leavers disabled within the service level does. A patch KPI measures process performance, so exposure to a threat needs a key risk indicator tracked against a threshold.

    See it in a sample question
  • Accepting a third-party report at face value

    The wrong answers accept a third-party report at face value. A SOC 2 Type 2 with a carve-out excludes the sub-processor from the auditor's opinion, and a one-page summary letter omits the system description, tested controls and exceptions. A report is only useful once its scope and period match the services in use, its exceptions and complementary user entity controls are read, and residual risk is documented. A right-to-audit clause covers the residual gaps the report leaves.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleSecurity Assessment and Testingmedium

Which statement most accurately describes the principal value an internal audit function provides to the organisation that employs it, compared with audits conducted by outside parties?

  • AInternal audit produces opinions that satisfy regulators and external stakeholders because reporting to the board grants the function the legal independence required for statutory attestation.
  • BInternal audit primarily exists to perform penetration testing and vulnerability scans across the production estate, replacing the need for a dedicated security testing team.
  • CInternal audit guarantees that fraud cannot occur within finance, operations, or technology because every transaction passes through a continuous audit pipeline before posting.
  • DInternal audit delivers continuous, risk-prioritised assurance over the organisation's own control environment and can recommend management actions because it understands the business context in depth. Correct
Recognise that internal audit's distinctive value is risk-prioritised, ongoing, context-aware assurance over the organisation's own controls. Internal audit sits within the third line of defence and reports functionally to the audit committee, giving it independence from operational management while keeping it close to the business. Its strength is the ability to plan continuously against the organisation's risk profile and to recommend remediation, which a point-in-time external attestation cannot match.

Why A is wrong: Although internal audit reports administratively to executives and functionally to the audit committee, it is still part of the entity and therefore cannot issue the independent attestation that regulators and capital markets demand. That role belongs to external auditors.

Why B is wrong: While internal audit may commission or review technical testing, executing penetration tests is the remit of security testing teams. Conflating audit with offensive testing misreads the assurance role of internal audit defined under the three lines model.

Why C is wrong: No assurance function guarantees the absence of fraud; audit provides reasonable, not absolute, assurance and operates on a sampled, risk-based plan. The claim that every transaction is pre-audited is operationally unrealistic and not the function's stated purpose.

Why D is correct: The defining strength of an internal audit function is its ongoing presence, business knowledge, and risk-based plan endorsed by the audit committee. It provides management and the board with timely assurance and improvement recommendations rather than a point-in-time external opinion.

Free sampleSecurity Assessment and Testinghard

A security manager is reviewing the testing programme and wants to draw a clear line between a vulnerability assessment and a penetration test for the executive committee. Which statement BEST characterises the principal distinction between the two activities?

  • AA vulnerability assessment enumerates and prioritises potential weaknesses across the estate, whereas a penetration test attempts to exploit selected weaknesses to demonstrate realised business impact. Correct
  • BA vulnerability assessment is performed without management approval, whereas a penetration test always requires a signed rules-of-engagement document before any activity commences.
  • CA vulnerability assessment relies exclusively on automated scanners, whereas a penetration test relies exclusively on manual techniques performed by a human tester.
  • DA vulnerability assessment is performed only against production systems, whereas a penetration test is performed only against pre-production or staging environments.
Distinguish a vulnerability assessment from a penetration test by intent: identification and prioritisation versus controlled exploitation to evidence impact. CISSP material frames vulnerability assessment as a discovery-and-prioritisation activity that catalogues weaknesses, while penetration testing chains and exploits selected findings under defined rules of engagement to demonstrate realised business impact. Tooling, environment, and authorisation paperwork are scoping concerns common to both, so the technique is defined by intent and outcome rather than these surface attributes.

Why A is correct: This captures the canonical distinction recognised across CISSP source material: assessments are breadth-oriented and identification-led, while penetration tests are depth-oriented and exploitation-led, producing evidence of actual rather than theoretical risk.

Why B is wrong: Tempting because rules of engagement are most often emphasised for penetration testing, but both activities require written authorisation. Scope and authorisation discipline applies equally; the option mischaracterises assessment governance.

Why C is wrong: This reflects a common simplification. Vulnerability assessments often include manual validation, and modern penetration tests use automation extensively. Tool choice is not the defining boundary between the two.

Why D is wrong: The environment is a scoping decision driven by risk appetite and business continuity, not a defining property of the technique. Both can be run against either environment when authorised.

Free sampleSecurity Assessment and Testingmedium

When triaging the output of an automated vulnerability scan against a production estate, which approach BEST converts raw scanner findings into a defensible remediation plan?

  • AUse the scanner's CVSS base score alone to rank every finding, then patch in strict descending order until the maintenance window closes.
  • BForward the unfiltered scanner report to system owners and ask each owner to determine independently which findings their team will remediate.
  • COpen a remediation ticket for every finding regardless of confidence, on the basis that engineering will close noise during normal sprint grooming.
  • DValidate findings to remove false positives, then rank surviving issues by combining technical severity with asset criticality, exposure, and existing controls. Correct
Convert raw scanner output into a remediation plan by validating findings and ranking on contextual risk, not raw severity alone. Effective test output analysis has two stages: validation, which strips false positives and confirms exploitability, and contextual ranking, which adjusts technical severity using asset value, network exposure, and any compensating controls. Only then does the remediation plan reflect actual residual risk to the business.

Why A is wrong: Tempting because CVSS base is universally available and easy to sort on, but base scores ignore environmental factors such as exposure, asset criticality, and compensating controls, so they alone produce a misranked plan.

Why B is wrong: Tempting because owners do drive fixes, but devolving triage without central validation and risk weighting produces inconsistent decisions, duplicated false-positive work, and gaps where shared infrastructure has no clear owner.

Why C is wrong: Tempting because it appears thorough, but flooding engineering with unvalidated noise erodes trust in the security backlog and pushes real findings down the queue behind false positives.

Why D is correct: Correct. Test output analysis pairs validation with business-context risk scoring so remediation effort lands where genuine residual risk is highest, not merely where the scanner shouted loudest.

Free sampleSecurity Assessment and Testingmedium

A CISO is designing the account management process data that will be reported each quarter to the audit committee. Which metric is the MOST useful indicator of identity and access governance health for that audience?

  • AThe total number of user accounts created across in-scope systems during the reporting quarter, broken down by business unit and platform.
  • BThe mean time taken by the service desk to fulfil a password reset request, measured from ticket creation to ticket closure across the quarter.
  • CThe percentage of leavers whose accounts were disabled within the documented service level after their final working day, against the total leavers in the quarter. Correct
  • DThe number of privileged sessions recorded by the privileged access management tool during the quarter, segmented by platform and administrator group.
Select an account management metric that reflects identity governance outcomes rather than raw activity for board-level reporting. Account management data should support governance decisions. Timeliness of leaver disablement is a leading indicator of insider risk exposure and a recurring audit finding, which is why the CISSP body of knowledge highlights it as a meaningful account management metric.

Why A is wrong: Raw account creation volumes are easy to collect but say little about governance health, because they describe activity rather than whether access is appropriate, timely, or properly reviewed.

Why B is wrong: Password reset turnaround is a useful service KPI but it is an operational efficiency measure that does not tell the audit committee whether access rights themselves are being governed appropriately.

Why C is correct: Timely disablement of leaver accounts directly evidences a core identity governance control. It speaks to insider risk, segregation of duties, and audit expectations, making it the most useful indicator for the audit committee.

Why D is wrong: Privileged session counts show that monitoring is occurring, but volume alone does not indicate whether privileged access is governed well; an audit committee needs an outcome measure such as leaver disablement timeliness.

Free sampleSecurity Assessment and Testingmedium

A bank is preparing a third-party assurance strategy for its critical SaaS payroll provider. The CISO is comparing a SOC 2 Type II report with the right to perform an on-site audit clause that exists in the contract. Which statement BEST reflects how these two assurance options compare conceptually?

  • AA SOC 2 Type II is a point-in-time design review, while a right-to-audit clause forces the provider to operate under the customer's internal control framework instead of its own.
  • BA SOC 2 Type II eliminates the need for any contractual audit rights because the AICPA certifies that the provider has zero residual risk for all customer use cases.
  • CA right-to-audit clause is legally enforceable only when no SOC 2 report exists, so the two assurance mechanisms cannot be combined within a single contract.
  • DA SOC 2 Type II provides operating-effectiveness evidence across a period and is efficient for many customers to consume, while the right-to-audit clause supports targeted, customer-specific testing where the standard report does not cover a residual risk. Correct
Compare SOC 2 Type II reports and contractual right-to-audit clauses as complementary third-party assurance mechanisms. SOC 2 Type II reports give a credible, period-based view of design and operating effectiveness against the Trust Services Criteria, but their scope is set by the provider and may not address every customer's residual risk. A contractual right-to-audit clause lets the customer test those gaps directly. The two are complementary, not mutually exclusive, and a strong third-party strategy uses standardised reports for breadth and audit rights for depth.

Why A is wrong: Confuses Type I with Type II; Type II covers operating effectiveness across a period. A right-to-audit clause does not subordinate the provider to the customer's framework; it grants access to evidence, not control over the provider's policies.

Why B is wrong: Tempting because SOC 2 carries weight, but it is an attestation under AICPA standards, not a zero-risk certification, and its scope rarely matches every customer's risk picture. Right-to-audit clauses remain useful for residual risks.

Why C is wrong: There is no such precedence rule. Mature contracts commonly include both, using the SOC 2 as routine evidence and the audit right as an escalation path. The statement misstates how the two mechanisms interact.

Why D is correct: Correct. SOC 2 Type II reports cover design and operating effectiveness over time and scale across many customers. A right-to-audit clause complements the report by enabling bespoke testing of issues or controls not addressed by the standard scope, balancing efficiency and depth.

Other domains in this exam

See also the CISSP cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by ISC2. Original, blueprint-aligned practice material only.