Question 530
At Sable Coast Logistics, a supplier's HR system and CUI engineering enclave share a network, and the scoping team excludes HR without checking connectivity. The review team must protect the integrity of any information it handles and stay within its authorized CMMC role. Which statement best characterizes the residual risk if no verified correction is made?
Explanation
Correct Answer
This correctly treats the unverified issue as unresolved. The case-specific reason is: Scope is based on handling and protection relationships, not just department names. Required proof: Document the flow and the separation or dependency that supports classification.
Incorrect Answers
“The risk disappears merely because the team considered this proposed action: Exclude HR automatically because it is not called engineering” documents intent rather than a verified outcome. The required action and validation are: The issue remains open until there is proof for this acceptance criterion: Document the flow and the separation or dependency that supports classification. Underlying exposure: Scope is based on handling and protection relationships, not just department names.
Scope and applicability require an authoritative analysis, not a convenient alternative. Scope is based on handling and protection relationships, not just department names.
An unsupported statement cannot close a deficiency. The intended correction is: Trace CUI information flow, security dependencies and logical isolation before exclusion.