Source: http://docplayer.net/21154865-Payment-card-industry-pci-data-security-standard-summary-of-changes-from-pci-dss-version-1-2-1-to-2-0.html
Timestamp: 2018-11-13 07:28:25
Document Index: 129912311

Matched Legal Cases: ['art 2', 'art 2', 'art 3', 'art 2', 'art 4', 'art 5', 'art 6', 'art 2', 'art 2']

Payment Card Industry (PCI) Data Security Standard. Summary of Changes from PCI DSS Version to PDF
Payment Card Industry (PCI) Data Security Standard. Summary of Changes from PCI DSS Version to 2.0
Download "Payment Card Industry (PCI) Data Security Standard. Summary of Changes from PCI DSS Version 1.2.1 to 2.0"
1 Payment Card Industry (PCI) Data Security Standard Summary of s from PCI DSS Version to 2.0 October 2010
2 General General Throughout Removed specific references to the Glossary as references are generally not provided for other glossary terms. General General Attestations of Compliance Attestations of Compliance removed from appendices and separate documents created. References and Appendix titles updated accordingly throughout document. 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. 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 account data (PAN) is the defining factor for the applicability of PCI DSS. Removed footnote addressing other legislation and replaced with updated paragraph text. Updated paragraph text and applicability table to clarify which data elements must be rendered unreadable according to PCI DSS Requirement 3.4. N/A General Relationship between PCI DSS and PA-DSS Added new section to reflect content in PA-DSS. Clarified that use of a PA-DSS compliant application alone does not make an entity PCI DSS compliant. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 2 of 20
3 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. 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. 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. General General Wireless Clarified focus on presence of a WLAN rather than a LAN. General General Third Parties/Outsourcing Minor changes to terminology for consistency. General General Sampling of Business Facilities and System Components Clarified that sampling is conducted independently by the assessor and that sampling must first be performed for business facilities and then for system components within each selected facility. Clarified that sampling does not reduce the scope of the cardholder data environment or the applicability of PCI DSS, and that sampling of the individual PCI DSS requirements is not permitted. Clarified specific criteria that assessors must document when using sampling. Added criteria that assessors must revalidate the sampling rationale for each assessment. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 3 of 20
4 General General Instructions and Content for Report on Compliance Added criteria for assessor to report how the accuracy of the PCI DSS scope was validated for the assessment, in part 2. Updated reporting detail for sampling rationale and validation of sample size in part 2, to align with clarified content in Sampling section. Clarified in part 3 that list of individuals interviewed should include their organizations and topics covered. Moved Timeframe of Assessment from Part 2 to part 4, and added that the timeframe should indicate the duration and specify the time period over which the assessment occurred. d PCI DSS Security Scanning Procedures to Approved Scanning Vendors Program Guide in Part 5. Added explanation for N/A responses in Part 6. Minor wording changes for consistency. General General PCI DSS Compliance Completion Steps Updated reference to Attestations of Compliance on the PCI SSC website. 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. 1 1 Introductory Paragraph Minor wording changes for consistency. Added explanation that other system components providing firewall functionality must be treated in accordance with Requirement a, b Testing Procedures Separated Testing Procedure into individual Testing Procedures a through b Requirement Added examples of insecure services, protocols or ports Requirement Updated requirement to align with testing procedure Testing Procedure Restructured to clarify intent of procedure. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 4 of 20
5 Requirement and Testing Procedure Clarified intent of requirement for DMZ to restrict inbound traffic to system components that provide authorized services, protocols, and ports Requirement and Testing Procedure Clarified that direct connections should not be permitted between the Internet and internal networks Requirement and Testing Procedure Clarified intent that only authorized outbound traffic is permitted Testing Procedure Allowed greater flexibility in testing procedure by removing specification of port scanner use Requirement and Testing Procedure Clarified that requirement applies to any type of cardholder data storage, rather than just databases a b 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 subprocedures. 1.4.b 1.4.b Testing Procedure Clarified that personal firewall software should not be alterable by employee-owned computer users to align testing procedure with requirement Requirement Minor wording changes for clarity. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 5 of 20
6 a e 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 into individual Testing Procedures 2.1.1a through e. Removed reference to WPA, as this is no longer considered strong encryption on its own Moved examples of system hardening standards from testing procedure to requirement and added ISO as a source for hardening standards. 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 b 2.2.d Testing Procedure Renumbered Testing Procedure 2.2.b to 2.2.d Requirement Updated requirement to clarify intent of one primary function per server and use of virtualization. N/A b Testing Procedures optional testing procedure for virtualization technologies. Renumbered Testing Procedure to a , a b a c , 2.3.a 2.3.c Clarified that only necessary and secure services, protocols, daemons, etc., are to be enabled, and security features implemented for any insecure such services, etc., with examples. Separated Testing Procedure into individual Procedures a and b. Testing Procedures Separated Testing Procedure into individual Procedures a through c. Clarified that strong cryptography is required. Separated Testing Procedure 2.3 into individual Procedures 2.3.a through 2.3.c. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 6 of 20
7 3 3 Introductory paragraph Clarified unprotected PANs should not be sent using end-user messaging technologies such as e- mail and instant messaging Made this a more general requirement, and moved testing procedures formerly in 3.1 to new Requirement and Testing Procedure (see below). N/A 3.1.1, a e Renumbered and separated former Testing Procedure 3.1 to individual Testing Procedures a through d. Added detail to requirement to align with testing procedures. Testing Procedure e to clarify that assessor should verify that stored data does not exceed retention requirements defined in the policy 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 the data is stored securely. Testing Procedure 3.2.a added for issuers and companies that support issuing services to verify that business justification exists if SAD is stored. Renumbered Testing Procedure formerly 3.2 to 3.2.b, and prefaced it with For all other entities Requirement and Testing Procedure Replaced contained in a chip to equivalent data on a chip for consistency Testing Procedures Clarified testing procedures to examine data sources, including but not limited to the following. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 7 of 20
8 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). 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 c c Testing Procedure Clarified note to verify that if disk encryption is not used to encrypt removable media, than other method will need to be used Requirement Clarified that any keys used to secure cardholder data must be protected against disclosure and misuse. Added note to clarify how this requirement applies to key-encrypting keys, if used Testing Procedure Updated testing procedure to align with requirement , a b Added testing procedure to align with requirement. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 8 of 20
9 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 through Deleted note about secure transmission of such keys as covered in sub-requirements 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 d 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 for decryption or verification purposes. Added testing procedure to verify that if retired or replaced keys are retained, that they are not used for encryption operations Requirement and Testing Procedure Clarified that split knowledge and dual control applies only to manual clear-text cryptographic key management operations. Added note to provide examples of key management operations Requirement and Testing Procedure Clarified that key custodians should formally acknowledge their key-custodian responsibilities rather than sign a form. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 9 of 20
10 , 4.1.a 4.1.e 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 Requirement Updated note regarding use of WEP as of 30 June d wording to clarify that unprotected (rather than unencrypted) PANs should never be sent by end-user messaging technologies Clarified that anti-virus mechanisms should be generating audit logs, rather than just being capable of generating such logs Requirements Clarified intent to protect system components and software from known vulnerabilities Added that in addition to identifying vulnerabilities, processes should including ranking vulnerabilities according to risk. Provided guidance on how to assign risk rankings. Note: The ranking of vulnerabilities as defined in 6.2.a is considered a best practice until June 30, 2012, after which it becomes a requirement. Evolving Requirement , 6.3.a 6.3.d Added types of software applications that secure development practices would apply to. Separated Testing Procedure 6.3.a into individual Testing Procedures 6.3.a through 6.3.d N/A Requirements and Testing Procedures Removed requirements and testing procedures as vulnerability testing formerly in is addressed in through Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 10 of 20
11 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 Requirements and Testing Procedures Renumbered requirements and testing procedures due to merging and/or moving of previous requirements Removed circular reference from note. Consolidated testing procedures (formerly a and b) into single procedure 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 c to b Clarified requirement and testing procedure apply to change control processes and procedures. Imported content from former Testing Procedure 6.3.to align with imported testing procedures formerly Testing Procedure Removed wording or are sanitized before use to clarify intent. 6.4, 6.4.a 6.4.b 6.4.5, a b Updated requirement previously 6.4 to align with testing procedures previously 6.4.a 6.4.b, to address security patches and software modifications Requirements and Testing Procedures Renumbered to align with imported requirements and testing procedures (formerly ) Testing Procedure Clarified that documentation of impact is required in the testing procedure, to align with existing requirement. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 11 of 20
12 Requirement and Testing Procedure Clarified in requirement and testing procedure that approval is needed by authorized parties rather than management , a b Clarified intent of requirement and testing procedure formerly is for Functionality testing to verify that changes do not adversely impact the security of the system. Former Requirement merged into new Testing Procedure b, to address testing of custom code changes with reference to that secure coding and prevention of vulnerabilities applies to all custom-developed application types in scope, rather than only web applications. Removed dependency on OWASP and included other industry examples SANS CWE and CERT Requirements and Testing Procedures Vulnerabilities formerly updated and combined with former Requirement to reflect current guidance from CWE, CERT, and OWASP identified as vulnerabilities specific to web applications. N/A Requirement and Testing Procedure Added new requirement and testing procedure to address high-risk vulnerabilities identified in Requirement 6.2. Note: The ranking of vulnerabilities as defined in Requirement 6.2.a is considered a best practice until June 30, 2012, after which it becomes a requirement Clarified requirement for documented approval by authorized parties, rather than a form signed by management Note moved from testing procedure to requirement. Evolving Requirement Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 12 of 20
13 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) Requirement Added clarification and examples authentication methods 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 Requirements and Testing Procedures Added term identification , 8.5.7, 8.5.8, , 8.5.7, 8.5.8, Requirements and Testing Procedures Added authentication to allow for more flexibility for companies using other authentication mechanisms outside of passwords Included password resets as requiring unique value and immediate change after first use , a b Clarified access by vendors. Updated requirement to align with testing procedure. Separated Testing Procedure into individual Procedures a through b Testing Procedures Clarify password management requirements for non-consumer users from a service provider perspective. Separated single testing procedure to distinguish procedure for service providers, for each requirement , a , a d Clarified that restricting direct access or queries to databases applies to user access. Separated Testing Procedure a into individual Testing Procedures a through d. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 13 of 20
14 9 9 Introductory Paragraph Added terms and definitions for onsite personnel, visitor, and media, to be used throughout requirement. term onsite personnel replaces old term employee with a new definition to clarify intent of coverage a c Testing Procedures Separated testing procedure formerly into individual Testing Procedures a through c. d to video cameras and/or access control mechanisms in testing procedures, since video cameras are access monitoring mechanisms that may be used with access control mechanisms Requirement and Testing Procedure Replaced employee with onsite personnel. Added example of physically accessible areas Requirement and Testing Procedure Added networking/communications hardware and telecommunication lines to the list of items for restricting physical access. These were previously included in Requirement , 9.2.a 9.2, 9.2.a 9.2.b Replaced employee with onsite personnel. Separated Testing Procedure 9.2.a into individual Procedures 9.2.a through 9.2.b. 9.2.b 9.2.c Testing Procedures Clarified to verify that visitor badges are easily distinguished from onsite personnel Testing Procedure Clarified that testing procedure applies to visitor controls to align with requirement Testing Procedures Clarified procedure from attempting to gain access to ensuring that visitors are not permitted unescorted physical access to those areas. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 14 of 20
15 , a b Replaced employee with onsite personnel. Separated Testing Procedure into individual Procedures a through b. Clarified that Testing Procedure a is to verify that visitor ID badges are used and visitors are distinguishable from employees Replaced employee with onsite personnel a 9.5.b Testing Procedures Separated Testing Procedure 9.5 into individual Procedures 9.5.a through 9.5.b. Clarified that Testing Procedure 9.5.a is to observe the storage location s physical security Requirement and Testing Procedure Replaced paper and electronic media with all media as defined in the introductory paragraph. Moved networking, and communications hardware, telecommunication lines to Testing Procedure Requirements and Testing Procedures Replaced references to media that contain cardholder data with media as it is already defined in the introductory paragraph Requirement and Testing Procedure Clarified intent is to be able to determine sensitivity of data on media , Requirements and Testing Procedures Clarified that intent is to use time synchronization technology to synchronize system clocks and times, and to ensure time is properly acquired, distributed, and stored. d time synchronization and NTP to time synchronization technology throughout 10.4, and clarified that NTP is an example of time synchronization technology. Separated former Testing Procedures 10.4.a through 10.4.c into new sub-requirements and Testing Procedures through (see below). Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 15 of 20
16 sub-requirement from former Testing Procedure 10.4.b, to ensure critical systems have correct and consistent time. Restructured former Testing Procedure 10.4.b into new Testing Procedures a and b, to cover how time is acquired and distributed Sub a and b to clarify that time data is protected and changes to time settings are authorized c Requirement and Testing Procedure Restructured former 10.4.c into new subrequirement to ensure time is received from industry-accepted sources b 10.7.b Testing Procedures Clarified that the test should confirm that audit log processes are in place to immediately restore log data, rather than that log data should be immediately available for analysis Clarified that process should be in place to detect unauthorized wireless access points on a quarterly basis. Added flexibility that methods used may include wireless network scans, physical/logical inspections of system components and infrastructure, network access control (NAC), or wireless IDS/IPS, and that whichever methods are used, they must be sufficient to detect and identify any unauthorized devices a 11.1.c 11.1.a 11.1.e Testing Procedures Separated former Testing Procedure 11.1.a into individual Procedures 11.1.a and 11.1.c. Added new Testing Procedure 11.1.b to test that the methodology is adequate to detect unauthorized wireless access points. Renumbered former Testing Procedure 11.1.b to 11.1.d, and clarified that configuration for generating alerts to personnel applies if automatic monitoring is used. Renumbered former Testing Procedure 11.1.c to 11.1.e Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 16 of 20
17 , a a c 11.2.b a b 11.2.c a c Requirements and Testing Procedures Separated and renumbered internal & external scan requirements formerly 11.2 into individual Sub-Requirements and Testing Procedures through Moved note from former Testing Procedure 11.2.b to Requirement 11.2 to clarify that four internal and external scans must be verified. 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. 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). Testing Procedures Clarified requirements for internal & external scans to include rescans until high-risk vulnerabilities are addressed, and to be performed by qualified parties Clarified that noted exploitable vulnerabilities must be addressed. Separated Testing Procedure 11.3.a into individual Testing Procedures 11.3.a through 11.3.b Requirement and Testing Procedure Clarified that application penetration testing should test for relevant vulnerabilities and encompass all application types in scope Clarified that IDS/IPS monitor traffic at the perimeter and at key points inside the CDE, rather than all traffic in the CDE. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 17 of 20
18 , 11.5.a 11.5.b Requirement and Testing Procedure Replaced software with tools to clarify intent that commercial software is not sole means of meeting requirement. Added Testing Procedure 11.5.b to align with existing requirement to alert personnel to unauthorized modifications and to perform critical file comparisons at least weekly Requirement Title Replaced employees and contractors with all personnel Introductory Paragraph Replaced employees with personnel with a slightly revised definition Testing Procedures Replaced employees with personnel Requirement and Testing Procedure Added examples of risk assessment methodologies. Clarified that test should verify risk assessment documentation Requirement Replaced once a year with annually Requirement and Testing Procedure Removed employee-facing to clarify. Added tablet to example of technologies Requirement and Testing Procedure Replaced management with authorized parties Requirement and Testing Procedure Clarified to allow for logical labeling Requirement and Testing Procedure Added business partners to the requirement along with vendors , a b Provided flexibility to limit prohibitions to those personnel without authorization. Renumbered Testing Procedure to a. Added new Testing Procedure b to verify that personnel with proper authorization are protecting cardholder data in accordance with PCI DSS requirements. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 18 of 20
19 Requirements and Testing Procedures Replaced employees and contractors with personnel Requirement and Testing Procedure Replaced employees with personnel Replaced employees with personnel. Added note to provide guidance on varying methods depending on the role of personnel Requirement and Testing Procedure Replaced employees with personnel. Replaced company with entity Requirement and Testing Procedure Replaced employees with personnel. Moved example from testing procedure to requirement. Clarified the note in Requirement 12.7 to apply to potential personnel to be hired for certain positions Testing Procedure Replaced entity being assessed with entity for consistency Requirements and Testing Procedures Clarified requirement to monitor the service providers PCI DSS compliance status at least annually. Replace entity assessed to entity , a b Testing Procedure Added Testing Procedure b to clarify that test should include verifying that documented procedures are followed. Renumber Testing Procedure to a Testing Procedure Clarified that designated personnel should be available for 24/7 incident response to align with requirement. Appendix D Attestation of Compliance Merchants Attestation of Compliance Removed from Appendix as separate document. Reorganized Assessor and Merchant contact information. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 19 of 20
20 Appendix E Attestation of Compliance Service Providers Attestations of Compliance Removed from Appendix as separate document. Reorganized Assessor and Service Provider contact information. options provided in list of Services that were included in the Scope of the PCI DSS Assessment, and added list of services not covered by the PCI DSS assessment. Appendix F Appendix D Segmentation and Sampling of Business Facilities/System Components Renamed to clarify process flow for segmentation and sampling. Created separate section titles for network segmentation and sampling. Updated to align with sampling section in introduction. i Explanations of Type : Type Type Definition Clarifies intent of requirement. Ensure that concise wording in the standards portray the desired intent of requirements. guidance Explanatory Explanations and/or definitions to increase understanding or provide further information on a particular topic. Evolving Requirement Enhancements s to ensure that the standards are up to date with emerging threats and changes in the market. Summary of s from PCI DSS Version to 2.0 October 2010 Copyright 2010 PCI Security Standards Council LLC Page 20 of 20
The Prioritized Approach to Pursue PCI DSS Compliance
PCI DSS Prioritized Approach for PCI DSS.0 PCI DSS Prioritized Approach for PCI DSS.0 The Prioritized Approach to Pursue PCI DSS Compliance The Payment Card Industry Data Security Standard (PCI DSS) provides
Payment Card Industry (PCI) Data Security Standard. Summary of Changes from PCI DSS Version 3.0 to 3.1
Payment Card Industry (PCI) Data Security Standard Summary of Changes from PCI DSS Version 3.0 to 3.1 April 2015 Introduction This document provides a summary of changes from PCI DSS v3.0 to PCI DSS v3.1.
Payment Card Industry (PCI) Data Security Standard Requirements and Security Assessment Procedures Version 1.2.1 July 2009 Document Changes Date Version Description Pages October 2008 July 2009 1.2 1.2.1
PCI DSS v3.0 Vulnerability & Penetration Testing
PCI DSS impacts to your company
PCI DSS impacts to your company If an organization is involved in the storage, processing or transmission of cardholder data, then it is subject to the requirements of PCI DSS (Payment Card Industry Data
PCI DSS 3.1 Security Policy
PCI DSS 3.1 Security Policy Purpose This document outlines all of the policy items required by PCI to be compliant with the current PCI DSS 3.1 standard and that it is the University of Northern Colorado
PCI DSS 2.0 and PA-DSS 2.0 SUMMARY OF CHANGES - HIGHLIGHTS
Introduction 2.0 and PA-DSS 2.0 SUMMARY OF CHANGES - HIGHLIGHTS This document from the PCI Security Standards Council (PCI SSC) is designed to provide a transparent runway to the introduction of the new
Mapping PCI DSS 3.0 to Instant PCI Policy Below are the requirements from the PCI Data Security Standard, version 3.0. Each requirement is followed by a bullet point that tells exactly where that requirement
PCI DSS PCI Prioritized DSS Approach for for PCI DSS.0 The Prioritized Approach to Pursue PCI DSS Compliance The Payment Card Industry Data Security Standard (PCI DSS) provides a detailed, 1 requirements
Information Technology Standard for PCI systems Syracuse University Information Technology and Services PCI Network Security Standard (Appendix 1)
Appendixes Information Technology Standard for PCI systems Syracuse University Information Technology and Services PCI Network Security Standard (Appendix 1) 1.0 Scope All credit card data and its storage
PCI DSS Requirements Version 2.0 Milestone Network Box Comments. 6 Yes
Requirement 1: Install and maintain a firewall configuration to protect cardholder data 1.1 Establish firewall and router configuration standards that include the following: 1.1.1 A formal process for
Payment Card Industry (PCI) Payment Application Data Security Standard Requirements and Security Assessment Procedures Version 2.0 October 2010 Document Changes Date Version Description Pages October 1,
VMware Product Applicability Guide for. Payment Card Industry Data Security Standard
VMware Product Applicability Guide for Payment Card Industry Data Security Standard (PCI DSS) version 3.0 February 2014 V3.0 DESIGN DO CU MENT Table of Contents EXECUTIVE SUMMARY... 4 INTRODUCTION... 5
Preparing for PCI DSS 3.0 & Ensuring a Seamless Transition. November 2013
Preparing for PCI DSS 3.0 & Ensuring a Seamless Transition November 2013 Introductions Brian Serra PCI Practice Director Nick Puetz Managing Director - Strategic Services 2013 FishNet Security Inc. All
Secure Auditor PCI Compliance Statement
Payment Card Industry (PCI) Data Security Standard is an international information security standard assembled by the Payment Card Industry Security Standards Council (PCI SSC). The standard was created
ISO 27001 PCI DSS 2.0 Title Number Requirement
ISO 27001 PCI DSS 2.0 Title Number Requirement 4 Information security management system 4.1 General requirements 4.2 Establishing and managing the ISMS 4.2.1 Establish the ISMS 4.2.1.a 4.2.1.b 4.2.1.b.1
Payment Card Industry (PCI) Data Security Standard Requirements and Security Assessment Procedures Version 3.0 DRAFT November 2013 Document Changes Date Version Description Pages October 2008 1.2 July
Policy Pack Cross Reference to PCI DSS Version 3.1
Policy Pack Cross Reference to PCI DSS Version 3.1 Requirement 1: Install and maintain a firewall configuration to protect cardholder data 1.1 Establish and implement firewall and router configuration
The University of Texas at El Paso Payment Card Industry Standards and Procedures Standards, Procedures, and Forms That Conform to PCI DSS version 2.0 Policy Version 2.0 March 2012 About this Document
Payment Card Industry Data Security Standard Self-Assessment Questionnaire C-VT Guide
Payment Card Industry Data Security Standard Self-Assessment Questionnaire C-VT Guide Prepared for: University of Tennessee Merchants 12 April 2013 Prepared by: University of Tennessee System Administration
Payment Card Industry (PCI) Data Security Standard. Version 1.1
Payment Card Industry (PCI) Data Security Standard Version 1.1 Release: September, 2006 Build and Maintain a Secure Network Requirement 1: Requirement 2: Install and maintain a firewall configuration to
Payment Card Industry (PCI) Data Security Standard Report on Compliance. PCI DSS v3.2 Template for Report on Compliance. Revision 1.0.
Payment Card Industry (PCI) Data Security Standard Report on Compliance PCI DSS v3.2 Template for Report on Compliance Revision 1.0 April 2016 Document Changes Date Version Description February 2014 July
Visa Asia Pacific Account Information Security (AIS) Program Payment Application Best Practices (PABP)
Visa Asia Pacific Account Information Security (AIS) Program Payment Application Best Practices (PABP) This document is to be used for payment application vendors to validate that the payment application
Using Automated, Detailed Configuration and Change Reporting to Achieve and Maintain PCI Compliance Part 2
Using Automated, Detailed Configuration and Change Reporting to Achieve and Maintain PCI Compliance Part 2 An in-depth look at Payment Card Industry Data Security Standard Requirements 1, 2, 3, 4 Alex
Payment Card Industry (PCI) Point-to-Point Encryption. Template for Report on Validation for use with P2PE v2.0 (Revision 1.1) for P2PE Application
Payment Card Industry (PCI) Point-to-Point Encryption Template for Report on Validation for use with P2PE v2.0 (Revision 1.1) for P2PE Application Revision 1.0 November 2015 Document Changes Date Use with
PCI 3.0 and Managed Security:
PCI 3.0 and Managed Security: How Network Box can help you with PCI compliance COPYRIGHT 2013 NETWORK BOX USA, INC. 1 COPYRIGHT 2013 NETWORK BOX USA, INC. 2825 WILCREST DRIVE, SUITE 259 HOUSTON, TX 77042
Transitioning from PCI DSS 2.0 to 3.1
Transitioning from PCI DSS 2.0 to 3.1 What You Need to Know April, 2015 Emma Sutcliffe, Director, Data Security Standards About the PCI Council Founded in 2006 - Guiding open standards for payment card
Payment Card Industry Self-Assessment Questionnaire
How to Complete the Questionnaire The questionnaire is divided into six sections. Each section focuses on a specific area of security, based on the requirements included in the PCI Data Security Standard.
Tagging PCI groups in OSSEC rules. PCI DSS Requirements v3.1 N/A N/A N/A N/A N/A N/A N/A N/A
Requirement 1: Install and maintain a firewall configuration to protect cardholder data 1.1 Establish and implement firewall and router configuration standards that include the following: 1.1.1 A formal
Using Skybox Solutions to Ensure PCI Compliance. Achieve efficient and effective PCI compliance by automating many required controls and processes
Using Skybox Solutions to Ensure PCI Compliance Achieve efficient and effective PCI compliance by automating many required controls and processes WHITEPAPER Executive Summary The Payment Card Industry
Three Critical Success Factors for PCI Assessment. Seth Peter NetSPI April 21, 2010
Three Critical Success Factors for PCI Assessment Seth Peter NetSPI April 21, 2010 Introduction Seth Peter NetSPI Chief Technology Officer and Founder 15 year history of application, system, and network
PCI DSS v2.0. Compliance Guide
PCI DSS v2.0 Compliance Guide May 2012 PCI DSS v2.0 Compliance Guide What is PCI DSS? Negative media coverage, a loss of customer confidence, and the resulting loss in sales can cripple a business. As