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.06.01E — Security Operations Center

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

03.06 — Incident Response · NIST SP 800-172 Revision 3

Active
Official NIST requirement content

Security requirement

Establish and maintain a security operations center.

Official NIST discussion

Discussion

A security operations center (SOC) is the focal point for security operations and computer network defense for an organization. The purpose of the SOC is to defend and monitor an organization’s systems and networks on an ongoing basis. The SOC is also responsible for detecting, analyzing, and responding to security incidents in a timely manner. The SOC is staffed with skilled technical and operational personnel (e.g., security analysts, incident response personnel, systems security engineers) and implements a combination of technical, management, and operational controls (including monitoring, scanning, and forensics tools) to monitor, fuse, correlate, analyze, and respond to threat and security-relevant event data from multiple sources. These sources include perimeter defenses, network devices (e.g., routers, switches), and endpoint agent data feeds. The SOC provides a holistic situational awareness capability to help organizations determine the security posture of the system and organization. A SOC capability can be obtained in a variety of ways. Larger organizations may implement a dedicated SOC, while smaller organizations may employ third-party organizations to provide this capability. This requirement enhances SP 800-171 requirement 03.06.01.

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
Bare Metal Cyber interpretation

Implementation perspective

Treat Security Operations Center 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 prepared detection, coordinated response, reporting, recovery, and lessons learned for incidents involving CUI.

  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

  • incident response plans and playbooks
  • case records and timelines
  • exercise and tabletop results
  • lessons-learned and corrective-action tracking

Common failure patterns

  • plans that do not match the current architecture
  • unclear authority for containment decisions
  • evidence lost during response
  • lessons learned recorded but not implemented
Official NIST SP 800-172A content

Assessment objectives and methods

Assessment objectives (2)

  1. a security operations center is established.

  2. a security operations center is maintained.

Examine

  • Incident response policy
  • contingency planning policy
  • procedures addressing incident handling
  • procedures addressing the security operations center operations
  • mechanisms supporting dynamic response capabilities
  • system security plan
  • contingency plan
  • incident response plan
  • other relevant documents or records

Interview

  • Personnel with incident handling responsibilities
  • personnel with information security responsibilities
  • security operations center personnel
  • personnel with contingency planning responsibilities

Test

  • Mechanisms that support and/or implement the security operations center capability
  • mechanisms that support and/or implement the incident handling process
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 controlIR-4(14)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.