CIS Controls v8 CIS-17.9: Establish and Maintain Security Incident Thresholds

What else in your programme already covers this

This control maps to 41 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 · 5 controls

NIST800-AU-6 AU-6 Audit Record Review, Analysis, and Reporting
NIST800-CA-7 CA-7 Continuous Monitoring
NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-5 IR-5 Incident Monitoring
NIST800-IR-8 IR-8 Incident Response Plan

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-DE.AE-04 The estimated impact and scope of adverse events are understood
NIST-CSF-DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria
NIST-CSF-RS.MA-02 Incident reports are triaged and validated
NIST-CSF-RS.MA-03 Incidents are categorized and prioritized

APRA CPS 234 · 2 controls

CPS234-35 APRA Notification of Material Incidents within 72 Hours
CPS234-P24 Information Security Response Plans

Azure Security Benchmark · 2 controls

ASBv3-IR-3 Detection and analysis - create incidents based on high-quality alerts
ASBv3-IR-5 Detection and analysis - prioritize incidents

DORA · 2 controls

DORA-Art.17 ICT-related incident management process
DORA-Art.18 Classification of ICT-related incidents and cyber threats

FedRAMP High · 2 controls

IR-1 Policy and Procedures
IR-8 Incident Response Plan

FedRAMP Moderate · 2 controls

IR-1 Policy and Procedures
IR-8 Incident Response Plan

ISO 22301:2019 · 2 controls

8.4.2 Response structure
9.1 Monitoring, measurement, analysis and evaluation

ISO 27002:2022 · 2 controls

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

PCI DSS 4.0 · 2 controls

12.10.1 12.10.1 Incident response plan ready for activation
12.10.5 12.10.5 Plan covers alerts from security monitoring systems

SOC 2 · 2 controls

SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
SOC2-P6.6 P6.6 Notifying breaches and incidents

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-40 Define a Security Incident Management Procedure

APRA CPS 230 Operational Risk Management · 1 control

CPS230-P33 APRA Notification of Operational Risk Incidents within 72 Hours

Australia My Health Records Act 2012 · 1 control

MYHR-ENF-1 Mandatory data breach notification

Australian Information Security Manual · 1 control

ISM-1228 Analysing cyber security events for incidents

C5 (Germany) · 1 control

C5-OPS-13 Logging and Monitoring - Identification of Events

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-16 Security Incident Response Plan and Testing

CIS Controls v8.1 · 1 control

17.9 Establish and Maintain Security Incident Thresholds

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-SEF-06 Event Triage Processes

ISO 27001:2022 · 1 control

5.25 Assessment and decision on information security events

ISO 27701:2019 · 1 control

6.13.1 Management of information security incidents and improvements

NIST SP 800-171 Rev 3 · 1 control

03.06.01 Incident Handling

NIST SP 800-172 · 1 control

3.6.1e Establish Security Operations Center (SOC)

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.

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-17.9 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

If you hold ISO 27001:202266.7% covered · 51 gaps If you hold FedRAMP Moderate62.7% covered · 57 gaps If you hold NIST SP 800-53 Rev 557.5% covered · 65 gaps If you hold NIST Cybersecurity Framework 2.050.3% covered · 76 gaps If you hold ISO 27002:202249.7% covered · 77 gaps If you hold Azure Security Benchmark49% covered · 78 gaps

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. 240 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 each Browse the graph free