EvidenceSheet

11.1.2 Roles for security testing assigned and understood

The responsibilities for carrying out each activity in Requirement 11 must be written down, allocated to named roles or people, and understood by those people. Illustrative scope: who runs internal and external scans, who commissions and reviews penetration tests, who watches IDS/IPS and change-detection alerts, and who handles wireless access point detection. Guidance (good practice): roles can sit inside the policies and procedures or in a separate document such as a RACI matrix, and entities can consider having staff acknowledge their assignments. Customized approach objective: day-to-day duties for all Requirement 11 activities are allocated and personnel are held accountable for their ongoing, successful operation.

Source: PCI DSS v4.0.1, 11.1.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

4
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Signed acknowledgements from personnel accepting their testing duties · HR system / LMS
  • Interview notes confirming staff can describe their Requirement 11 tasks · Document repository

governing documentDocuments that govern the control

  • RACI matrix or role descriptions covering each Requirement 11 activity · Policy repository / GRC workspace
  • Job descriptions or assignment letters for scan, pentest and alert-monitoring owners · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

11.1.1 Requirement 11 policies and procedures managed · 11.2.1 Detect authorized and rogue wireless access points