EvidenceSheet
PCI DSS v4.0.1 · Req 2: Secure Configurations

2.1.1 Requirement 2 policies and procedures governed

Every security policy and operational procedure required under Requirement 2 (secure configuration of system components) must be written down, kept current, followed in practice, and known to every party it affects. This spans hardening standards, vendor default handling, function isolation and wireless configuration procedures. Applicability: no special notes; applies to every assessed entity. Customized approach objective: affected personnel understand and follow the defined expectations, controls and oversight for Requirement 2 work, and supporting activities are repeatable, consistent and in line with management's intent.

Source: PCI DSS v4.0.1, 2.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
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

  • Evidence of communication to system administrators, such as training records or intranet publication · HR system / LMS
  • Interview notes with system and platform owners describing how they apply the procedures · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • Secure configuration policy and hardening procedures covering Requirement 2, with version and review dates · Policy repository / GRC workspace
  • Document ownership register for Requirement 2 documents · 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

1.5.1 Security controls on dual-connected devices · 2.1.2 Requirement 2 roles and responsibilities assigned