EvidenceSheet

12.1.1 Overall information security policy established and disseminated

The organisation must have one overarching information security policy that is formally set up, made available in published form, kept under maintenance, and distributed to every relevant member of personnel and to vendors and business partners who are relevant. The guidance defines 'relevant' as anyone whose role, internal or as an outside provider of services or functions, touches some or all of the topics the policy addresses. The guidance explains that this top-level policy governs the more specific technical and discipline policies beneath it. Objective under the customized approach: the strategic aims and principles of information security are set out, formally adopted, and understood by everyone who works for the entity.

Source: PCI DSS v4.0.1, 12.1.1. 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
1
held by a system
1
at each review
moderate
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

  • Policy maintenance history showing changes over time · Policy repository / GRC workspace

periodic reviewEvidence produced at each review

  • Distribution records to staff and to relevant vendors and business partners · Vendor register / contract repository

governing documentDocuments that govern the control

  • Approved overarching information security policy with version and owner · Policy repository / GRC workspace
  • Policy publication location (intranet page or document portal) and access records · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.

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.6.1 Payment page tamper detection · 12.1.2 Security policy reviewed annually and updated as needed