Encryption Requirements for PCI Compliance in 2025
Complete guide to implementing encryption for PCI Compliance in 2025. Understand must-haves and some practical strategies to maintain compliance.
The Payment Card Industry Data Security Standard (PCI DSS) is a mandatory set of security measures designed to ensure that all companies that accept, process, store, or transmit credit card information maintain a secure environment. This standard is crucial for protecting payment data and maintaining customer trust and is enforced primarily by acquiring banks and card brands.
Complying with PCI DSS can be daunting due to its complexity and required resources. Audits in the US, for instance, can be expensive, with costs varying significantly depending on the size and complexity of the environment being audited and penetration tested, but don’t be surprised at invoices north of $65,000. Beyond the financial aspect and licensing software, the implementation, ongoing maintenance, and monitoring of the required controls demand substantial time and effort from internal teams. The table below is an informed estimate of complexity and effort across the 12 PCI DSS requirements for a large eCommerce business that develops its code, processes, stores card data, and operates in its own data centre. The effort is aggregated across roles, including Network Admin, System Admin, DBA, Security Operations, Developers, Change Managers, Info Sec / Compliance and Payments teams.
Requirement | Level of Effort/Cost | Level of Complexity | Estimated FTE Work Days |
---|---|---|---|
1. Firewall Configuration | Medium | High | 15 |
2. Secure Configurations | Medium | High | 20 |
3. Protect Stored Data | High | Very High | 20 |
4. Encrypt Transmissions | Medium | Medium | 10 |
5. Malware Protection | Medium | Medium | 15 |
6. Secure Systems/Applications | Very High | Very High | 45 |
7. Access Restriction | Medium | High | 15 |
8. Identify/Authenticate Access | High | High | 15 |
9. Physical Access Control | Medium | Medium | 10 |
10. Logging and Monitoring | Very High | High | 40 |
11. Security Testing | High | High | 25 |
12. Information Security Policy and IR | Medium | Medium | 20 |
Total: 250 |
For certain payment processing models, using Evervault would reduce this effort significantly, in most cases by 95% above across a much-reduced set of roles and covering basic security hygiene. The stakes are high for card processing companies; a breach can lead to fines of up to $18 per compromised card, potential cessation of card processing capabilities by card brands, and severe damage to customer trust due to the theft of cardholder data (CHD). It’s worth remembering that Target settled their 2015 card breach for $39.4m and British Airways 2018 breach for $26m.
The approach to PCI compliance varies by business type and necessity for handling card data. For many businesses, especially those not primarily in the financial sector, handling card data directly may not be essential. In such cases, reducing the PCI DSS scope becomes a strategic priority to minimise the compliance burden and reduce the risk of card breaches. There are also opportunities for FinTechs to minimise the likelihood of cardbreach, reduce scope and ease the compliance burden while maintaining control over the flow of card data for payment orchestration and optimisation.
When considering outsourcing card processing to a third party, it is crucial for organizations to conduct thorough due diligence, assess the alignment of the service provider's capabilities with their specific needs, and ensure contractual agreements comprehensively address security, compliance, and service delivery expectations.
Compliance with PCI DSS can be achieved through two main pathways: Self-Assessment Questionnaires (SAQs) and Report on Compliance (ROC) by a Qualified Security Assessor (QSA).
Whether you can self-assess depends on the volume of transactions (cards you process) per year. Service Providers processing <300k p/a are Level 2 and can self-assess;> 300k p/a are Level 1 and must have a QSA validate their environment in a Report on Compliance (RoC).
For merchants, it's slightly different; there are four levels, and a QSA is only required to validate compliance in an RoC once >6m transactions p/a are processed. Otherwise, self-assessment using one of the many types of SAQ is acceptable to acquirers.
There are many different SAQs, depending on how card data is processed (web only, face-to-face, etc) and the volume of cards processed per year. A detailed description of the SAQs from the PCI Council is here.
Using services like Evervault can significantly descope the environment from many PCI DSS requirements, aligning it more closely with the simplified controls outlined in SAQ A (<30 Controls) for most use cases. Evervault's payment security services ensure that sensitive cardholder data is encrypted before it enters the business environment, effectively removing the data from the business's PCI DSS scope. This reduces the compliance burden and mitigates the breach risk associated with storing and processing cardholder data directly.
In summary, while PCI DSS compliance is essential for businesses handling cardholder data, its complexity and resource demands make scope reduction an attractive strategy. Utilizing solutions like Evervault can streamline compliance efforts, reduce costs, and enhance overall data security, allowing businesses to focus more on their core operations and less on the intricacies of PCI DSS compliance.
With Evervault's PCI solution, you can reduce your PCI scope, saving you time and money.
Learn more