Knowledge is Power
BARE METAL CYBERKnowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

NIST SP 800-171 CUI Protection Center

03.04.05 — Access Restrictions for Change

Read the official CUI requirement and assessment content, then use the separately labeled Bare Metal Cyber perspective to connect it to implementation, evidence, and sustained operation.

1Source controls
6Assessment objectives
3Assessment methods

03.04 — Configuration Management · NIST SP 800-171 Revision 3

Active
Official NIST requirement content

Security requirement

Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system.

Official NIST discussion

Discussion

Changes to the hardware, software, or firmware components of the system or the operational procedures related to the system can have potentially significant effects on the security of the system. Therefore, organizations permit only qualified and authorized individuals to access the system for the purpose of initiating changes. Access restrictions include physical and logical access controls, software libraries, workflow automation, media libraries, abstract layers (i.e., changes implemented into external interfaces rather than directly into the system), and change windows (i.e., changes occur only during specified times).

Bare Metal Cyber interpretation

Implementation perspective

Treat Access Restrictions for Change as a CUI protection outcome 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.

  1. Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
  2. Resolve every organization-defined parameter through an approved governance and tailoring process.
  3. Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
  4. Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
  5. Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

  • Which CUI assets, data flows, users, and services are protected by this 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-171A content

Assessment objectives and methods

Assessment objectives (6)
  1. SR-03.4.5.

    physical access restrictions associated with changes to the system are defined and documented.

  2. SR-03.4.5.

    physical access restrictions associated with changes to the system are approved.

  3. SR-03.4.5.

    physical access restrictions associated with changes to the system are enforced.

  4. SR-03.4.5.

    logical access restrictions associated with changes to the system are defined and documented.

  5. SR-03.4.5.

    logical access restrictions associated with changes to the system are approved.

  6. SR-03.4.5.

    logical access restrictions associated with changes to the system are enforced.

Examine

  • configuration management policy and procedures
  • procedures for access restrictions for system changes
  • configuration management plan
  • system design documentation
  • system architecture
  • system configuration settings
  • logical access approvals
  • physical access approvals
  • access credentials
  • change control records
  • system audit records
  • system security plan
  • other relevant documents or records

Interview

  • personnel with logical access control responsibilities
  • personnel with physical access control responsibilities
  • personnel with information security responsibilities
  • system administrators

Test

  • processes for managing access restrictions for system changes
  • mechanisms for supporting, implementing, or enforcing access restrictions associated with system changes
Official source-control relationships

Source NIST SP 800-53 controls

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

Source controlCM-5Open 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.