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.12.03E — Risk Monitoring

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
4Assessment objectives
3Assessment methods

03.12 — Security Assessment and Monitoring · NIST SP 800-172 Revision 3

Active
Official NIST requirement content

Security requirement

Ensure risk monitoring is an integral part of the continuous monitoring strategy that includes effectiveness monitoring, compliance monitoring, change monitoring.

Official NIST discussion

Discussion

Risk monitoring is guided and informed by the established organizational risk tolerance. Effectiveness monitoring determines the ongoing effectiveness of the implemented risk response measures. Compliance monitoring verifies that required risk response measures are implemented. It also verifies that security requirements are satisfied. Change monitoring identifies changes to organizational systems and environments of operation that may affect security risk. This requirement enhances SP 800-171 requirement 03.12.03.

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 Risk Monitoring 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 assessment planning, evidence quality, remediation, continuous monitoring, and system security plan accuracy.

  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

  • assessment plans and reports
  • plans of action and milestones
  • system security plans
  • continuous monitoring results

Common failure patterns

  • requirement status based only on owner assertion
  • findings closed without evidence
  • scope missing inherited services
  • monitoring data disconnected from risk decisions
Official NIST SP 800-172A content

Assessment objectives and methods

Assessment objectives (4)

  1. risk monitoring is an integral part of the continuous monitoring strategy.

  2. effectiveness monitoring is included in risk monitoring.

  3. compliance monitoring is included in risk monitoring.

  4. change monitoring is included in risk monitoring.

Examine

  • Assessment and monitoring policy
  • organizational continuous monitoring strategy
  • system-level continuous monitoring strategy
  • procedures addressing continuous monitoring of system
  • assessment report
  • plan of action and milestones
  • system monitoring records
  • impact analyses
  • status reports
  • system security plan
  • other relevant documents or records

Interview

  • Personnel with continuous monitoring responsibilities
  • personnel with information security responsibilities

Test

  • Mechanisms supporting risk monitoring
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 controlCA-7(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.