AWS Well-Architected Security Pillar SEC11-BP03: Perform regular penetration testing

What else in your programme already covers this

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

PCI DSS 4.0 · 6 controls

11.4.1 11.4.1 Penetration testing methodology defined and implemented
11.4.2 11.4.2 Internal penetration testing annually and after change
11.4.3 11.4.3 External penetration testing annually and after change
11.4.4 11.4.4 Correct exploitable findings from penetration tests
11.4.5 11.4.5 Annual segmentation penetration testing
6.4.1 6.4.1 Public web application review or automated protection

CIS Controls v8 · 4 controls

CIS-16.13 Conduct Application Penetration Testing
CIS-18.1 Establish and Maintain a Penetration Testing Program
CIS-18.2 Perform Periodic External Penetration Tests
CIS-18.5 Perform Periodic Internal Penetration Tests

ISO 27001:2022 · 4 controls

5.35 Independent review of information security
8.29 Security testing in development and acceptance
8.34 Protection of information systems during audit testing
8.8 Management of technical vulnerabilities

ISO 27002:2022 · 4 controls

5.35 Independent review of information security
8.29 Security testing in development and acceptance
8.34 Protection of information systems during audit testing
8.8 Management of technical vulnerabilities

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-ID.IM-01 Improvements are identified from evaluations
NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
NIST-CSF-ID.RA-08 Processes for receiving, analyzing, and responding to vulnerability disclosures are established

NIST SP 800-161 Rev 1 · 3 controls

161R1-CA-2 Control Assessments
161R1-PM-14 Testing, Training, and Monitoring
161R1-SA-11 Developer Testing and Evaluation

CMMC 2.0 · 2 controls

CA.L2-3.12.1 Security Control Assessment
RA.L2-3.11.2 Vulnerability Scan

FedRAMP High · 2 controls

CA-8 Penetration Testing
CA-8(1) Penetration Testing | Independent Penetration Testing Agent or Team (CA-8(1))

FedRAMP Moderate · 2 controls

CA-8 Penetration Testing
CA-8(1) Penetration Testing | Independent Penetration Testing Agent or Team (CA-8(1))

NIST SP 800-171 Rev 3 · 2 controls

03.11.02 Vulnerability Monitoring and Scanning
03.12.01 Security Assessment

NIST SP 800-218 · 2 controls

SP800-218-PW.8.1 Executable Testing for Security
SP800-218-PW.8.2 Execute Security Testing

NIST SP 800-53 Rev 5 · 2 controls

NIST800-CA-8 CA-8 Penetration Testing
NIST800-SA-11 SA-11 Developer Testing and Evaluation

SOC 2 · 2 controls

SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
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

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-STEP4 Step 4 - Implement a formal controls assessment program

Azure Security Benchmark · 1 control

ASBv3-PV-7 Conduct regular red team operations

C5 (Germany) · 1 control

C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests

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

CCM-TVM-06 Penetration Testing

HIPAA Security Rule · 1 control

164.308(a)(8) Evaluation (Standard)

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(8) Evaluation (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 SEC11-BP03 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