If a company takes card payments — in a shop, online or through partners — PCI DSS applies to it. As the Payment Card Industry Security Standards Council (PCI SSC) puts it, the standard provides a baseline of technical and operational requirements designed to protect payment account data.
Below: who PCI DSS applies to, what requirements it consists of and what they mean for IT.
What PCI DSS is and who it applies to
PCI DSS (Payment Card Industry Data Security Standard) is developed by PCI SSC. According to the Council, it applies to entities that store, process or transmit cardholder data or sensitive authentication data, as well as those that could impact the security of the environment where that data is handled. That includes merchants, processors, acquirers, issuers and service providers.
- The current version is PCI DSS v4.0.1, published in June 2024. It adds no new requirements: it is a clarification of v4.0.
- Version 4.0 was retired on 31 December 2024.
- The new v4.0 requirements, which were initially best practices, have been mandatory since 31 March 2025.
PCI DSS is an industry standard, not a law. The form in which you confirm compliance — a self-assessment questionnaire (SAQ) or an assessment — depends on how you accept payments; check this with your acquiring bank.
12 requirements in six groups
| Group | Requirements |
|---|---|
| Build and maintain a secure network and systems | 1. Network security controls. 2. Secure configurations for all system components |
| Protect account data | 3. Protect stored account data. 4. Strong cryptography during transmission over open, public networks |
| Maintain a vulnerability management program | 5. Protection from malicious software. 6. Develop and maintain secure systems and software |
| Implement strong access control measures | 7. Access by business need to know. 8. Identify users and authenticate access. 9. Restrict physical access |
| Regularly monitor and test networks | 10. Log and monitor all access. 11. Test security of systems and networks regularly |
| Maintain an information security policy | 12. Organizational policies and programs for information security |
What it means for IT
The wording below follows the PCI DSS v4.0 Self-Assessment Questionnaire D published by PCI SSC.
- Vulnerability scanning. Internal — at least once every three months, with high-risk and critical vulnerabilities resolved and rescans performed (11.3.1). External — at least once every three months, by a PCI SSC Approved Scanning Vendor (ASV) (11.3.2). How to set up the process: “Vulnerability management: where to start”.
- Penetration testing. Internal and external — at least once every 12 months and after any significant infrastructure or application upgrade or change, by a qualified internal resource or qualified external third party; the tester must be organizationally independent (11.4.2, 11.4.3). See “Penetration testing: what it is, types and stages”.
- Multi-factor authentication — for all access into the cardholder data environment (8.4.2) and for all remote network access from outside that could access or impact it, for both personnel and third parties (8.4.3). See “Two-factor authentication for business”.
- Logging and monitoring of all access to systems and data (requirement 10) — see “SIEM vs SOC: the difference for business”.
- Protection from malicious software on all systems (requirement 5) — see “Antivirus vs EDR: what a business needs”.
- An incident response plan ready to be activated: roles, responsibilities, communications, including notifying payment brands and acquirers (12.10.1).
How to reduce the scope
The most effective way to simplify PCI DSS is to have fewer systems touching card data:
- do not store full card numbers if you can do without them;
- use the provider’s payment page or terminal, so card data does not pass through your servers;
- separate the cardholder data environment from the rest of the network;
- remove unnecessary access to that environment.
Where to start
- Understand the data flows: where card data appears, where it is sent, where it is stored.
- Define the boundaries of the cardholder data environment and shrink them where possible.
- Compare the current state with the requirements and list the gaps.
- Close the gaps: network segmentation, MFA, logs, scanning, penetration testing, policies.
- Confirm compliance in the form your acquirer requires.
- Keep it up: quarterly scans, penetration tests yearly and after changes, regular access reviews.
Checklist
- It is known exactly where card data passes and is stored
- The cardholder data environment is defined and minimised
- Internal scanning runs at least once every three months
- External scanning is done by a PCI SSC Approved Scanning Vendor (ASV)
- Internal and external penetration tests at least once every 12 months and after significant changes
- MFA for access to the cardholder data environment and for all remote access
- Access logs are collected and analysed
- An incident response plan is ready to be activated
How Bereg-IT can help
At an audit we assess which systems fall under PCI DSS, compare their state with the requirements and draw up a roadmap. Together with our partner, a Qualified Security Assessor (QSA) listed by the PCI SSC, we prepare you for the audit: the documentation and policies, and the technical controls. We carry out internal and external penetration tests with our own team, set up vulnerability management and network security on an NGFW, and SOC as a Service collects and analyses logs. The partner carries out the compliance audit (often called certification), and we stay with you through it and help close any findings; Bereg-IT does not certify on its own. External scanning for PCI DSS must be done by a PCI SSC Approved Scanning Vendor (ASV), and compliance is confirmed in the form your acquirer specifies.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- PCI Security Standards Council, PCI DSS: https://www.pcisecuritystandards.org/standards/pci-dss/
- PCI SSC Blog, Just Published: PCI DSS v4.0.1 (11.06.2024): https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1
- PCI SSC, Self-Assessment Questionnaire D for Merchants, PCI DSS v4.0 (April 2022) — requirements 8.4.2, 8.4.3, 11.3.1, 11.3.2, 11.4.2, 11.4.3, 12.10.1: https://listings.pcisecuritystandards.org/documents/PCI-DSS-v4-0-SAQ-D-Merchant.pdf