How should teams handle control enhancements in practice?
Select an enhancement because the applicable baseline, overlay, requirement, or documented risk decision calls for its additional capability. A crosswalk may help locate candidates, but it does not establish applicability or implementation.
The base control and enhancement may have different owners or evidence, including common and system-specific portions. The security or privacy plan should describe both, and the assessment record should address the enhancement's own determination statements. If tailoring removes or modifies a baseline enhancement, retain the original allocation, applicable tailoring authority, rationale, approver, alternative protection when relevant, and residual-risk decision.
- Record the selection trigger and the base-control dependency before assigning implementation work.
- Complete every applicable parameter and identify whether the base value also applies to the enhancement.
- Document the implementation narrative, owner, common or system-specific portions, dependencies, and evidence for the added requirement.
- Use the applicable SP 800-53A procedure to record findings for the enhancement rather than folding it into an unsupported base-control conclusion.
- Review selection after baseline, overlay, requirement, risk, threat, boundary, technology, or common-control changes.
Defines enhancement purpose, base-control dependency, parameters, and implementation approaches.
Defines how assessors evaluate applicable enhancement requirements and organization-defined parameters.
Provides federal baseline allocations and tailoring guidance used to establish enhancement selection.