I saw that the PCI DSS 3.0 preview made penetration testing a requirement for everyone, including SMBs. Could you detail what exactly is required out of PCI DSS penetration tests to achieve compliance? What do you think would be the cheapest method for SMBs to meet this requirement?
Ed Moyle analyzes the five most important PCI 3.0 changes.
You are correct. The Payment Card Industry Data Security Standard (PCI DSS) does indeed require that all merchants conduct penetration testing to ensure the security of their environments. While pen tests aren't actually a new requirement in PCI DSS 3.0, the recently released draft revision includes language that applies a new degree of rigor to penetration testing. Here are some of the key changes to the PCI DSS penetration testing requirement:
- Penetration tests must be based upon an industry-accepted model, such as the NIST SP 800-115 framework.
- Testing must cover the entire cardholder data environment, including the effectiveness of any controls designed to reduce the environment's scope.
- It must cover both application-layer and network-layer threats.
Penetration testing must be done from both an internal and external perspective on an annual basis and after any significant change in the infrastructure or applications. Additionally, any exploitable vulnerabilities discovered during the test must be addressed and retested.
There is one piece of good news: Unlike most of the PCI DSS 3.0 changes that go into effect at the beginning of 2014, organizations have until July 15, 2015, to comply with the new provisions of section 11.3 covering penetration testing. Until that date, they may continue to follow existing procedures that comply with PCI DSS 2.0.
Dig Deeper on PCI Data Security Standard
Related Q&A from Mike Chapple
Choosing to encrypt confidential data with AES or DES encryption is an important cybersecurity matter. Learn about the important differences between ... Continue Reading
It's not possible to eradicate the risk of DoS attacks, but there are steps infosec pros can take to reduce their impact. Mike Chapple shares ... Continue Reading
The HHS OCR ruled that healthcare ransomware attacks are HIPAA violations, so these covered entities need to react according to the HHS's guidance. ... Continue Reading