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-172 Enhanced CUI Protection Center

03.04.04E — Automation Support for Baseline Configuration

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.

1Parameters
1Source controls
4Assessment objectives
3Assessment methods

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

Active
Official NIST requirement content

Security requirement

Maintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using [Organization-defined: automated mechanisms].

Official NIST discussion

Discussion

Automated mechanisms that help organizations maintain consistent baseline configurations for systems include configuration management tools; hardware, software, and firmware inventory tools; and network management tools. Automated tools can be used to track version numbers on operating systems, applications, the types of software installed, and current patch levels. Automation support for accuracy and currency can be satisfied by the implementation of 03.04.03E for organizations that combine system component inventory and baseline configuration activities. This requirement enhances SP 800-171 requirement 03.04.01.

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.

automated mechanismsorganization-defined automated mechanismsautomated mechanisms for maintaining the baseline configuration of the system are 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-DLODamage-Limiting Operations
PS-PRAPenetration-Resistant Architecture
Bare Metal Cyber interpretation

Implementation perspective

Treat Automation Support for Baseline Configuration 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.

  1. 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.
  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 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 (4)

  1. the currency of the baseline configuration of the system is maintained using [Organization-defined: automated mechanisms].

  2. the completeness of the baseline configuration of the system is maintained using [Organization-defined: automated mechanisms].

  3. the accuracy of the baseline configuration of the system is maintained using [Organization-defined: automated mechanisms].

  4. the availability of the baseline configuration of the system is maintained using [Organization-defined: automated mechanisms].

Examine

  • Configuration management policy
  • procedures addressing the baseline configuration of the system
  • configuration management plan
  • system design documentation
  • system architecture and configuration documentation
  • system configuration settings and associated documentation
  • system component inventory
  • configuration change control records
  • system security plan
  • other relevant documents or records

Interview

  • Personnel with configuration management responsibilities
  • personnel with information security responsibilities
  • system/network administrators

Test

  • Processes for managing baseline configurations
  • automated mechanisms implementing baseline configuration maintenance
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-2(2)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.