AWS Well-Architected Security Pillar SEC04-BP04: Initiate remediation for non-compliant resources

What else in your programme already covers this

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

ISO 27001:2022 · 5 controls

5.26 Response to information security incidents
5.36 Compliance with policies, rules and standards for information security
8.16 Monitoring activities
8.8 Management of technical vulnerabilities
8.9 Configuration management

ISO 27002:2022 · 4 controls

5.26 Response to information security incidents
5.36 Compliance with policies, rules and standards for information security
8.16 Monitoring activities
8.9 Configuration management

NIST Cybersecurity Framework 2.0 · 4 controls

NIST-CSF-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated
NIST-CSF-PR.PS-01 Configuration management practices are established and applied
NIST-CSF-RS.MI-01 Incidents are contained
NIST-CSF-RS.MI-02 Incidents are eradicated

NIST SP 800-53 Rev 5 · 4 controls

NIST800-CA-5 CA-5 Plan of Action and Milestones
NIST800-CA-7 CA-7 Continuous Monitoring
NIST800-SI-2 SI-2 Flaw Remediation
NIST800-SI-4 SI-4 System Monitoring

Azure Security Benchmark · 3 controls

ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling
ASBv3-PV-4 Audit and enforce secure configurations for compute resources
PV-2 Audit and enforce secure configurations

CMMC 2.0 · 3 controls

CA.L2-3.12.3 Security Control Monitoring
CM.L2-3.4.2 Security Configuration Enforcement
RA.L2-3.11.3 Vulnerability Remediation

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

CCM-CCC-07 Detection of Baseline Deviation
CCM-LOG-05 Audit Logs Monitoring and Response
CCM-TVM-03 Vulnerability Remediation Schedule

NIST SP 800-161 Rev 1 · 3 controls

161R1-CM-6 Configuration Settings
161R1-RA-7 Risk Response
161R1-SI-2 Flaw Remediation

PCI DSS 4.0 · 3 controls

10.4.3 10.4.3 Exceptions and anomalies from log review addressed
10.7.1 10.7.1 Service providers detect critical control failures (superseded)
10.7.2 10.7.2 Detect and alert on critical security control failures

C5 (Germany) · 2 controls

C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept
C5-OPS-22 Testing and Documentation of known Vulnerabilities

CIS Controls v8 · 2 controls

CIS-4.6 Securely Manage Enterprise Assets and Software
CIS-7.7 Remediate Detected Vulnerabilities

FedRAMP Moderate · 2 controls

CM-6(1) Automated Management, Application, and Verification
RA-7 Risk Response

NIST SP 800-171 Rev 3 · 2 controls

03.11.04 Risk Response
03.12.03 Continuous Monitoring

SOC 2 · 2 controls

SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

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

ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions

FedRAMP High · 1 control

CM-6(1) Automated Management, Application, and Verification

HIPAA Security Rule · 1 control

164.308(a)(1)(ii)(B) Risk Management (Required)

NIST SP 800-218 · 1 control

SP800-218-RV.2.1 Assess, Prioritize, and Remediate Vulnerabilities

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(1)(ii)(B) Risk Management (Required)

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 AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC04-BP04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gaps If you hold ISO 27002:202273% covered · 17 gaps If you hold FedRAMP Moderate69.8% covered · 19 gaps If you hold Azure Security Benchmark65.1% covered · 22 gaps If you hold PCI DSS 4.063.5% covered · 23 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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