Document Comparison
pci_dss_summary_of_changes_v1-2.pdf
→
pci_dss_v2_summary_of_changes.pdf
7% similar
15 → 20
Pages
4664 → 5855
Words
40
Content Changes
Content Changes
40 content changes. 24 administrative changes (dates, page numbers) hidden.
Added
p. 2
Section or Requirement Change Typei Old New General General Throughout Removed specific references to the Glossary as references are generally not provided for other glossary terms.
Clarification General General Attestations of Compliance Attestations of Compliance removed from appendices and separate documents created. References and Appendix titles updated accordingly throughout document.
Clarification General General Introduction and PCI Data Security Standard Overview Added information about the role of PCI DSS in the protection of cardholder data. Updated „High Level Overview‟ graphic to reflect requirement titles. Clarified that the PCI DSS is an assessment tool for use during compliance assessments. Added information about resources available on the PCI SSC website.
Additional Guidance General General PCI DSS Applicability Information Added term “account data” to align with PTS Secure Exchange and Reading of Data (SRED) module. Provided more details on “cardholder data” and “sensitive authentication data.” Clarified that primary …
Clarification General General Attestations of Compliance Attestations of Compliance removed from appendices and separate documents created. References and Appendix titles updated accordingly throughout document.
Clarification General General Introduction and PCI Data Security Standard Overview Added information about the role of PCI DSS in the protection of cardholder data. Updated „High Level Overview‟ graphic to reflect requirement titles. Clarified that the PCI DSS is an assessment tool for use during compliance assessments. Added information about resources available on the PCI SSC website.
Additional Guidance General General PCI DSS Applicability Information Added term “account data” to align with PTS Secure Exchange and Reading of Data (SRED) module. Provided more details on “cardholder data” and “sensitive authentication data.” Clarified that primary …
Added
p. 3
Section or Requirement Change Typei Old New General General Scope of Assessment for Compliance with PCI DSS Requirements Added “virtualization components” to the definition of “system components.” Clarified that the cardholder data environment is comprised of “people, processes and technology that store, process, or transmit cardholder data or sensitive authentication data.” Additional Guidance General General Scope of Assessment for Compliance with PCI DSS Requirements Added detailed paragraph to clarify that the first step of a PCI DSS review is to accurately determine the scope of the assessment, by identifying all locations and flows of cardholder data and ensuring that all such locations are included in the assessment.
Additional Guidance General General Network Segmentation Added clarifications including that segmentation may be achieved through physical or logical means. Minor replacements to some wording to clarify meaning.
Clarification General General Wireless Clarified focus on presence of a WLAN rather than a …
Additional Guidance General General Network Segmentation Added clarifications including that segmentation may be achieved through physical or logical means. Minor replacements to some wording to clarify meaning.
Clarification General General Wireless Clarified focus on presence of a WLAN rather than a …
Added
p. 5
Section or Requirement Change Typei Old New 1.3.1 1.3.1 Requirement and Testing Procedure Clarified intent of requirement for DMZ to restrict inbound traffic to system components that provide authorized services, protocols, and ports.
Clarification 1.3.3 1.3.3 Requirement and Testing Procedure Clarified that direct connections should not be permitted between the Internet and internal networks.
Clarification 1.3.5 1.3.5 Requirement and Testing Procedure Clarified intent that only authorized outbound traffic is permitted.
Clarification 1.3.6 1.3.6 Testing Procedure Allowed greater flexibility in testing procedure by removing specification of port scanner use.
Clarification 1.3.8 1.3.8.a
• Requirement and Testing Procedure Clarified intent to prevent disclosure of private IP addresses to the Internet and ensure that any such disclosure to external entities is authorized. Removed specific references to IP masquerading and use of network address translation (NAT) technologies and added examples of methods for preventing private IP address disclosure. Separated testing procedure into two sub- procedures.
Additional 1.4.b …
Clarification 1.3.3 1.3.3 Requirement and Testing Procedure Clarified that direct connections should not be permitted between the Internet and internal networks.
Clarification 1.3.5 1.3.5 Requirement and Testing Procedure Clarified intent that only authorized outbound traffic is permitted.
Clarification 1.3.6 1.3.6 Testing Procedure Allowed greater flexibility in testing procedure by removing specification of port scanner use.
Clarification 1.3.8 1.3.8.a
• Requirement and Testing Procedure Clarified intent to prevent disclosure of private IP addresses to the Internet and ensure that any such disclosure to external entities is authorized. Removed specific references to IP masquerading and use of network address translation (NAT) technologies and added examples of methods for preventing private IP address disclosure. Separated testing procedure into two sub- procedures.
Additional 1.4.b …
Added
p. 6
Section or Requirement Change Typei Old New 2.1.1 2.1.1.a
• Requirement and Testing Procedure Removed content that overlapped with Requirement 4.1.1, to clarify that the intent of this requirement is to ensure that vendor defaults are changed. Separated Testing Procedure 2.1.1 into individual Testing Procedures 2.1.1a through 2.1.1.e. Removed reference to WPA, as this is no longer considered strong encryption on its own.
Clarification 2.2 2.2 Requirement and Testing Procedures Moved examples of system hardening standards from testing procedure to requirement and added ISO as a source for hardening standards.
Clarification 6.2.b 2.2.b Testing Procedure Moved content from former Testing Procedure 6.2.b to 2.2.b to ensure that system configuration standards are updated with vulnerabilities identified in Requirement 6.2.
Clarification 2.2.b 2.2.d Testing Procedure Renumbered Testing Procedure 2.2.b to 2.2.d. Clarification 2.2.1 2.2.1 Requirement Updated requirement to clarify intent of “one primary function per server” and use of virtualization.
Additional Guidance N/A 2.2.1.b …
• Requirement and Testing Procedure Removed content that overlapped with Requirement 4.1.1, to clarify that the intent of this requirement is to ensure that vendor defaults are changed. Separated Testing Procedure 2.1.1 into individual Testing Procedures 2.1.1a through 2.1.1.e. Removed reference to WPA, as this is no longer considered strong encryption on its own.
Clarification 2.2 2.2 Requirement and Testing Procedures Moved examples of system hardening standards from testing procedure to requirement and added ISO as a source for hardening standards.
Clarification 6.2.b 2.2.b Testing Procedure Moved content from former Testing Procedure 6.2.b to 2.2.b to ensure that system configuration standards are updated with vulnerabilities identified in Requirement 6.2.
Clarification 2.2.b 2.2.d Testing Procedure Renumbered Testing Procedure 2.2.b to 2.2.d. Clarification 2.2.1 2.2.1 Requirement Updated requirement to clarify intent of “one primary function per server” and use of virtualization.
Additional Guidance N/A 2.2.1.b …
Added
p. 7
Section or Requirement Change Typei Old New 3 3 Introductory paragraph Clarified “unprotected PANs should not be sent using end-user messaging technologies such as e- mail and instant messaging.” Clarification 3.1 3.1 Requirement and Testing Procedures Made this a more general requirement, and moved testing procedures formerly in 3.1 to new Requirement and Testing Procedure 3.1.1 (see below).
Clarification N/A 3.1.1, 3.1.1.a
• Requirement and Testing Procedures Renumbered and separated former Testing Procedure 3.1 to individual Testing Procedures 3.1.1.a through 3.1.1.d. Added detail to requirement to align with testing procedures. New Testing Procedure 3.1.1.e to clarify that assessor should verify that stored data does not exceed retention requirements defined in the policy.
Clarification 3.2 3.2 Requirement and Testing Procedures Added note to requirement to clarify that it is permissible for issuers and companies that support issuing processing to store sensitive authentication data when there is a business justification and …
Clarification N/A 3.1.1, 3.1.1.a
• Requirement and Testing Procedures Renumbered and separated former Testing Procedure 3.1 to individual Testing Procedures 3.1.1.a through 3.1.1.d. Added detail to requirement to align with testing procedures. New Testing Procedure 3.1.1.e to clarify that assessor should verify that stored data does not exceed retention requirements defined in the policy.
Clarification 3.2 3.2 Requirement and Testing Procedures Added note to requirement to clarify that it is permissible for issuers and companies that support issuing processing to store sensitive authentication data when there is a business justification and …
Added
p. 8
Section or Requirement Change Typei Old New 3.4 3.4 Requirement Clarified that requirement applies only to the PAN. Removed note about minimum account information since this has been clarified in the requirement and in the PCI DSS Applicability Table. Clarified requirements if hashing or truncation is used to render PAN unreadable. Added Note to identify risk of hashed and truncation PANs in the same environment, and that additional security controls are required to ensure that original PAN data cannot be reconstructed. Deleted note on the use of compensating controls (since compensating controls may be applicable for most PCI DSS requirements).
Clarification 3.4.d 3.4.d Testing Procedure Clarified that PAN should be “rendered unreadable or removed,” rather than “sanitized or removed,” as “sanitize” is redundant with “remove.” Clarification 3.4.1.c 3.4.1.c Testing Procedure Clarified note to verify that if disk encryption is not used to encrypt removable media, than …
Clarification 3.4.d 3.4.d Testing Procedure Clarified that PAN should be “rendered unreadable or removed,” rather than “sanitized or removed,” as “sanitize” is redundant with “remove.” Clarification 3.4.1.c 3.4.1.c Testing Procedure Clarified note to verify that if disk encryption is not used to encrypt removable media, than …
Added
p. 9
Section or Requirement Change Typei Old New 3.6 3.6 Requirement and Testing Procedures Moved note from testing procedure to requirement. Clarified in Testing Procedure 3.6.b that service providers should provide key management guidance to customers covering transmission, storage, and update of customer keys (not just storage), in accordance with Sub-Requirements 3.6.1 through 3.6.8. Deleted note about secure transmission of such keys as covered in sub-requirements.
Clarification 3.6.4 3.6.4 Requirement and Testing Procedure Clarified that key changes are required when keys reach the end of their defined cryptoperiod, rather than “at least annually.” Added guidance for industry best practices.
Clarification 3.6.5 3.6.5 Requirement and Testing Procedures Changed wording to clarify that keys should be retired or replaced when the integrity of keys has been weakened, and provided examples. Added note that if retired or replaced keys are retained, they must be securely archived and retained only …
Clarification 3.6.4 3.6.4 Requirement and Testing Procedure Clarified that key changes are required when keys reach the end of their defined cryptoperiod, rather than “at least annually.” Added guidance for industry best practices.
Clarification 3.6.5 3.6.5 Requirement and Testing Procedures Changed wording to clarify that keys should be retired or replaced when the integrity of keys has been weakened, and provided examples. Added note that if retired or replaced keys are retained, they must be securely archived and retained only …
Added
p. 10
Section or Requirement Change Typei Old New 4.1 4.1, 4.1.a
• 4.1.e Requirement and Testing Procedures Included SSH as an example of a security protocol, removed examples from testing procedure. Separated Testing Procedure 4.1 into individual Testing Procedures 4.1.a through 4.1.e. Clarified in Testing Procedure 4.1.b that trusted keys and/or certificates are required for all types of transmissions, not only SSL/TLS. Clarified in procedure 4.1.c that the protocol must be implemented to use secure configurations.
Clarification 4.1.1 4.1.1 Requirement Updated note regarding use of WEP as of 30 June 2010.
Clarification 4.2 4.2 Requirement and Testing Procedures Changed wording to clarify that unprotected (rather than unencrypted) PANs should never be sent by end-user messaging technologies.
Clarification 5.2 5.2 Requirement and Testing Procedures Clarified that anti-virus mechanisms should be generating audit logs, rather than just being “capable of generating” such logs.
Clarification 6.1 6.1 Requirements Clarified intent to protect system components and …
• 4.1.e Requirement and Testing Procedures Included SSH as an example of a security protocol, removed examples from testing procedure. Separated Testing Procedure 4.1 into individual Testing Procedures 4.1.a through 4.1.e. Clarified in Testing Procedure 4.1.b that trusted keys and/or certificates are required for all types of transmissions, not only SSL/TLS. Clarified in procedure 4.1.c that the protocol must be implemented to use secure configurations.
Clarification 4.1.1 4.1.1 Requirement Updated note regarding use of WEP as of 30 June 2010.
Clarification 4.2 4.2 Requirement and Testing Procedures Changed wording to clarify that unprotected (rather than unencrypted) PANs should never be sent by end-user messaging technologies.
Clarification 5.2 5.2 Requirement and Testing Procedures Clarified that anti-virus mechanisms should be generating audit logs, rather than just being “capable of generating” such logs.
Clarification 6.1 6.1 Requirements Clarified intent to protect system components and …
Added
p. 10
Clarification 6.3.1 N/A Requirements and Testing Procedures Removed requirements and testing procedures as vulnerability testing formerly in 6.3.1 is addressed in 6.5.1 through 6.5.9.
Section or Requirement Change Typei Old New
• 6.4.4 Requirements and Testing Procedures Moved requirements and testing procedures to 6.4, to clarify intent that requirements apply to test and development environments, and not just development environments.
Clarification 6.3.7 6.3.2 Requirement and Testing Procedures Removed circular reference from note. Consolidated testing procedures (formerly 6.3.7.a and 6.3.7.b) into single procedure 6.3.2.a, to combine „internal‟ and „web‟ applications into single procedure. Removed specific reference to web applications and OWASP Guide to consolidate secure coding requirements for applications in scope, including non-web applications. Renumbered testing procedure previously 6.3.7.c to 6.3.2.b.
Clarification 6.4 6.4 Requirement and Testing Procedures Clarified requirement and testing procedure apply to change control processes and procedures. Imported content from former Testing Procedure 6.3.to align with …
Section or Requirement Change Typei Old New
• 6.4.4 Requirements and Testing Procedures Moved requirements and testing procedures to 6.4, to clarify intent that requirements apply to test and development environments, and not just development environments.
Clarification 6.3.7 6.3.2 Requirement and Testing Procedures Removed circular reference from note. Consolidated testing procedures (formerly 6.3.7.a and 6.3.7.b) into single procedure 6.3.2.a, to combine „internal‟ and „web‟ applications into single procedure. Removed specific reference to web applications and OWASP Guide to consolidate secure coding requirements for applications in scope, including non-web applications. Renumbered testing procedure previously 6.3.7.c to 6.3.2.b.
Clarification 6.4 6.4 Requirement and Testing Procedures Clarified requirement and testing procedure apply to change control processes and procedures. Imported content from former Testing Procedure 6.3.to align with …
Added
p. 13
Section or Requirement Change Typei Old New 8 8 Introductory Paragraph Added note to align with PA-DSS Requirement 3.2, regarding applicability of unique user ID and secure authentication controls to “user accounts within a point of sale payment application that only have access to one card number at a time in order to facilitate a single transaction (such as cashier accounts).” Clarification 8.2 8.2 Requirement Added clarification and examples authentication methods.
Clarification 8.3 8.3 Requirement and Testing Procedure Clarified examples of two factor authentication to include Radius “with tokens” and “other technologies that support strong authentication.” Added note clarify intent of two-factor authentication.
Clarification 8.5 8.5 Requirements and Testing Procedures Added term “identification.” Clarification 8.5.2, 8.5.7, 8.5.8, 8.5.13 8.5.2, 8.5.7, 8.5.8, 8.5.13 Requirements and Testing Procedures Added “authentication” to allow for more flexibility for companies using other authentication mechanisms outside of passwords.
Clarification 8.5.3 8.5.3 Requirement and Testing Procedures Included “password resets” as …
Clarification 8.3 8.3 Requirement and Testing Procedure Clarified examples of two factor authentication to include Radius “with tokens” and “other technologies that support strong authentication.” Added note clarify intent of two-factor authentication.
Clarification 8.5 8.5 Requirements and Testing Procedures Added term “identification.” Clarification 8.5.2, 8.5.7, 8.5.8, 8.5.13 8.5.2, 8.5.7, 8.5.8, 8.5.13 Requirements and Testing Procedures Added “authentication” to allow for more flexibility for companies using other authentication mechanisms outside of passwords.
Clarification 8.5.3 8.5.3 Requirement and Testing Procedures Included “password resets” as …
Added
p. 17
Section or Requirement Change Typei Old New 11.2 11.2, 11.2.1
• Requirements and Testing Procedures Separated and renumbered internal & external scan requirements formerly 11.2 into individual Sub-Requirements and Testing Procedures 11.2.1 through 11.2.3. Moved note from former Testing Procedure 11.2.b to Requirement 11.2 to clarify that four internal and external scans must be verified.
Clarification 11.2.a 11.2.1.a
• Testing Procedure Clarified that the internal scan process includes rescans until passing results are obtained, or all “High” vulnerabilities as defined in PCI DSS Requirement 6.2 are resolved. Clarified that internal scans should be performed by qualified parties.
Clarification 11.2.b 11.2.2.a
• Testing Procedures Replaced “PCI Security Scanning Procedures” with “ASV Program Guide Requirements.” Clarified that ASVs are approved by the PCI Security Standards Council (PCI SSC).
Clarification 11.2.c 11.2.3.a
• Testing Procedures Clarified requirements for internal & external scans to include rescans until high-risk vulnerabilities are addressed, and to be performed …
• Requirements and Testing Procedures Separated and renumbered internal & external scan requirements formerly 11.2 into individual Sub-Requirements and Testing Procedures 11.2.1 through 11.2.3. Moved note from former Testing Procedure 11.2.b to Requirement 11.2 to clarify that four internal and external scans must be verified.
Clarification 11.2.a 11.2.1.a
• Testing Procedure Clarified that the internal scan process includes rescans until passing results are obtained, or all “High” vulnerabilities as defined in PCI DSS Requirement 6.2 are resolved. Clarified that internal scans should be performed by qualified parties.
Clarification 11.2.b 11.2.2.a
• Testing Procedures Replaced “PCI Security Scanning Procedures” with “ASV Program Guide Requirements.” Clarified that ASVs are approved by the PCI Security Standards Council (PCI SSC).
Clarification 11.2.c 11.2.3.a
• Testing Procedures Clarified requirements for internal & external scans to include rescans until high-risk vulnerabilities are addressed, and to be performed …
Modified
p. 1
Payment Card Industry (PCI) Data Security Standard Summary of Changes from PCI DSS Version 1.1 to 1.2
Payment Card Industry (PCI) Data Security Standard Summary of Changes from PCI DSS Version 1.2.1 to 2.0
Removed
p. 2
Clarification General General Eliminated stand-alone PCI Data Security Standards document since it is redundant• the “standard” has always been included as the “PCI DSS Requirements’ column in the PCI DSS Security Assessment Procedures document.
Clarification General General Added the table that lists the PCI DSS 6 topics and 12 main requirements, formerly in the PCI Data Security Standard document.
Explanatory General General PCI DSS Applicability Information Changed “full magnetic stripe” to “full magnetic stripe data” and added a footnote to define this data.
Clarification General General Clarified “system components’ definition and emphasized use of “system components” term throughout document. In the Scope of Assessment section, clarified the following concepts: network segmentation, scoping, sampling, compensating controls, and third parties/outsourcing. Deleted merchant scoping section and related bullets previously on page 5.
Clarification General General Instructions and Content for Report on Compliance: Reordered listed items and enhanced required report content, including detail for scope of review, and …
Clarification General General Added the table that lists the PCI DSS 6 topics and 12 main requirements, formerly in the PCI Data Security Standard document.
Explanatory General General PCI DSS Applicability Information Changed “full magnetic stripe” to “full magnetic stripe data” and added a footnote to define this data.
Clarification General General Clarified “system components’ definition and emphasized use of “system components” term throughout document. In the Scope of Assessment section, clarified the following concepts: network segmentation, scoping, sampling, compensating controls, and third parties/outsourcing. Deleted merchant scoping section and related bullets previously on page 5.
Clarification General General Instructions and Content for Report on Compliance: Reordered listed items and enhanced required report content, including detail for scope of review, and …
Modified
p. 2 → 4
Additional Guidance General General PCI DSS Compliance • Completion Steps Updated reference to Attestations of Compliance on the PCI SSC website.
Modified
p. 2 → 4
Clarification Mirrors SAQs and PA- DSS General General Detailed PCI DSS Requirements and Security Assessment Procedures: Added section title before start of the Report on Compliance template. Included definitions for each of the column headings in the Report on Compliance template.
Clarification General General Detailed PCI DSS Requirements and Security Assessment Procedures Added clarification that N/A responses are to be reported in the “In Place” column.
Removed
p. 3
Clarification 1.1.2 1.1.2 Testing Procedures: Added an example of a network diagram “that shows cardholder data flows over the network.” Clarification 1.1.5, 1.1.6 & 1.1.7 1.1.5 Requirements & Testing Procedures: Combined 1.1.6 & 1.1.7 into 1.1.5. Former term “risky” changed to “insecure.” Clarification The requirements all covered the same theme.
Removed
p. 3
Clarification Added flexibility, based on Participating Organization feedback, so controls can be customized to an organization’s risk management policies.
Removed
p. 4
Clarification Didn’t logically fit into firewall configuration section 2 2 Introductory Paragraph: Reworded summary to aid understanding. Explanatory 2.1.1 2.1.1 Requirement and Testing Procedure: Clarified that requirement applies to wireless environments “attached to cardholder environment or transmitting cardholder data.” Clarification To address scoping/ segmentation FAQ’s 2.1.1 2.1.1 Requirement & Testing Procedure: Deleted references to specific wireless technologies like WEP. Clarification To emphasize using strong encryption technologies for wireless networks, for both authentication and transmission.
Removed
p. 5
Clarification 2.2 2.2 Requirement & Testing Procedure: Moved examples from requirement to testing procedures. Clarification 2.3 2.3 Testing Procedure: Changed bullet for “wireless management interfaces” to “web-based management interfaces.” Clarification 2.4 2.4 Requirement & Testing Procedure: Clarified that this requirement applies to “shared” hosting providers Clarification 3 3 Introductory Paragraph: Expanded first sentence to include examples in addition to encryption (truncation, masking, obfuscation, and hashing).
Explanatory 3.1 3.1 Testing Procedure: Simplified third bullet to add clarity. Clarification 3.2 3.2 Requirement: Changed “subsequent to” authorization to “after” authorization. Clarification 3.2.1 3.2.1 Requirement: Removed redundant information from italicized note. Clarification 3.2.1, 3.2.2. 3.2.3 3.2.1, 3.2.2. 3.2.3 Testing Procedures: Removed references to different types of logs, added “All logs,” and provided examples.
Explanatory 3.3 3.3 Testing Procedures: Changed the following terms: “specific” need to “legitimate business” need, “credit card data” to “PAN.” Provided examples of where PAN may be displayed.
Clarification 3.4 3.4 Requirement and Testing …
Explanatory 3.1 3.1 Testing Procedure: Simplified third bullet to add clarity. Clarification 3.2 3.2 Requirement: Changed “subsequent to” authorization to “after” authorization. Clarification 3.2.1 3.2.1 Requirement: Removed redundant information from italicized note. Clarification 3.2.1, 3.2.2. 3.2.3 3.2.1, 3.2.2. 3.2.3 Testing Procedures: Removed references to different types of logs, added “All logs,” and provided examples.
Explanatory 3.3 3.3 Testing Procedures: Changed the following terms: “specific” need to “legitimate business” need, “credit card data” to “PAN.” Provided examples of where PAN may be displayed.
Clarification 3.4 3.4 Requirement and Testing …
Removed
p. 6
Clarification 3.5, 3.6 3.5, 3.6 Requirement: Changed “encryption” to cryptographic throughout 3.5 and 3.6.” Clarification 3.6 3.6 Testing Procedures: Provided example of where Key Management Guidance can be found (NIST). Explanatory
Clarification 3.6.5, 3.6.8, 3.6.9 3.6.5 Requirement and Testing Procedures: Combined Requirements 3.6.8 and 3.6.9 into Requirement 3.6.5. Clarification 3.6.6 3.6.6 Requirement and Testing Procedures: Moved part of requirement included in parentheses to the testing procedures as an example.
Clarification 3.6.10 3.6.8 Requirement and Testing Procedures: Re- numbered 3.6.10 to 3.6.8. N/A 4 4 Introductory Paragraph: Reworded summary to aid understanding. Explanatory 4.1 4.1 Requirement and Testing Procedure: Changed former example of “WiFi (IEEE 802.11x)” to “Wireless technologies.” Updated SSL to include ‘latest patches.” Clarification Addressing SSL 2.0 FAQs 4.1 4.1 Testing Procedures: Broke SSL tests into three bullets. Clarification
Clarification 3.6.5, 3.6.8, 3.6.9 3.6.5 Requirement and Testing Procedures: Combined Requirements 3.6.8 and 3.6.9 into Requirement 3.6.5. Clarification 3.6.6 3.6.6 Requirement and Testing Procedures: Moved part of requirement included in parentheses to the testing procedures as an example.
Clarification 3.6.10 3.6.8 Requirement and Testing Procedures: Re- numbered 3.6.10 to 3.6.8. N/A 4 4 Introductory Paragraph: Reworded summary to aid understanding. Explanatory 4.1 4.1 Requirement and Testing Procedure: Changed former example of “WiFi (IEEE 802.11x)” to “Wireless technologies.” Updated SSL to include ‘latest patches.” Clarification Addressing SSL 2.0 FAQs 4.1 4.1 Testing Procedures: Broke SSL tests into three bullets. Clarification
Modified
p. 6 → 11
• 3.6.8 Requirement and Testing Procedures: Clarified that the testing procedures should include verification that the procedures are implemented.
• 6.3.2 Requirements and Testing Procedures Renumbered requirements and testing procedures due to merging and/or moving of previous requirements.
Removed
p. 7
Enhancement To emphasize using strong encryption technologies for wireless networks, for both authentication and transmission.
Removed
p. 7
Clarification To mirror PA-DSS and address FAQ’s.
Removed
p. 7
Clarification 5.2 5.2 Testing Procedures: Split former bullets of Testing Procedure 5.2 into separate testing procedures 5.2.a through 5.2.d. Included all operating system types in the sample of system components. Changed “in accordance with company retention policy” to “in accordance with PCI DSS Requirement 10.7.” Clarification & Enhancement Clarified that this log- retention policy should be in line with other log-retention policies required by PCI DSS.
Removed
p. 8
Clarification 6.2 6.2 Requirements: Clarified that “standards” refers to “configuration standards required by PCI DSS Requirement 2.2”.
Clarification 6.3 6.3 Requirements & Testing Procedures: Clarified that applications must be developed in accordance with PCI DSS requirements. Separated Testing Procedure 6.3 into 6.3.a and 6.3.b
•moved latter half of 6.3 to 6.3.b.
Clarification 6.3.1 6.3.1 Requirements & Testing Procedures: Added 6.3.1.1-6.3.1.5 to clarify items to be included in the software development life cycle when testing security patches and software and configuration changes.
Clarification 6.3.7 6.3.7 Requirements & Testing Procedures: Added note to detail what type of code this requirement applies to, and that internal parties can perform these code reviews. Updated testing procedure 6.3.7.a to focus on reviews of application code changes for internal applications. For 6.3.7.a, added a bulleted list to cover: That code changes must be reviewed by individuals other than originating code author, and by knowledgeable individuals; That corrections must …
Clarification 6.3 6.3 Requirements & Testing Procedures: Clarified that applications must be developed in accordance with PCI DSS requirements. Separated Testing Procedure 6.3 into 6.3.a and 6.3.b
•moved latter half of 6.3 to 6.3.b.
Clarification 6.3.1 6.3.1 Requirements & Testing Procedures: Added 6.3.1.1-6.3.1.5 to clarify items to be included in the software development life cycle when testing security patches and software and configuration changes.
Clarification 6.3.7 6.3.7 Requirements & Testing Procedures: Added note to detail what type of code this requirement applies to, and that internal parties can perform these code reviews. Updated testing procedure 6.3.7.a to focus on reviews of application code changes for internal applications. For 6.3.7.a, added a bulleted list to cover: That code changes must be reviewed by individuals other than originating code author, and by knowledgeable individuals; That corrections must …
Removed
p. 9
• 6.5.10 Requirements & Testing Procedures: Changed each to match new Open Web Application Security Project guide (new “Top Ten”).
Clarification 6.6 6.6 Requirements & Testing Procedures: Deleted note that this requirement is “a best practice until June 30, 2008” - this is now a requirement. Clarified that this requirement 1) applies to public- facing web applications to address new threats and vulnerabilities on an ongoing basis, 2) that applications can be reviewed with manual or automated application vulnerability assessment tools or methods, and 3) that applications should be reviewed at least annually and for all changes. Replaced “application layer firewall” with “web- application firewall.” Clarification Removed “Best Practice” wording 7 7 Introductory Paragraph: Reworded summary to aid understanding. Explanatory 7.1 7.1 Requirement & Testing Procedures: To standardize use of terms, changed “computing resources and cardholder information” to “system components and cardholder data”.
Clarification 7.1, 7.2 7.1.1 - 7.1.4, 7.2.1 - 7.2.3 …
Clarification 6.6 6.6 Requirements & Testing Procedures: Deleted note that this requirement is “a best practice until June 30, 2008” - this is now a requirement. Clarified that this requirement 1) applies to public- facing web applications to address new threats and vulnerabilities on an ongoing basis, 2) that applications can be reviewed with manual or automated application vulnerability assessment tools or methods, and 3) that applications should be reviewed at least annually and for all changes. Replaced “application layer firewall” with “web- application firewall.” Clarification Removed “Best Practice” wording 7 7 Introductory Paragraph: Reworded summary to aid understanding. Explanatory 7.1 7.1 Requirement & Testing Procedures: To standardize use of terms, changed “computing resources and cardholder information” to “system components and cardholder data”.
Clarification 7.1, 7.2 7.1.1 - 7.1.4, 7.2.1 - 7.2.3 …
Removed
p. 10
Clarification 8.5.1 8.5.1 Testing Procedures: Removed 8.5.1.b due to its redundancy. Clarification 8.5.4 8.5.4 Testing Procedures: Changed “inactivated” to “deactivated.” Clarification 8.5.5 8.5.5 Requirement &Testing Procedure: Changed “remove” to “remove or disable.” Clarification 8.5.6 8.5.6 Testing Procedure: Changed “inactive” to “disabled.” Clarification 8.5.16 8.5.16 Testing Procedures: To clarify that access to databases should be restricted to administrators and applications, separated user access, queries, and actions from application access. Changed “SQL” to database.
Clarification 9.1.1 9.1.1 Requirement & Testing Procedure: Clarified that “cameras” means “video cameras”. Added an alternate option of “other access control mechanisms” in addition to “video cameras” and clarified that the technology must provide ability to monitor “individual physical access”. Added note to define “sensitive areas”.
Clarification 9.4 9.4 Requirement: Added required contents of visitor logs to align the requirement with the testing procedure. Clarification 9.5 9.5 Requirement & Testing Procedure: To match the testing procedure, added requirement to review …
Clarification 9.1.1 9.1.1 Requirement & Testing Procedure: Clarified that “cameras” means “video cameras”. Added an alternate option of “other access control mechanisms” in addition to “video cameras” and clarified that the technology must provide ability to monitor “individual physical access”. Added note to define “sensitive areas”.
Clarification 9.4 9.4 Requirement: Added required contents of visitor logs to align the requirement with the testing procedure. Clarification 9.5 9.5 Requirement & Testing Procedure: To match the testing procedure, added requirement to review …
Modified
p. 10 → 5
Clarification 9.1 9.1 Requirement & Testing Procedure: Changed “that store, process, or transmit cardholder data” to “in the cardholder data environment”.
Clarification 1.3.7 1.3.7 Requirement and Testing Procedure Clarified that requirement applies to any type of cardholder data storage, rather than just databases.
Modified
p. 10 → 14
Clarification 9.2.a 9.2.a Requirement & Testing Procedure: Removed “contractors” in the testing procedure and added “contractors” as part of the definition of an “employee” in the requirement.
Clarification 9.3 9.3 Testing Procedure Clarified that testing procedure applies to visitor controls to align with requirement.
Removed
p. 11
Clarification 9.8 9.8 Requirement & Testing Procedure: Clarified “media” as “media that contain cardholder data”. Clarification 9.9 9.9 Testing Procedure: Removed “periodic” in the frequency of media inventories. (Defined frequency in 9.9.1.) Clarification 9.9.1 9.9.1 Requirement & Testing Procedure: Clarified that media inventories should be performed at least annually. Removed testing procedure 9.9.1.b.
Clarification Redundant with testing procedure 9.6.
Clarification Redundant with testing procedure 9.6.
Removed
p. 11
Clarification 9.10.2 9.10.2 Requirement & Testing Procedure: Clarified that, when electronic media is destroyed, cardholder data must be rendered unrecoverable, which can be achieved via a secure wipe program or by physical destruction.
Clarification 10 10 Introductory Paragraph: Reworded summary to aid understanding. Explanatory 10.1 10.1 Testing Procedure: Removed specific reference to wireless networks since requirement applies to all system components.
Clarification 10.2 10.2 Testing Procedure: Added to all 10.2 sub requirements wording to ensure events are verified to be “logged.” Clarification 10.3 10.3 Testing Procedure: Added to all 10.3 sub requirements wording to ensure these events are verified to “be included in log entries.” Clarification 10.4.a 10.4.a Testing Procedure: Added “a known, stable version” of NTP “kept current per PCI DSS requirements 6.1 and 6.2” to remove redundancy in 10.4.c.
Clarification 10 10 Introductory Paragraph: Reworded summary to aid understanding. Explanatory 10.1 10.1 Testing Procedure: Removed specific reference to wireless networks since requirement applies to all system components.
Clarification 10.2 10.2 Testing Procedure: Added to all 10.2 sub requirements wording to ensure events are verified to be “logged.” Clarification 10.3 10.3 Testing Procedure: Added to all 10.3 sub requirements wording to ensure these events are verified to “be included in log entries.” Clarification 10.4.a 10.4.a Testing Procedure: Added “a known, stable version” of NTP “kept current per PCI DSS requirements 6.1 and 6.2” to remove redundancy in 10.4.c.
Modified
p. 11 → 16
Clarification 10.4.d 10.4.c Testing Procedure: Removed 10.4.c sub- requirement as it was redundant with 10.4.a. Renumbered previous 10.4.d to 10.4.c.
Clarification 10.4.c 10.4.3 Requirement and Testing Procedure Restructured former 10.4.c into new sub- requirement to ensure time is received from industry-accepted sources.
Removed
p. 12
Clarification To address FAQs and PO feedback on the “online” requirement 11 11 Introductory Paragraph: Changed “hackers” to “malicious individuals”, and “systems” to “system components”. Added language that controls have to adapt to changing environment.
Explanatory 11.1 11.1 Requirements & Testing Procedures: Removed general language regarding testing of security controls since this is duplicated by other requirements. Focused requirement on testing for the presence of wireless access points and added option to implement wireless IDS/IPS. Changed 11.1.a to address verification that scanning takes place or that IDS/IPS is implemented. Changed 11.1.b to verify IDS/IPS will generate alerts. Added 11.1.c to ensure Incident Response Plan defines a process to react to unauthorized wireless devices.
Clarification To address duplication of other requirements and provide more flexibility 11.2 11.2 Requirements & Testing Procedures: Changed language in note to be consistent with other documentation. Changed 11.2.a to be specific to internal scans and changed “clean” to …
Explanatory 11.1 11.1 Requirements & Testing Procedures: Removed general language regarding testing of security controls since this is duplicated by other requirements. Focused requirement on testing for the presence of wireless access points and added option to implement wireless IDS/IPS. Changed 11.1.a to address verification that scanning takes place or that IDS/IPS is implemented. Changed 11.1.b to verify IDS/IPS will generate alerts. Added 11.1.c to ensure Incident Response Plan defines a process to react to unauthorized wireless devices.
Clarification To address duplication of other requirements and provide more flexibility 11.2 11.2 Requirements & Testing Procedures: Changed language in note to be consistent with other documentation. Changed 11.2.a to be specific to internal scans and changed “clean” to …
Removed
p. 12
Clarification Qualified internal personnel or external 3rd parties can perform penetration tests.
Modified
p. 12 → 14
Clarification 10.7 10.7 Requirement & Testing Procedure: Replaced “online” reference with “immediately available for analysis” and provided examples (online, archived or restorable from backup).
Clarification 9.1.2 9.1.2 Requirement and Testing Procedure Replaced “employee” with “onsite personnel.” Added example of physically accessible areas.
Removed
p. 13
Clarification 11.3.2 11.3.2 Testing Procedures: Added reference to requirement 6.5 as minimum tests to perform. Clarification 11.4 11.4 Requirements & Testing Procedures: Clarified IDS vs. IPS requirement. Changed monitoring scope from “all network traffic” to “all traffic in the cardholder data environment”. Changed 11.4.a from “Observe the use of”” to “Verify the use of” Changed 11.4b from “is in place to monitor and alert” to “are configured to monitor and alert”.
Clarification 11.5 11.5 Requirements & Testing Procedures: Added configuration files. Removed reference to cardholder data files from italicized text. Added examples of types of files to be monitored.
Clarification Cardholder data changes as part of regular business and are not expected to be monitored by file integrity monitoring.
Clarification 11.5 11.5 Requirements & Testing Procedures: Added configuration files. Removed reference to cardholder data files from italicized text. Added examples of types of files to be monitored.
Clarification Cardholder data changes as part of regular business and are not expected to be monitored by file integrity monitoring.
Removed
p. 13
Clarification 12.1.1 12.1.1 Requirement & Testing Procedure: Changed “requirements in this specification” to “PCI DSS requirements.” Clarification 12.3 12.3 Requirement: Changed list of critical employee-facing technologies to include “remote access technologies, wireless technologies, removable electronic media, e- mail usage, internet usage, laptops, and personal data/digital assistants (PDAs).” Clarification 12.3.1 and 12.3.2 12.3.1 and 12.3.2 Testing Procedure: Changed “devices” to “technologies.” Clarification 12.3.8 and 12.3.9 12.3.8 and 12.3.9 Requirement & Testing Procedure: Changed “modems” to “remote access technologies.” Clarification 12.3.10 12.3.10 Requirement & Testing Procedure: Changed “remotely via modem” to “via remote access technologies.” Generalized media such as floppy disks and external media to “removable electronic media.” Clarified that copy, move and storage functions are prohibited.
Removed
p. 14
Clarification 12.6.2 12.6.2 Requirement & Testing Procedure: Clarified that employee acknowledgement must be done at least annually. Provided examples of acknowledgement (in writing or electronically).
Clarification 12.7 12.7 Requirement & Testing Procedure: Changed “potential employees” to “potential employees prior to hire.” Clarification Previous confusion around the definition of “potential employees”.
Clarification 12.7 12.7 Requirement & Testing Procedure: Changed “potential employees” to “potential employees prior to hire.” Clarification Previous confusion around the definition of “potential employees”.
Removed
p. 14
Clarification 12.8.1 12.8.1 Requirement & Testing Procedure: Replaced with former 12.10.1 but changed the applicability from connected entities to service providers.
Clarification 12.8.2 12.8.2 Requirement & Testing Procedure: Changed “contract” to “written agreement.” Changed “third party” to “service providers” in the testing procedure.
Clarification N/A 12.8.3 Requirement & Testing Procedure: Formerly 12.10.2 and 12.10.4 but combined as new 12.8.3 and changed the applicability from connected entities to service providers. Clarified that an established process for engaging service providers including proper due diligence is in place prior to engagement.
Clarification N/A 12.8.4 Requirement & Testing Procedure: Formerly 12.10.3 but changed the applicability from connected entities to service providers. Clarified to include a maintenance program to monitor service providers’ PCI DSS compliance status.
Clarification Added flexibility, based on Participating Organization feedback so the control can be customized to the organization’s risk management policies.
Clarification 12.9.3 and 12.9.5 12.9.3 and 12.9.5 Testing Procedure: Added “detection of unauthorized wireless …
Clarification 12.8.2 12.8.2 Requirement & Testing Procedure: Changed “contract” to “written agreement.” Changed “third party” to “service providers” in the testing procedure.
Clarification N/A 12.8.3 Requirement & Testing Procedure: Formerly 12.10.2 and 12.10.4 but combined as new 12.8.3 and changed the applicability from connected entities to service providers. Clarified that an established process for engaging service providers including proper due diligence is in place prior to engagement.
Clarification N/A 12.8.4 Requirement & Testing Procedure: Formerly 12.10.3 but changed the applicability from connected entities to service providers. Clarified to include a maintenance program to monitor service providers’ PCI DSS compliance status.
Clarification Added flexibility, based on Participating Organization feedback so the control can be customized to the organization’s risk management policies.
Clarification 12.9.3 and 12.9.5 12.9.3 and 12.9.5 Testing Procedure: Added “detection of unauthorized wireless …
Removed
p. 15
Clarification Appendix C Appendix C Compensating Controls Worksheet: Clarified compensating controls as needed to mirror clarifications throughout document.
Clarification N/A Appendix D Attestation of Compliance for Onsite Assessments
• Merchants: Added standard attestation of compliance forms to be completed and signed by merchants and/or QSAs.
Enhancement N/A Appendix E Attestation of Compliance for Onsite Assessments
• Service Providers: Added standard attestation of compliance forms to be completed and signed by service providers and QSAs.
Enhancement N/A Appendix F PCI DSS Reviews
• Scoping and Sampling: Added flowchart to depict scoping and sampling processes, to be used by assessors conducting PCI DSS reviews.
Clarification i Explanatory: Explanations and/or definitions to increase understanding Clarification: Clarifies intent of requirement Enhancements: Changes needed to ensure ongoing integrity so that the standard continues to adequately address risks
Clarification N/A Appendix D Attestation of Compliance for Onsite Assessments
• Merchants: Added standard attestation of compliance forms to be completed and signed by merchants and/or QSAs.
Enhancement N/A Appendix E Attestation of Compliance for Onsite Assessments
• Service Providers: Added standard attestation of compliance forms to be completed and signed by service providers and QSAs.
Enhancement N/A Appendix F PCI DSS Reviews
• Scoping and Sampling: Added flowchart to depict scoping and sampling processes, to be used by assessors conducting PCI DSS reviews.
Clarification i Explanatory: Explanations and/or definitions to increase understanding Clarification: Clarifies intent of requirement Enhancements: Changes needed to ensure ongoing integrity so that the standard continues to adequately address risks