Compliancemanzill.com
PCI DSS v4.0

PCI DSS v4.0/Requirement 11: Test Security of Systems and Networks Regularly/203 of 250

11.4.1External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected

Control family: Requirement 11: Test Security of Systems and Networks Regularly

Control description

Defined Approach Requirements:

A penetration testing methodology is defined, documented, and implemented by the entity, and includes:

- Industry-accepted penetration testing approaches.

- Coverage for the entire CDE perimeter and critical systems.

- Testing from both inside and outside thenetwork.

- Testing to validate any segmentation and scope?reduction controls.

- Application-layer penetration testing to identify, at a minimum, the vulnerabilities listed in Requirement 6.2.4.

- Network-layer penetration tests that encompass all components that support network functions as well as operating systems.

- Review and consideration of threats and vulnerabilities experienced in the last 12 months.

- Documented approach to assessing and addressing the risk posed by exploitable vulnerabilities and security weaknesses found during penetration testing.

- Retention of penetration testing results and remediation activities results for at least 12 months.

Defined Approach Testing Procedures:

11.4.1 Examine documentation and interview personnel to verify that the penetration-testing methodology defined, documented, and implemented by the entity includes all elements specified in this requirement.

How to implement

Coming in phase 2Step-by-step guidance for implementing this control on Microsoft Azure, using services such as Azure Policy, Microsoft Defender for Cloud and Entra ID. It will be matched to your environment.