We e-mail the editable toolkit files to the address you gave, usually within 2 to 3 business days.
Cyber Security

What Documents You Need for PCI DSS 4 Implementation

What Documents You Need for PCI DSS 4 Implementation
In short

A practical list of the policies, procedures, diagrams, inventories and records you need to implement and evidence PCI DSS 4 requirements.

In this article
  1. Start with the document hierarchy
  2. Policy-level documents
  3. Scope and inventory documents
  4. Procedures, standards and role assignments
  5. Documents that are new or more prominent in PCI DSS 4
  6. Records and evidence to retain
  7. Practical tips for managing the document set
  8. Frequently asked questions

Most PCI DSS projects stall on documentation rather than technology. Firewalls and encryption may already be in place, but nobody can show who owns them, how they are reviewed, or what the cardholder data environment (CDE) actually includes.

PCI DSS 4 is explicit about this. Nearly every requirement expects defined processes, documented roles and responsibilities, and evidence that the activity happens. This article sets out the documents you need, grouped so you can plan the work.

Start with the document hierarchy#

PCI DSS does not prescribe a document template or a fixed list of file names. It prescribes outcomes, and your documents show how you meet them. A simple four-layer structure works well:

  1. Policies: management's high-level intent and rules.
  2. Standards and procedures: the specific, repeatable steps for each control.
  3. Scope and design documents: diagrams, inventories and data-flow records.
  4. Records and evidence: logs, review sign-offs, test results and training records.

Assessors will test the bottom layer hardest. A well-written procedure with no evidence of operation will not carry you through an assessment.

Policy-level documents#

Requirement 12 of the standard centres on an information security policy that is published, maintained, communicated and reviewed. Beyond that overarching policy, plan for topic-specific policies or standards covering:

  • Acceptable use of end-user technologies
  • Access control and authentication, including password and MFA rules
  • Network security and configuration standards
  • Data retention, storage and secure disposal of cardholder data
  • Cryptography and key management
  • Vulnerability and patch management
  • Secure development and change management
  • Logging, monitoring and time synchronisation
  • Incident response
  • Third-party service provider management
  • Security awareness and personnel screening

You can combine some of these into a single policy if your organisation is small. What matters is that each requirement area has a clear, approved owner and a review cycle.

Scope and inventory documents#

Scoping errors cause more assessment pain than almost anything else. PCI DSS 4 expects you to document and confirm your scope, and not simply assume it. The documents that support this include:

  • Network diagram(s): showing connections into and out of the CDE and other connected systems.
  • Account data flow diagram(s): showing how card data is received, processed, stored and transmitted.
  • Inventory of system components: servers, network devices, applications, databases and cloud services in scope, with purpose and owner.
  • Inventory of bespoke and custom software and third-party components used in it.
  • Data storage inventory: where cardholder data is kept, why, and for how long.
  • Scope confirmation record: a dated, reviewed statement of what is in and out of scope, and why.
  • Inventory of cryptographic cipher suites and protocols in use, where relevant to your environment.

Keep diagrams current. An outdated diagram is worse than none, because it shows the assessor that change control is not working.

Procedures, standards and role assignments#

PCI DSS 4 repeatedly expects that roles and responsibilities for performing activities in each requirement are documented, assigned and understood. A responsibility matrix is the simplest way to satisfy this across all twelve requirements.

Beyond that, document operational procedures for the activities that recur:

AreaTypical documents
Network security controlsConfiguration standards, rule-set review procedure, change approval process
Secure configurationHardening standards, vendor default account handling
Protecting stored dataRetention schedule, disposal procedure, key management procedures
Vulnerability managementPatch procedure, scanning schedule, risk-ranking method
Secure developmentSecure coding guidelines, code review process, change control, separation of environments
Access controlUser provisioning and removal, periodic access review, MFA procedure
Logging and monitoringLog review procedure, alert handling, retention rules
Security testingInternal and external scan process, penetration testing methodology, segmentation testing
OrganisationalRisk assessment method, incident response plan, awareness programme, third-party management

Documents that are new or more prominent in PCI DSS 4#

If you are moving from the previous version, expect extra paperwork in these areas. The future-dated requirements have now taken effect, so they are no longer optional improvements.

  • Targeted risk analyses: where the standard lets you define how often a control is performed, you must document the risk analysis behind that frequency. Keep a template and a register of completed analyses.
  • Customised approach documentation: if you choose this over the defined approach for any requirement, you need a control matrix and a targeted risk analysis. Most organisations use the defined approach and can skip this.
  • Scope confirmation and review: documented at a defined interval and after significant change.
  • Payment page script management: an inventory of scripts, with written justification and authorisation for each, if you have e-commerce pages.
  • Phishing and social engineering awareness: training content and records that address these threats.
  • Service provider responsibility matrices: a written statement of which PCI DSS requirements you manage and which your providers manage.

Check the exact wording in the current published standard before finalising any of these. The requirements have specifics on frequency and content.

Records and evidence to retain#

Evidence turns documentation into proof. Build a simple evidence folder structure that mirrors the twelve requirements, and capture items such as:

  • Firewall and router rule review sign-offs
  • Quarterly internal and external vulnerability scan reports and rescans
  • Penetration test and segmentation test reports with remediation tracking
  • User access review records and joiner, mover and leaver tickets
  • Change records with security impact assessment and approval
  • Log review records and alert investigation tickets
  • Security awareness attendance and completion records
  • Incident response test records and any real incident reports
  • Third-party agreements, due diligence records and compliance status evidence
  • Attestation of Compliance (AOC) and the Report on Compliance or Self-Assessment Questionnaire, as applicable

Date every record and name the reviewer. If a task is meant to happen quarterly, four dated records are far more convincing than a description of the schedule.

Practical tips for managing the document set#

  • Map each document to requirements. A cross-reference table helps you answer assessor questions quickly.
  • Assign an owner and review date to every document, and put version control in place.
  • Reuse what you have. If you already run an ISO 27001 management system, much of the policy layer can be adapted. Privacy-related overlaps are covered in our guide to ISO 27701 documentation.
  • Keep procedures realistic. Write what your teams actually do, then improve it, instead of copying generic text nobody follows.

Frequently asked questions#

Does PCI DSS 4 require a specific list of mandatory documents?#

No fixed list exists. The standard requires policies, procedures, inventories, diagrams and evidence across its twelve requirements, and your assessor will test that these exist and operate. The set described above reflects what is typically needed.

How many documents will a small merchant need?#

It depends on your validation type and how card data reaches you. A merchant that fully outsources payment processing will have a much smaller scope and a lighter set than a service provider that stores or processes card data. Confirm your SAQ or assessment type first, then size the documentation to match.

Can one policy cover several requirements?#

Yes, provided it clearly addresses each requirement's expectations, names owners, and is reviewed on schedule. Many organisations use one information security policy with supporting standards and procedures.

If you would rather not draft every policy and procedure from scratch, the PCI DSS 4 Toolkit offers a ready-to-use documentation starting point that you can adapt to your own environment.

Share this guide

Ready to put this into practice?

Start with the PCI DSS 4 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp