We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

FAQGLOBALNIST SP 800-53 Rev. 5

NIST SP 800-53 Rev. 5 When should teams select NIST control enhancements?

Select an enhancement only with its base control, document why it applies, complete its parameters, implement it, and assess its own requirements.

An enhancement number in a baseline or crosswalk is a selection input, not evidence that the enhancement operates.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Questions
2

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 24, 2026
Overview

A adds functionality or specificity to a or increases its strength. Selecting an enhancement always requires selecting and implementing its base control. Treat each selected enhancement as assessable control text: complete its parameters, assign responsibility, document implementation and inheritance, and evaluate its own applicable SP 800-53A determination statements.

Search this module

Find a question or answer quickly

2 of 2 questions
Question 1

What are control enhancements in NIST SP 800-53 Rev. 5?

Control enhancements add functionality or specificity to a or increase its strength. NIST states that selecting and implementing an enhancement always requires selecting and implementing its base control.

The catalog's numbering does not rank enhancements by importance or imply an implementation sequence. Selection may come from an SP 800-53B baseline, an overlay, another applicable requirement, or an organization-specific risk decision. For example, AU-4 requires allocating audit log storage capacity to accommodate organization-defined audit log retention requirements; AU-4(1) adds transferring audit logs to a different system, system component, or medium at an organization-defined frequency. Selecting AU-4(1) therefore requires AU-4, the retention requirements and frequency values, the storage allocation and transfer implementations, and evidence for both statements.

  • Record the baseline, overlay, requirement, or risk decision that selected the enhancement.
  • Select and implement the before treating the enhancement as applicable.
  • Complete assignment and selection operations in the and enhancement and keep their scopes consistent.
  • Review the selection after relevant baseline, requirement, risk, threat, boundary, technology, or implementation changes.
Citations
NIST SP 800-53 Rev. 5 Controls

Section 2.2 defines control enhancements, their relationship to base controls, and the rule that selecting an enhancement requires selecting its base control.

Question 2

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 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.
Citations
Recommended next step

Put this NIST SP 800-53 Rev. 5 guidance into practice

Use the cited sources to turn the guidance into scoped decisions, owners, evidence requests, and review checkpoints.

Assessment workflow
Open Assessment Autopilot for NIST SP 800-53 Rev. 5

Create cited tasks, evidence requests, and review checkpoints for this NIST SP 800-53 Rev. 5 scope.

Explore next step
Talk to Sorena
Review this NIST SP 800-53 Rev. 5 scope with Sorena

Check source coverage, ownership, evidence gaps, and next steps before publishing or operationalizing the work.

Explore next step
Primary sources

References and citations

NIST SP 800-53 Rev. 5 Controls
doi.org
Referenced sections
  • Defines enhancement purpose, base-control dependency, parameters, and implementation approaches.
Related guides

Explore more topics

How do NIST SP 800-53A assessment methods work?
Use SP 800-53A examine, interview, and test methods against specific determination statements, with documented objects, depth, coverage, and findings.
How do teams select and tailor NIST SP 800-53B baselines?
Start with the applicable SP 800-53B security and privacy baselines, then document categorization, tailoring, parameters, overlays, responsibility, and additions.
How should teams complete NIST control parameters?
Complete every SP 800-53 assignment and selection operation with an approved, scoped, implementable value, then assess the completed control statement.
How should teams document NIST common controls?
Document the common-control provider, inherited capability, parameters, consumer boundary, assessment results, dependencies, and system-specific work.
How should teams document NIST control inheritance?
Verify actual control inheritance by comparing provider scope, completed parameters, assessment results, dependencies, and remaining system-specific work.
NIST SP 800-53 Rev. 5 Applicability Guide
Decide whether NIST SP 800-53 applies, identify the adopting authority and boundary, and document the control, assessment, and authorization path.
NIST SP 800-53 Rev. 5 Baseline Selection Guide
Choose the NIST SP 800-53B security and privacy starting baselines, document the basis, and preserve the tailoring decisions that produce the final control set.
NIST SP 800-53 Rev. 5 Control Assessment Evidence Workflow
Plan and document SP 800-53A assessments by mapping determination statements to examine, interview, and test evidence, coverage, findings, and risk decisions.
NIST SP 800-53 Rev. 5 Control Families Explained
Understand all 20 NIST SP 800-53 Rev. 5 control families, how base controls and enhancements work, and how to assign ownership and assessment evidence.
NIST SP 800-53 Rev. 5 Control Tailoring Method
Tailor an NIST SP 800-53B baseline with scoping, common controls, parameters, compensating controls, additions, implementation detail, and documented approvals.
NIST SP 800-53 Rev. 5 Evidence and Audit Readiness Guide
Prepare assessment evidence for NIST SP 800-53A by linking each determination statement to scoped, current, reproducible examine, interview, or test records.
NIST SP 800-53 Rev. 5 FAQ: practical implementation questions
Answers to NIST SP 800-53 Rev. 5 questions on applicability, baselines, tailoring, parameters, enhancements, inheritance, assessments, evidence, and POA&Ms.
NIST SP 800-53 Rev. 5 Overlays and Common Controls Guide
Apply NIST SP 800-53 overlays and document common, hybrid, and inherited controls with clear provider, consumer, assessment, and change responsibilities.
NIST SP 800-53 Rev. 5 POA&M Evidence Guide
Document POA&M source findings, planned remediation, milestones, status evidence, governance decisions, and reassessment-backed closure under NIST SP 800-53 CA-5.
NIST SP 800-53 Rev. 5 POA&M Evidence Workflow
Turn assessed control deficiencies into governed POA&M records with risk, corrective actions, resources, milestones, status evidence, and validated closure.
NIST SP 800-53 Rev. 5 SP 800-53A Assessment Procedures Guide
NIST SP 800-53A gives assessors a methodology and set of procedures for checking whether security and privacy controls are implemented correctly, operating as intended, and producing the desired outcome.
NIST SP 800-53 Rev. 5 vs CIS Controls Decision Guide
Decide when to use NIST SP 800-53 Rev. 5 or CIS Controls v8.1, how selection differs, and when control evidence can be reused.
NIST SP 800-53 Rev. 5 vs CIS Controls: practical side-by-side comparison
Compare NIST SP 800-53 Rev. 5 and CIS Controls v8.1 by scope, selection method, safeguards, assessment evidence, and assurance.
NIST SP 800-53 Rev. 5 vs ISO/IEC 27001: practical side-by-side comparison
Compare NIST SP 800-53 Rev. 5 with ISO/IEC 27001:2022 by scope, controls, ISMS requirements, evidence, and certification.
NIST SP 800-53 Rev. 5 vs NIST CSF 2.0: practical side-by-side comparison
Compare NIST SP 800-53 Rev. 5 and CSF 2.0 by scope, controls, outcomes, Profiles, Tiers, evidence, and assurance.
NIST SP 800-53 Rev. 5 vs NIST CSF Decision Guide
Decide when to use NIST SP 800-53 Rev. 5 or CSF 2.0, how controls relate to outcomes, and when evidence can support both.
NIST SP 800-53 Rev. 5 vs NIST SP 800-171 Decision Guide
Decide when to use NIST SP 800-53 Rev. 5 or SP 800-171 Rev. 3, how their scopes differ, and when control evidence can be reused.
NIST SP 800-53 Rev. 5 vs NIST SP 800-171 Rev. 3: practical side-by-side comparison
Compare NIST SP 800-53 Rev. 5 with SP 800-171 Rev. 3 by scope, adopting authority, CUI boundary, requirements, evidence, and assessment.
What evidence should teams collect for NIST SP 800-53A control assessments?
Collect evidence for each SP 800-53A determination statement, using the selected examine, interview, and test methods at the planned depth and coverage.
What should a POA&M item include for NIST SP 800-53 Rev. 5 control gaps?
A useful POA&M item identifies the finding, affected control and system, risk response, owner, milestones, status evidence, dependencies, and closure criteria.