NIST Cybersecurity Framework 2.0
DE - Detect

NIST Cybersecurity Framework 2.0 NIST-CSF-DE.AE-04: The estimated impact and scope of adverse events are understood

The estimated impact and scope of adverse events are understood

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 6 controls

CIS Controls v8 · 5 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-13.6 Collect Network Traffic Flow Logs
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-17.9 Establish and Maintain Security Incident Thresholds
  • CIS-8.11 Conduct Audit Log Reviews

FedRAMP High · 5 controls

  • IR-1 Policy and Procedures
  • IR-4 Incident Handling
  • IR-9 Information Spillage Response (IR-9)
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))
  • RA-3 Risk Assessment

FedRAMP Moderate · 5 controls

  • IR-1 Policy and Procedures
  • IR-4 Incident Handling
  • IR-9 Information Spillage Response (IR-9)
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))
  • RA-3 Risk Assessment

ISO 27001:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.25 Assessment and decision on information security events
  • 5.26 Response to information security incidents
  • 5.28 Collection of evidence

ISO 27701:2019 · 4 controls

  • 5.6.2 Information security risk assessment
  • 5.7.1 Monitoring, measurement, analysis and evaluation
  • 6.13.1 Management of information security incidents and improvements
  • 6.14.1 Information security continuity

ISO/IEC 42001:2023 · 3 controls

  • 6.1.2 AI risk assessment
  • 9.1 Monitoring, measurement, analysis and evaluation
  • A.5 Assessing impacts of AI systems

SOC 2 · 3 controls

  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents

CMMC 2.0 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

  • ASD37-28 Continuous incident detection and response (Excellent)
  • ASBv3-IR-5 Detection and analysis - prioritize incidents

C5 (Germany) · 1 control

DORA · 1 control

  • DORA-Art.18 Classification of ICT-related incidents and cyber threats

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

  • 8.2.2 Business impact analysis

ISO 27002:2022 · 1 control

  • 5.25 Assessment and decision on information security events

NIS2 Directive · 1 control

  • Art.23.4.b Submit an incident notification within 72 hours, with an initial assessment and indicators of compromise
  • DE.AE-4 DE.AE-4: Impact of events is determined
  • DE.AE-4 DE.AE-4: Impact of events is determined

NIST SP 800-172 · 1 control

  • 3.11.3e Advanced Automation and Analytics Capabilities
  • DE.AE-04 DE.AE-04 Impact and scope of adverse events estimated and refined

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 DE - Detect

You are reading one control. How much of NIST Cybersecurity Framework 2.0 have you already done?

NIST Cybersecurity Framework 2.0 NIST-CSF-DE.AE-04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST Cybersecurity Framework 2.0 your existing evidence covers. Hold ISO 27001:2022 and 73 of 106 NIST Cybersecurity Framework 2.0 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. 174 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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