FedRAMP Moderate IR-4(1): Automated Incident Handling Processes

What else in your programme already covers this

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

CIS Controls v8 · 4 controls

CIS-13.1 Centralize Security Event Alerting
CIS-13.8 Deploy a Network Intrusion Prevention Solution
CIS-17.4 Establish and Maintain an Incident Response Process
CIS-8.9 Centralize Audit Logs

ISO 27001:2022 · 4 controls

5.24 Information security incident management planning and preparation
5.26 Response to information security incidents
8.15 Logging
8.16 Monitoring activities

ISO 27002:2022 · 4 controls

5.24 Information security incident management planning and preparation
5.26 Response to information security incidents
8.16 Monitoring activities
8.7 Protection against malware

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-DE.AE-08 Incidents are declared when adverse events meet the defined incident criteria
NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared
NIST-CSF-RS.MI-01 Incidents are contained
NIST-CSF-RS.MI-02 Incidents are eradicated

SOC 2 · 3 controls

SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
SOC2-CC7.4 CC7.4 Responding to security incidents

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-28 Continuous incident detection and response (Excellent)

AWS Well-Architected Security Pillar · 1 control

SEC10-BP06 Pre-deploy tools

Azure Security Benchmark · 1 control

ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling

C5 (Germany) · 1 control

C5-SIM-02 Processing of security incidents

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-03 Incident Response Plans

NIST SP 800-171 Rev 3 · 1 control

03.06.01 Incident Handling

NIST SP 800-172 · 1 control

3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-53 Rev 5 · 1 control

NIST800-IR-4 IR-4 Incident Handling

NIST SP 800-53 Rev 5 HIGH · 1 control

IR-4(1) IR-4(1) Incident Handling | Automated Incident Handling Processes

NIST SP 800-53 Rev 5 MODERATE · 1 control

IR-4(1) IR-4(1) Incident Handling | Automated Incident Handling Processes

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 FedRAMP Moderate have you already done?

FedRAMP Moderate IR-4(1) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

If you hold ISO 27002:202256.3% covered · 141 gaps If you hold PCI DSS 4.051.1% covered · 158 gaps If you hold ISO 27001:202249.8% covered · 162 gaps If you hold NIST SP 800-171 Rev 345.5% covered · 176 gaps If you hold C5 (Germany)37.2% covered · 203 gaps If you hold CMMC 2.035% covered · 210 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. 348 were rejected on the ISO 27002:2022 pair alone.

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