DOMAIN 6 · Security Assessment and Testing
Control Assessment: From Requirements to Evidence
Plan a defensible assessment, combine examination, interviews, and tests, and report findings separately from risk acceptance.
Decide what the assessment must establish
Section titled “Decide what the assessment must establish”A control assessment gathers evidence about whether a control meets specified objectives. It is more than checking that a product is installed or a policy exists. NIST SP 800-53A Rev. 5 provides an assessment methodology linked to SP 800-53 controls, with procedures that organizations can tailor to their circumstances.1
Begin with a clear requirement and the scope in which it applies. Without them, two assessors can examine the same evidence and reach different conclusions because they are answering different questions.
Build the assessment plan
Section titled “Build the assessment plan”Identify the systems, processes, people, assessment period, and controls in scope. Define the evidence needed, methods, responsibilities, dependencies, and reporting approach. Agree how to obtain records without unnecessarily exposing sensitive information or disrupting operations.
NIST distinguishes specifications, mechanisms, activities, and individuals as assessment objects. A review can therefore include an approved procedure, a technical enforcement mechanism, records of performed work, and the people responsible. Select objects that support the assessment objective rather than collecting every available document.1
Combine three methods
Section titled “Combine three methods”| Method | What it contributes | Example |
|---|---|---|
| Examine | Evidence from reviewing or observing assessment objects | Inspect access-review records |
| Interview | Understanding from responsible people | Ask how rejected access is removed |
| Test | Evidence of behavior under specified conditions | Verify that revoked access no longer works |
An interview can explain a procedure without proving that it operated throughout the period. A test can demonstrate one outcome without proving complete population coverage. Combining methods addresses these limitations; NIST does not require every method for every object.1
Distinguish depth from coverage
Section titled “Distinguish depth from coverage”Depth concerns the rigor and detail of the assessment. Coverage concerns its breadth, including which objects or instances are examined. A detailed test of one account has substantial depth for that account but limited coverage of the organization.
Document sampling choices and exclusions. If a service provider operates part of a control, identify what evidence is inherited and what the customer must still assess. A provider’s assurance report does not automatically prove that the customer’s own configuration meets its requirement.
Worked example: removing privileged access
Section titled “Worked example: removing privileged access”Suppose a fictional organization requires privileged access to be removed when a contractor leaves. The assessor examines the approved requirement, interviews the account owner, samples departures during the assessment period, and tests a suitable account in a controlled setting.
If a sample lacks evidence of timely removal, the report identifies the specific account, period, missing evidence, and affected objective. The assessor does not declare that every account is compromised. NIST’s findings distinguish objectives that are satisfied from those that are other than satisfied, including cases where sufficient evidence could not be obtained. Subsequent risk acceptance belongs to the organization’s risk-management process.1
Relate assessment to ISMS auditing
Section titled “Relate assessment to ISMS auditing”JIPDEC’s public ISMS user guide discusses internal audit as a way to evaluate conformity, effective operation, and improvement opportunities. This provides a useful management-system perspective alongside technical assessment.2
The guide is an explanation of ISMS requirements, not a substitute for the ISO/JIS standard. Similarly, completing a NIST assessment does not by itself establish conformity with ISO/IEC 27001 or confer ISMS certification.
Common misunderstandings
Section titled “Common misunderstandings”- “No evidence means the control certainly failed.” Report the evidence limitation and the resulting determination precisely.
- “A passed test proves ongoing effectiveness.” State the tested conditions, period, and coverage.
- “The assessor accepts the risk.” Findings inform the accountable organization’s decision.
Connect this topic
Section titled “Connect this topic”Security testing explores technical methods. Access control and business continuity provide examples of controls requiring both operational records and behavioral evidence.
References
Section titled “References”Footnotes
Section titled “Footnotes”-
NIST, SP 800-53A Rev. 5, Assessing Security and Privacy Controls in Information Systems and Organizations, January 2022; sections 2.4 and 3 on assessment methods, planning, execution, and findings. The publication record also records the August 2025 Release 5.2.0 assessment-procedure updates. ↩ ↩2 ↩3 ↩4
-
JIPDEC, ISMS User’s Guide: JIS Q 27001:2023 / ISO/IEC 27001:2022, March 2025; sections 9.1–9.2 (monitoring, evaluation and internal audit), printed pp. 60–67. Public explanatory guidance. ↩
Independent, unofficial study notes. Not endorsed or reviewed by ISC2. CISSP is a registered trademark of ISC2.
Editorial policy & attribution