NIST SP 800-172
IR

NIST SP 800-172 3.6.1e: Establish Security Operations Center (SOC)

Establish and maintain a security operations center that operates 24/7, with allowance for remote/on-call staff.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 43 controls across 17 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy
  • ASBv3-IR-2 Preparation - setup incident notification
  • ASBv3-IR-3 Detection and analysis - create incidents based on high-quality alerts
  • ASBv3-IR-4 Detection and analysis - investigate an incident
  • ASBv3-IR-5 Detection and analysis - prioritize incidents
  • LT-5 Centralize security log management and analysis
  • NIST-CSF-DE.AE-02 Potentially adverse events are analyzed to better understand associated activities
  • NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident
  • NIST-CSF-RS.MA-02 Incident reports are triaged and validated

NIST SP 800-161 Rev 1 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

FedRAMP High · 3 controls

  • IR-5 Incident Monitoring
  • IR-7 Incident Response Assistance
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))

FedRAMP Moderate · 3 controls

  • IR-5 Incident Monitoring
  • IR-7 Incident Response Assistance
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))

C5 (Germany) · 2 controls

  • C5-OPS-17 Logging and Monitoring - Availability of the Monitoring Software
  • C5-SIM-01 Policy for security incident management

CIS Controls v8 · 2 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-17.9 Establish and Maintain Security Incident Thresholds

ISO 27001:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.25 Assessment and decision on information security events

ISO 27002:2022 · 2 controls

  • 5.24 Information security incident management planning and preparation
  • 5.25 Assessment and decision on information security events

NIST SP 800-171 Rev 3 · 2 controls

  • 03.06.01 Incident Handling
  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance

SOC 2 · 2 controls

  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

PCI DSS 4.0 · 1 control

  • 12.10.3 12.10.3 Incident response personnel available 24/7

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in IR

You are reading one control. How much of NIST SP 800-172 have you already done?

NIST SP 800-172 3.6.1e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 5 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 43 it maps to, and the evidence behind each claim, over MCP and REST.