PCI DSS Version 3.0 Released

PCI Security Standards Council (PCI SSC) has recently released Version 3.0 of the PCI Data Security Standard (PCI DSS) and Payment Application Data Security Standard (PA DSS). Organizations have one year (till December 31, 2014) to become compliant with the new standard.
 

The new requirements for PCI DSS are:
 
1.1.3 A Current diagram that shows cardholder data flows
2.4 Maintain an inventory of system components in scope for PCI DSS to support development of configuration standards.
5.1.2 Evaluate evolving malware threats for any systems not considered to be commonly affected by malicious software.

5.3 Ensure that anti-virus solutions are actively running (formerly in 5.2), and cannot be disabled or altered by users unless specifically authorized by management on a per-case basis.

6.5.10 Coding practices to protect against broken authentication and session management. Effective July 1, 2015
8.5.1 Service providers with remote access to customer premises, to use unique authentication credentials for each customer. Effective July 1, 2015
8.6 Where other authentication mechanisms are used (for example, physical or logical security tokens, smart cards, certificates, etc.) that the mechanisms must be linked to an individual account and ensure only the intended user can gain access with that mechanism.
9.3 Control physical access to sensitive areas for onsite personnel, including a process to authorize access, and revoke access immediately upon termination.

9.9.x Protect devices that capture payment card data via direct physical interaction with the card from tampering and substitution. Effective July 1, 2015
11.1.2 Align with an already existing testing procedure, for incident response procedures if unauthorized wireless access points are detected.
11.3 To implement a methodology for penetration testing. Effective July 1, 2015. PCI DSS v2.0 requirements for penetration testing must be followed until v3.0 is in place.
11.3.3 Created from former testing procedure (11.3.b) to correct exploitable vulnerabilities found during penetration testing and repeat testing to verify corrections.

11.3.4 If segmentation is used to isolate the CDE from other networks, to perform penetration tests to verify that the segmentation methods are operational and effective.
11.5.1 To implement a process to respond to any alerts generated by the change-detection mechanism (supports 11.5)

12.8.5 To maintain information about which PCI DSS requirements are managed by each service provider, and which are managed by the entity.

12.9 Service providers to provide the written agreement/acknowledgment to their customers as specified at requirement 12.8. Effective July 1, 2015
 
The new requirements for PA DSS are:
 
3.1.1 – 3.1.2 New requirements created from former Testing Procedures 3.1.b – 3.1.c to ensure that changing of default passwords is enforced by the application and appropriately validated.
3.4 Applications to limit access to required functions/resources and enforce least privilege for built-in application accounts.

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 practices for secure coding techniques
5.1.7 New requirement created from former Testing Procedures 5.2.a and 5.2.b for payment application developers to be trained in secure development
practices.

5.2.10 Address “Broken authentication and session management.”

5.4 Payment application vendor to define and implement a versioning methodology in accordance with PA-DSS Program Guide

5.5 Payment application vendors to incorporate risk assessment techniques into their software development process.
5.6 Payment application vendors to implement a formal authorization process prior to final release.
6.3 New Requirement 6.3 created from former Testing Procedure 6.2.b.
7.3 The application vendor to provide release notes for all application updates
10.2.2 Vendors who provide support/maintenance services to customers to maintain unique authentication credentials for each customer.

13.1.1 Validate that the PA-DSS Implementation Guide is specific to the application and version(s) being assessed.

14 New requirement to focus on instructional documentation and training programs, including internal training for vendor personnel with
PA-DSS responsibilities.

14.1 Providing information security and PA-DSS training for vendor personnel with PA-DSS responsibility at least annually.

14.2 Assignment of PA-DSS responsibilities to vendor personnel.
 
Other than the new requirements mentioned above, there are many clarifications and enhanced requirements for certain points which are available on the council’s website.

Comments are closed.