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

2.2.5 Insecure services, protocols or daemons secured

Where any insecure service, protocol or daemon is present on system components: (a) the business justification is documented; and (b) additional security features that lower the risk of using them are documented and implemented. The guidance recommends enabling security features before new components are deployed, so insecure configurations do not enter the environment. Applicability: no special notes; applies to every assessed entity. Customized approach objective: no insecure service, protocol or daemon can be used as a route to compromise system components.

Source: PCI DSS v4.0.1, 2.2.5. 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
Cloud console / configuration management
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

  • Configuration evidence that those features are active on the affected systems · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Interview notes with system owners confirming justification is current · Cloud console / configuration management

governing documentDocuments that govern the control

  • Register of insecure services, protocols and daemons present on system components, with business justification · Policy repository / GRC workspace
  • Documented additional security features for each (for example wrapping in an encrypted tunnel, host restrictions) · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); 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

2.2.4 Only necessary functionality enabled · 2.2.6 System security parameters configured against misuse