The Payment Card Industry Security Standards Council has published the latest version of the data security standards it administers and highlighted what is new.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Version 3.0 becomes effective on 1 January 2014, but V2.0 will remain active until 31 December 2014 to ensure organisations have adequate time to make the transition.
The latest version is aimed at helping organisations make payment security part of their business-as-usual activities by introducing more flexibility.
There is also an increased focus on education, awareness and security as a shared responsibility.
New requirements for PCI DSS include:
- 5.1.2 - evaluate evolving malware threats for any systems not considered to be commonly affected;
- 8.2.3 - combined minimum password complexity and strength requirements into one, and increased flexibility for alternatives;
- 8.5.1 - for service providers with remote access to customer premises, use unique authentication credentials for each customer;
- 8.6 - where other authentication mechanisms are used (for example, physical or logical security tokens, smart cards, certificates) these must be linked to an individual account and ensure only the intended user can gain access;
- 9.3 - control physical access to sensitive areas for onsite personnel, including a process to authorise access, and revoke access immediately upon termination;
- 9.9 - protect devices that capture payment card data via direct physical interaction with the card from tampering and substitution;
- 11.3 and 11.3.4 - implement a methodology for penetration testing. If segmentation is used to isolate the cardholder data environment from other networks, perform penetration tests to verify that the segmentation methods are operational and effective;
- 11.5.1 - implement a process to respond to any alerts generated by the change-detection mechanism;
- 12.8.5 - maintain information about which PCI DSS requirements are managed by each service provider, and which are managed by the entity;
- 12.9 - for service providers, provide the written, agreement/acknowledgment to their customers as specified at requirement 12.8.2.
Read more about PCI DSS
- Latest version of PCI DSS reaches final stages
- Analysis: What’s PCI DSS V3.0 all about?
- Has your project got stuck PCI syndrome?
- PCI QSA analysis: PCI DSS 3.0 to bring new PCI challenges, benefits
- The history of the PCI DSS standard: A visual timeline
- Podcast: PCI SSC's Bob Russo, Troy Leach on PCI DSS 3.0 changes
- Using encryption technology to achieve PCI DSS compliance objectives
- Podcast: What’s new in PCI-DSS and PA-DSS version 3.0?
- Understanding the PCI DSS prioritized approach to compliance
New requirements for PA DSS include:
- 5.1.5 – payment application developers to verify integrity of source code during the development process;
- 5.1.6 – payment applications to be developed according to industry best practice for secure coding techniques;
- 5.4 - payment application suppliers to incorporate versioning methodology for each payment application;
- 5.5 - payment application suppliers to incorporate risk assessment techniques into their software development process;
- 7.3 - application supplier to provide release notes for all application updates;
- 10.2.2 - suppliers with remote access to customer premises (for example, to provide support/maintenance services) use unique authentication credentials for each customer;
- 14.1 – provide information security and PA-DSS training for supplier personnel with PA-DSS responsibility at least annually.