RA-4 — Risk Assessment Update

From control text to operational evidence

Use Risk Assessment Update as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to risk framing, threat and vulnerability analysis, impact, criticality, and response decisions.

Implementation workflow

• Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
• Resolve each organization-defined parameter before declaring the control implemented.
• Document how the implementation satisfies every clause of the official control statement.
• Collect evidence as a normal byproduct of operation rather than only before an assessment.
• Review exceptions, changes, and monitoring results on a risk-based cadence.

Evidence examples

• risk assessments and threat models
• vulnerability findings and prioritization records
• supply-chain risk assessments
• risk response and acceptance decisions

Common failure patterns

• risk registers detached from technical evidence
• vulnerability severity treated as business impact
• assessments not updated after material change
• accepted risks have no owner or expiration

Questions practitioners should ask

• What risk decision is this control intended to support in this system?
• Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
• Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
• What event or threshold requires the implementation to be reviewed or changed?