03.04.05E — Dual Authorization for System Changes

Official NIST requirement content

Security requirement

Enforce dual authorization for implementing changes to [Organization-defined: organization-defined system components and system-level information].

Official NIST discussion

Discussion

Dual authorization is also known as two-person control. Organizations employ dual authorization to help ensure that any changes to selected system components and system-level information cannot occur unless two qualified individuals approve and implement such changes. Requiring two individuals to implement system changes provides an increased level of assurance that the proposed changes are correct implementations of approved changes. The individuals are also accountable for the changes that have been implemented. To reduce the risk of collusion, organizations consider rotating dual authorization duties to other individuals. System-level information includes operational procedures. This requirement enhances SP 800-171 requirement 03.04.05.

Official organization-defined parameters

Tailoring decisions required

Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.

organization-defined system components and system-level information

system componentsorganization-defined system components and system-level informationsystem components requiring dual authorization for the implementation of changes are defined.

system-level informationorganization-defined system components and system-level informationsystem-level information requiring dual authorization for the implementation of changes is defined.

Official protection strategy classifications

Protection strategies supported

These classifications are carried from the official SP 800-172 OSCAL record and help explain the enhanced requirement’s defensive purpose.

PS-PRAPenetration-Resistant Architecture

Bare Metal Cyber interpretation

Implementation perspective

Treat Dual Authorization for System Changes as an enhanced CUI protection outcome for elevated threat conditions that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to approved baselines, secure configuration, change control, inventories, and drift management within the CUI boundary.

Confirm the federal agency selected this enhanced requirement for the critical program or high-value asset and identify the CUI system components, services, users, and external connections in scope.
Resolve every organization-defined parameter through an approved governance and tailoring process.
Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

Which critical-program or high-value-asset CUI, data flows, users, and services are protected by this enhanced requirement?
Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
What change, incident, or threshold should trigger reassessment?

Evidence and validation

approved baseline configurations
change tickets and approvals
configuration scan and drift reports
software and hardware inventories

Common failure patterns

baselines documented but not enforced
emergency changes never reconciled
cloud or ephemeral assets missing from inventory
security impact analysis performed after deployment

Official NIST SP 800-172A content

Assessment objectives and methods

Assessment objectives (2)

dual authorization for implementing changes to [Organization-defined: system components] is enforced.
dual authorization for implementing changes to [Organization-defined: system-level information] is enforced.

Examine

Configuration management policy
procedures addressing access restrictions for changes to the system
configuration management plan
system design documentation
system architecture and configuration documentation
system configuration settings and associated documentation
change control records
system audit records
system component inventory
system information types
system security plan
other relevant documents or records

Interview

Personnel with dual authorization enforcement responsibilities for implementing system changes
personnel with information security responsibilities
system/network administrators

Test

Processes for managing access restrictions to change
mechanisms implementing dual authorization enforcement

Official source-control relationships

Source NIST SP 800-53 controls

These controls are referenced by the official SP 800-172 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.

Source controlCM-5(4)Open SP 800-53 control →

Source record

Authoritative sources

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.