Security Questionnaire Mapper

Penetration testing: the clause the question tests

Whether an independent tester attacks the service on a cycle, and what happened to the findings.

How the customer usually asks it

example

"Do you commission an independent penetration test of the service at least once a year?"

Read this question

Anchor clauses

3 frameworks
FrameworkAnchor clause
ISO/IEC 27001:20228.8 Management of technical vulnerabilities
SIG (Shared Assessments)domain P Threat Management
PCI DSS v4.0.111.4.3 External penetration testing annually and after change

Every framework that anchors this family is listed here; a register shows the ones ticked for the customer.

Evidence expected

The latest penetration test summary (tester, date, scope, findings by severity) and the remediation status of each finding.

The clauses, with what an assessor asks for

ISO 27001 8.8 Management of technical vulnerabilities

Obtain vulnerability information, evaluate exposure, and take appropriate remediation.

Evidence an assessor expects: Vulnerability feed logs; Risk assessment reports; Remediation ticket records; Patch deployment evidence
Where answers usually fall short: Relying on ad-hoc scans only; Missing documented risk ranking for vulnerabilities
Source: ISO/IEC 27001:2022
SIG domain P Threat Management

What it asks for, in one line (the standard's own text is not quoted here):

Maintain threat intelligence, vulnerability management, penetration testing, and red team capabilities to identify and remediate weaknesses in a timely manner.

Evidence an assessor expects: Threat intelligence sources and feeds; Vulnerability scan reports with remediation timelines; Annual external penetration test report; Red team or purple team exercise reports
Where answers usually fall short: Critical vulnerabilities open beyond SLA; Penetration test scope omits new applications
Source: SIG (Shared Assessments)
PCI DSS 11.4.3 External penetration testing annually and after change

What it asks for, in one line (the standard's own text is not quoted here):

External penetration testing must be performed: using the methodology the entity has defined; no less than annually; after every significant upgrade or change to infrastructure or applications; by a qualified tester, whether an internal resource or an external third party; and with organizational independence of the tester (a QSA or ASV is not required). Guidance (good practice): when selecting a tester, entities can weigh specialist penetration testing certifications and prior experience such as years in the field and the type and scope of past engagements. Objective under the customized approach: technical testing following the defined methodology verifies external defenses as often as needed to keep pace with new and evolving attacks and to confirm that significant changes bring in no unknown vulnerabilities.

Evidence an assessor expects: Latest external penetration test report, scope and engagement letter; Tests triggered by significant changes to internet-facing infrastructure or applications; Tester qualifications (certifications, experience summary); Independence confirmation for the tester; External asset inventory used to define scope
Where answers usually fall short: External test scoped to a handful of IPs, missing web applications; New internet-facing application launched without a test
Source: PCI DSS v4.0.1

Other families in operations, logging and vulnerability