Skip to main content

IRO-07.1: Automated Reporting

IRO 9 — Critical Detect

Automated mechanisms exist to assist in the reporting of cybersecurity and data protection incidents.

Renumbered: Formerly IRO-10.1 in SCF 2025.4.

Control Question: Does the organization use automated mechanisms to assist in the reporting of cybersecurity and data protection incidents?

General (11)
Framework Mapping Values
GovRAMP IR-06(01)
GovRAMP Core IR-06(01)
GovRAMP Moderate IR-06(01)
GovRAMP High IR-06(01)
NIST 800-53 R4 IR-6(1)
NIST 800-53 R5.2 IR-06(01)
NIST 800-53B R5 (moderate) (source) IR-06(01)
NIST 800-53B R5 (high) (source) IR-06(01)
NIST 800-82 R3 IR-06(01)
NIST 800-82 R3 MODERATE OT Overlay IR-06(01)
NIST 800-82 R3 HIGH OT Overlay IR-06(01)
US (5)

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.

Level 2 — Planned & Tracked

SCR-CMM Level 2 criteria definitions are not available for this control: ▪ A reasonable person would conclude a well-defined and standardized process is required. ▪ At this level of maturity, the “requirements-driven” nature of performing the control is focused on a localized and/or regionalized implementation, not uniform and consistent across the organization. ▪ Requirements are narrowly scoped for applicability and are primarily derived from compliance obligations (e.g., laws, regulations and contracts).

Level 3 — Well Defined

Incident Response (IRO) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IRO domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Cybersecurity personnel operate an incident response capability using a documented and tested Incident Response Plan (IRP) to facilitate incident management operations that cover preparation, detection and analysis, containment, eradication and recovery. ▪ An incident response team, or similar function, is appropriately staffed and supported to implement and maintain IRO domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of incident response operations (e.g., incident management software). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IRO domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to automatically assist in the reporting of cybersecurity and data protection incidents.

Level 4 — Quantitatively Controlled

Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. IRO-07.1_A01 automated mechanisms used for reporting incidents are defined.
  2. IRO-07.1_A02 incidents are reported using automated mechanisms.

Technology Recommendations

Micro/Small

  • Basic incident response plan
  • Designate incident response contact

Small

  • Documented incident response plan
  • Incident log
  • Designated IR team

Medium

  • Formal incident response program
  • IR playbooks
  • Tabletop exercises

Large

  • Enterprise incident response program
  • 24/7 SOC monitoring
  • SOAR platform

Enterprise

  • Enterprise SOC with SIEM/SOAR (e.g., Splunk SOAR, Palo Alto XSOAR)
  • IR retainer
  • Threat hunting

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.