AWS Well-Architected Security Pillar SEC01-BP06: Automate deployment of standard security controls

What else in your programme already covers this

This control maps to 61 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.

FedRAMP High · 7 controls

CM-2 Baseline Configuration
CM-2(2) Automation Support for Accuracy and Currency
CM-2(3) Retention of Previous Configurations
CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
CM-6 Configuration Settings
CM-6(1) Automated Management, Application, and Verification
SA-10 Developer Configuration Management

FedRAMP Moderate · 7 controls

CM-2 Baseline Configuration
CM-2(2) Automation Support for Accuracy and Currency
CM-2(3) Retention of Previous Configurations
CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
CM-6 Configuration Settings
CM-6(1) Automated Management, Application, and Verification
SA-10 Developer Configuration Management

PCI DSS 4.0 · 5 controls

1.2.1 1.2.1 Ruleset configuration standards for NSCs
1.2.8 1.2.8 NSC configuration files secured and consistent
2.2.1 2.2.1 System configuration standards maintained
2.2.6 2.2.6 System security parameters configured against misuse
6.5.2 6.5.2 Confirm PCI DSS controls after significant change

Azure Security Benchmark · 4 controls

ASBv3-GS-5 Define and implement security posture management strategy
ASBv3-PV-1 Define and establish secure configurations
DS-6 Enforce security of workload throughout DevOps lifecycle
PV-2 Audit and enforce secure configurations

CMMC 2.0 · 4 controls

CA.L2-3.12.3 Security Control Monitoring
CM.L2-3.4.1 System Baselining
CM.L2-3.4.2 Security Configuration Enforcement
SC.L2-3.13.2 Security Engineering

NIST SP 800-161 Rev 1 · 4 controls

161R1-CM-2 Baseline Configuration
161R1-CM-6 Configuration Settings
161R1-CM-9 Configuration Management Plan
161R1-PL-9 Central Management

C5 (Germany) · 3 controls

C5-DEV-03 Policies for changes to information systems
C5-DEV-08 Version Control
C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CIS Controls v8 · 3 controls

CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
CIS-4.1 Establish and Maintain a Secure Configuration Process
CIS-4.6 Securely Manage Enterprise Assets and Software

ISO 27001:2022 · 3 controls

8.27 Secure system architecture and engineering principles
8.32 Change management
8.9 Configuration management

ISO 27002:2022 · 3 controls

8.27 Secure system architecture and engineering principles
8.32 Change management
8.9 Configuration management

NIST SP 800-171 Rev 3 · 3 controls

03.04.01 Baseline Configuration
03.04.02 Configuration Settings
03.16.01 Security Engineering Principles

NIST SP 800-53 Rev 5 · 3 controls

NIST800-CM-2 CM-2 Baseline Configuration
NIST800-CM-3 CM-3 Configuration Change Control
NIST800-CM-6 CM-6 Configuration Settings

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate
ANSSI-HYG-16 Use a Centralised Management Tool to Standardise Security Policies

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

CCM-AIS-06 Automated Secure Application Deployment
CCM-CCC-06 Change Management Baseline

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
NIST-CSF-PR.PS-01 Configuration management practices are established and applied

NIST SP 800-218 · 2 controls

SP800-218-PO.3.2 Toolchain Configuration and Integration
SP800-218-PS.1.1 Protect All Forms of Code from Unauthorized Modification

SOC 2 · 2 controls

SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

HIPAA Security Rule · 1 control

164.308(a)(1)(i) Security Management Process (Standard)

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(1)(i) Security Management Process (Standard)

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 SEC01-BP06 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