PCI DSS Self Assessment Questionnaire (SAQ) Form D

PCI DSS Self Assessment Questionnaire (SAQ) Form D
PCI DSS Requirment Requirement Section 1

1.1 Establish firewall and router configuration standards that include the following: 1.1 Obtain and inspect the firewall and router configuration standards and other documentation specified below to verify that standards are complete. Complete the following: 1.1.1 Verify that there is a formal process for testing and approval of all network connections and changes to firewall and router configurations.
Testing Procedure or Question
Owner
Area
Completed (Yes/No/NA)
Notes / Questions
Unassigned
Unassigned
No
1.1.1 A formal process for approving and testing all network connections and changes to the firewall and router configurations
Unassigned
Unassigned
No
1.1.2 Current network diagram with all connections to 1.1.2.a Verify that a current network diagram (for cardholder data, including any wireless networks example, one that shows cardholder data flows over the network) exists and that it documents all connections to cardholder data, including any wireless networks. 1.1.2.b Verify that the diagram is kept current. 1.1.3 Requirements for a firewall at each Internet connection and between any demilitarized zone (DMZ) and the internal network zone 1.1.3.a Verify that firewall configuration standards include requirements for a firewall at each Internet connection and between any DMZ and the internal network zone. 1.1.3.b Verify that the current network diagram is consistent with the firewall configuration standards.
Unassigned
Unassigned
No
Unassigned Unassigned
No No
Unassigned
Unassigned
No
1.1.4 Description of groups, roles, and responsibilities 1.1.4 Verify that firewall and router configuration for logical management of network components standards include a description of groups, roles, and responsibilities for logical management of network components. 1.1.5 Documentation and business justification for use 1.1.5.a Verify that firewall and router configuration of all services, protocols, and ports allowed, including standards include a documented list of services, documentation of security features implemented for protocols and ports necessary for businessfor those protocols considered to be insecure. example, hypertext transfer protocol (HTTP) and Secure Sockets Layer (SSL), Secure Shell (SSH), and Virtual Private Network (VPN) protocols. Examples of insecure services, protocols, or ports include but are not limited to FTP, Telnet, POP3, IMAP, and SNMP. 1.1.5.b Identify insecure services, protocols, and ports allowed; and verify they are necessary and that security features are documented and implemented by examining firewall and router configuration standards and settings for each service. 1.1.6.a Verify that firewall and router configuration standards require review of firewall and router rule sets at least every six months.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
1.1.6 Requirement to review firewall and router rule sets at least every six months
Unassigned
Unassigned
No
1.1.6.b Obtain and examine documentation to verify that the rule sets are reviewed at least every six months. 1.2 Build firewall and router configurations that restrict 1.2 Examine firewall and router configurations to verify connections between untrusted networks and any that connections are restricted between untrusted system components in the cardholder data networks and system components in the cardholder environment. data environment, as follows: Note: An untrusted network is any network that is external to the networks belonging to the entity under review, and/or which is out of the entity's ability to control or manage. 1.2.1 Restrict inbound and outbound traffic to that 1.2.1.a Verify that inbound and outbound traffic is which is necessary for the cardholder data limited to that which is necessary for the cardholder environment. data environment, and that the restrictions are documented. 1.2.1.b Verify that all other inbound and outbound traffic is specifically denied, for example by using an explicit deny all or an implicit deny after allow statement. 1.2.2 Secure and synchronize router configuration 1.2.2 Verify that router configuration files are secure files. and synchronizedfor example, running configuration files (used for normal running of the routers) and startup configuration files (used when machines are rebooted), have the same, secure configurations. 1.2.3 Install perimeter firewalls between any wireless networks and the cardholder data environment, and configure these firewalls to deny or control (if such traffic is necessary for business purposes) any traffic from the wireless environment into the cardholder data environment. 1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment. 1.2.3 Verify that there are perimeter firewalls installed between any wireless networks and systems that store cardholder data, and that these firewalls deny or control (if such traffic is necessary for business purposes) any traffic from the wireless environment into the cardholder data environment. 1.3 Examine firewall and router configurationsincluding but not limited to the choke router at the Internet, the DMZ router and firewall, the DMZ cardholder segment, the perimeter router, and the internal cardholder network segmentto determine that there is no direct access between the Internet and system components in the internal cardholder network segment, as detailed below.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.
1.3.1 Verify that a DMZ is implemented to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports. 1.3.2 Limit inbound Internet traffic to IP addresses 1.3.2 Verify that inbound Internet traffic is limited to IP within the DMZ. addresses within the DMZ. 1.3.3 Do not allow any direct connections inbound or 1.3.3 Verify direct connections inbound or outbound outbound for traffic between the Internet and the are not allowed for traffic between the Internet and the cardholder data environment. cardholder data environment. 1.3.4 Do not allow internal addresses to pass from the 1.3.4 Verify that internal addresses cannot pass from Internet into the DMZ. the Internet into the DMZ. 1.3.5 Do not allow unauthorized outbound traffic from 1.3.5 Verify that outbound traffic from the cardholder the cardholder data environment to the Internet. data environment to the Internet is explicitly authorized 1.3.6 Implement stateful inspection, also known as dynamic packet filtering. (That is, only established connections are allowed into the network.) 1.3.6 Verify that the firewall performs stateful inspection (dynamic packet filtering). (Only established connections should be allowed in, and only if they are associated with a previously established session.)
Unassigned
Unassigned
No
No No
No No
Unassigned
Unassigned
No
196511261.xls.ms_office
12/18/2013

PCI DSS Requirment
1.3.7 Place system components that store cardholder data (such as a database) in an internal network zone, segregated from the DMZ and other untrusted networks. 1.3.8 Do not disclose private IP addresses and routing information to unauthorized parties. Note: Methods to obscure IP addressing may include, but are not limited to: Network Address Translation (NAT) Placing servers containing cardholder data behind proxy servers/firewalls or content caches, Removal or filtering of route advertisements for private networks that employ registered addressing, 1.3.8.b Verify that any disclosure of private IP addresses and routing information to external entities is authorized. 1.4 Install personal firewall software on any mobile 1.4.a Verify that mobile and/or employee-owned and/or employee-owned computers with direct computers with direct connectivity to the Internet (for connectivity to the Internet (for example, laptops used example, laptops used by employees), and which are by employees), which are used to access the used to access the organizations network, have organizations network. personal firewall software installed and active. 1.4.b Verify that the personal firewall software is configured by the organization to specific standards and is not alterable by users of mobile and/or employee-owned computers. Internal use of RFC1918 address space instead of registered addresses.

1.3.7 Verify that system components that store cardholder data are on an internal network zone, segregated from the DMZ and other untrusted networks. 1.3.8.a Verify that methods are in place to prevent the disclosure of private IP addresses and routing information from internal networks to the Internet.
Owner
Unassigned
Area
Unassigned
No
Notes / Questions
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013

2.1 Always change vendor-supplied defaults before installing a system on the network, including but not limited to passwords, simple network management protocol (SNMP) community strings, and elimination of unnecessary accounts. 2.1 Choose a sample of system components, and attempt to log on (with system administrator help) to the devices using default vendor-supplied accounts and passwords, to verify that default accounts and passwords have been changed. (Use vendor manuals and sources on the Internet to find vendor-supplied accounts/passwords.)
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
2.1.1 For wireless environments connected to the 2.1.1 Verify the following regarding vendor default cardholder data environment or transmitting settings for wireless environments: cardholder data, change wireless vendor defaults, including but not limited to default wireless encryption keys, passwords, and SNMP community strings. 2.1.1.a Verify encryption keys were changed from default at installation, and are changed anytime anyone with knowledge of the keys leaves the company or changes positions 2.1.1.b Verify default SNMP community strings on wireless devices were changed. 2.1.1.c Verify default passwords/passphrases on access points were changed. 2.1.1.d Verify firmware on wireless devices is updated to support strong encryption for authentication and transmission over wireless networks. 2.1.1.e Verify other security-related wireless vendor defaults were changed, if applicable. 2.2.a Examine the organizations system configuration standards for all types of system components and verify the system configuration standards are consistent with industry-accepted hardening standards.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned Unassigned Unassigned
No No No
No No
2.2 Develop configuration standards for all system components. Assure that these standards address all known security vulnerabilities and are consistent with industry-accepted system hardening standards. Sources of industry-accepted system hardening standards may include, but are not limited to: Center for Internet Security (CIS)
International Organization for Standardization (ISO) 2.2.b Verify that system configuration standards are updated as new vulnerability issues are identified, as defined in Requirement 6.2. SysAdmin Audit Network Security (SANS) Institute 2.2.c Verify that system configuration standards are applied when new systems are configured. National Institute of Standards Technology (NIST) 2.2.d Verify that system configuration standards include each item below (2.2.1 2.2.4). 2.2.1 Implement only one primary function per server 2.2.1.a For a sample of system components, verify to prevent functions that require different security that only one primary function is implemented per levels from co-existing on the same server. (For server. example, web servers, database servers, and DNS should be implemented on separate servers.) Note: Where virtualization technologies are in use, implement only one primary function per virtual system component. 2.2.1.b If virtualization technologies are used, verify that only one primary function is implemented per virtual system component or device. 2.2.2 Enable only necessary and secure services, protocols, daemons, etc., as required for the function of the system. 2.2.2.a For a sample of system components, inspect enabled system services, daemons, and protocols. Verify that only necessary services or protocols are enabled. Implement security features for any required services, 2.2.2.b Identify any enabled insecure services, protocols or daemons that are considered to be daemons, or protocols. Verify they are justified and insecurefor example, use secured technologies that security features are documented and such as SSH, S-FTP, SSL, or IPSec VPN to protect implemented. insecure services such as NetBIOS, file-sharing, Telnet, FTP, etc. 2.2.3 Configure system security parameters to prevent misuse. 2.2.3.a Interview system administrators and/or security managers to verify that they have knowledge of common security parameter settings for system components. 2.2.3.b Verify that common security parameter settings are included in the system configuration standards. 2.2.3.c For a sample of system components, verify that common security parameters are set appropriately. 2.2.4.a For a sample of system components, verify that all unnecessary functionality (for example, scripts, drivers, features, subsystems, file systems, etc.) is removed. 2.2.4.b. Verify enabled functions are documented and support secure configuration. 2.2.4.c. Verify that only documented functionality is present on the sampled system components. 2.3 For a sample of system components, verify that non-console administrative access is encrypted by performing the following: 2.3.a Observe an administrator log on to each system to verify that a strong encryption method is invoked before the administrators password is requested. 2.3.b Review services and parameter files on systems to determine that Telnet and other remote login commands are not available for use internally. 2.3.c Verify that administrator access to the webbased management interfaces is encrypted with strong cryptography. 2.4 Perform testing procedures A.1.1 through A.1.4 detailed in Appendix A: Additional PCI DSS Requirements for Shared Hosting Providers for PCI DSS assessments of shared hosting providers, to verify that shared hosting providers protect their entities (merchants and service providers) hosted environment and data.
Unassigned
Unassigned
No
No No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
2.2.4 Remove all unnecessary functionality, such as scripts, drivers, features, subsystems, file systems, and unnecessary web servers.
Unassigned
Unassigned
No
No No No
2.3 Encrypt all non-console administrative access using strong cryptography. Use technologies such as SSH, VPN, or SSL/TLS for web-based management and other non-console administrative access.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
2.4 Shared hosting providers must protect each entitys hosted environment and cardholder data. These providers must meet specific requirements as detailed in Appendix A: Additional PCI DSS Requirements for Shared Hosting Providers.
Unassigned
Unassigned
No
12/18/2013

PCI DSS Requirment Testing Procedure or Question Owner Area Completed (Yes/No/NA) Notes / Questions
12/18/2013

3.1 Keep cardholder data storage to a minimum by implementing data retention and disposal policies, procedures and processes, as follows. 3.1.1 Implement a data retention and disposal policy that includes: Limiting data storage amount and retention time to that which is required for legal, regulatory, and business requirements Processes for secure deletion of data when no longer needed 3.1 Obtain and examine the policies, procedures and processes for data retention and disposal, and perform the following: 3.1.1.a Verify that policies and procedures are implemented and include legal, regulatory, and business requirements for data retention, including specific requirements for retention of cardholder data (for example, cardholder data needs to be held for X period for Y business reasons). 3.1.1.b Verify that policies and procedures include provisions for secure disposal of data when no longer needed for legal, regulatory, or business reasons, including disposal of cardholder data.
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Specific retention requirements for cardholder data 3.1.1.c Verify that policies and procedures include coverage for all storage of cardholder data. A quarterly automatic or manual process for identifying and securely deleting stored cardholder data that exceeds defined retention requirements A programmatic process (automatic or manual) to remove, at least quarterly, stored cardholder data that exceeds requirements defined in the data retention policy Requirements for a review, conducted at least quarterly, to verify that stored cardholder data does not exceed requirements defined in the data retention policy. 3.1.1.e For a sample of system components that store cardholder data, verify that the data stored does not exceed the requirements defined in the data retention policy. 3.2.a For issuers and/or companies that support issuing services and store sensitive authentication data, verify there is a business justification for the storage of sensitive authentication data, and that the data is secured. 3.2.b For all other entities, if sensitive authentication data is received and deleted, obtain and review the processes for securely deleting the data to verify that the data is unrecoverable. 3.1.1.d Verify that policies and procedures include at least one of the following:
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
3.2 Do not store sensitive authentication data after authorization (even if encrypted).
Unassigned
Unassigned
No
Sensitive authentication data includes the data as cited in the following Requirements 3.2.1 through 3.2.3:
Unassigned
Unassigned
No
Note: It is permissible for issuers and companies that 3.2.c For each item of sensitive authentication data support issuing services to store sensitive below, perform the following steps: authentication data if there is a business justification and the data is stored securely. 3.2.1 Do not store the full contents of any track (from the magnetic stripe located on the back of a card, equivalent data contained on a chip, or elsewhere). This data is alternatively called full track, track, track 1, track 2, and magnetic-stripe data. Note: In the normal course of business, the following data elements from the magnetic stripe may need to be retained: The cardholders name Primary account number (PAN) Expiration date Service code To minimize risk, store only these data elements as needed for business. 3.2.2 Do not store the card verification code or value (three-digit or four-digit number printed on the front or back of a payment card) used to verify card-notpresent transactions. 3.2.1 For a sample of system components, examine data sources, including but not limited to the following, and verify that the full contents of any track from the magnetic stripe on the back of card or equivalent data on a chip are not stored under any circumstance: Incoming transaction data
Unassigned
Unassigned
No
Unassigned
Unassigned
No
All logs (for example, transaction, history, debugging, error) History files Trace files Several database schemas Database contents 3.2.2 For a sample of system components, examine data sources, including but not limited to the following, and verify that the three-digit or four-digit card verification code or value printed on the front of the card or the signature panel (CVV2, CVC2, CID, CAV2 data) is not stored under any circumstance: Incoming transaction data All logs (for example, transaction, history, debugging, error) History files Trace files Several database schemas Database contents 3.2.3 For a sample of system components, examine data sources, including but not limited to the following and verify that PINs and encrypted PIN blocks are not stored under any circumstance: Incoming transaction data All logs (for example, transaction, history, debugging, error) History files Trace files Several database schemas Database contents 3.3 Obtain and examine written policies and examine displays of PAN (for example, on screen, on paper receipts) to verify that primary account numbers (PANs) are masked when displaying cardholder data, except for those with a legitimate business need to see full PAN.
Unassigned
Unassigned
No
3.2.3 Do not store the personal identification number (PIN) or the encrypted PIN block.
Unassigned
Unassigned
No
3.3 Mask PAN when displayed (the first six and last four digits are the maximum number of digits to be displayed). Notes: This requirement does not apply to employees and other parties with a legitimate business need to see the full PAN. This requirement does not supersede stricter requirements in place for displays of cardholder datafor example, for point-of-sale (POS) receipts.
Unassigned
Unassigned
No
12/18/2013

PCI DSS Requirment Testing Procedure or Question Owner
Unassigned
Area
Unassigned
No
Notes / Questions
3.4 Render PAN unreadable anywhere it is stored 3.4.a Obtain and examine documentation about the (including on portable digital media, backup media, system used to protect the PAN, including the vendor, and in logs) by using any of the following approaches: type of system/process, and the encryption algorithms (if applicable). Verify that the PAN is rendered unreadable using any of the following methods: One-way hashes based on strong cryptography One-way hashes based on strong cryptography (hash must be of the entire PAN) Truncation (hashing cannot be used to replace the Truncation truncated segment of PAN) Index tokens and pads (pads must be securely Index tokens and pads, with the pads being stored) securely stored Strong cryptography with associated key Strong cryptography, with associated keymanagement processes and procedures management processes and procedures Note: It is a relatively trivial effort for a malicious 3.4.b Examine several tables or files from a sample of individual to reconstruct original PAN data if they data repositories to verify the PAN is rendered have access to both the truncated and hashed unreadable (that is, not stored in plain-text). version of a PAN. Where hashed and truncated versions of the same PAN are present in an entitys environment, additional controls should be in place to ensure that the hashed and truncated versions cannot be correlated to reconstruct the original PAN. 3.4.c Examine a sample of removable media (for example, back-up tapes) to confirm that the PAN is rendered unreadable. 3.4.d Examine a sample of audit logs to confirm that the PAN is rendered unreadable or removed from the logs. 3.4.1.a If disk encryption is used, verify that logical access to encrypted file systems is implemented via a mechanism that is separate from the native operating systems mechanism (for example, not using local user account databases). 3.4.1.b Verify that cryptographic keys are stored securely (for example, stored on removable media that is adequately protected with strong access controls). 3.4.1.c Verify that cardholder data on removable media is encrypted wherever stored. Note: If disk encryption is not used to encrypt removable media, the data stored on this media will need to be rendered unreadable through some other method. 3.5 Verify processes to protect keys used for encryption of cardholder data against disclosure and misuse by performing the following:
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
3.4.1 If disk encryption is used (rather than file- or column-level database encryption), logical access must be managed independently of native operating system access control mechanisms (for example, by not using local user account databases). Decryption keys must not be tied to user accounts.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
3.5 Protect any keys used to secure cardholder data against disclosure and misuse: Note: This requirement also applies to keyencrypting keys used to protect data-encrypting keyssuch key-encrypting keys must be at least as strong as the data-encrypting key . 3.5.1 Restrict access to cryptographic keys to the fewest number of custodians necessary. 3.5.2 Store cryptographic keys securely in the fewest possible locations and forms.
Unassigned
Unassigned
No
3.5.1 Examine user access lists to verify that access to keys is restricted to the fewest number of custodians necessary. 3.5.2.a Examine system configuration files to verify that keys are stored in encrypted format and that keyencrypting keys are stored separately from dataencrypting keys. 3.5.2.b Identify key storage locations to verify that keys are stored in the fewest possible locations and forms. 3.6.a Verify the existence of key-management procedures for keys used for encryption of cardholder data. 3.6.b For service providers only: If the service provider shares keys with their customers for transmission or storage of cardholder data, verify that the service provider provides documentation to customers that includes guidance on how to securely transmit, store and update customers keys, in accordance with Requirements 3.6.1 through 3.6.8 below. 3.6.c Examine the key-management procedures and perform the following: 3.6.1 Verify that key-management procedures are implemented to require the generation of strong keys. 3.6.2 Verify that key-management procedures are implemented to require secure key distribution.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
3.6 Fully document and implement all keymanagement processes and procedures for cryptographic keys used for encryption of cardholder data, including the following: Note: Numerous industry standards for key management are available from various resources including NIST, which can be found at http://csrc.nist.gov.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
No No
3.6.1 Generation of strong cryptographic keys
3.6.2 Secure cryptographic key distribution
Unassigned
Unassigned
No
3.6.3 Secure cryptographic key storage
3.6.3 Verify that key-management procedures are implemented to require secure key storage. 3.6.4 Cryptographic key changes for keys that have 3.6.4 Verify that key-management procedures are reached the end of their cryptoperiod (for example, implemented to require periodic key changes at the after a defined period of time has passed and/or after end of the defined cryptoperiod. a certain amount of cipher-text has been produced by a given key), as defined by the associated application vendor or key owner, and based on industry best practices and guidelines (for example, NIST Special Publication 800-57). 3.6.5 Retirement or replacement (for example, 3.6.5.a Verify that key-management procedures are archiving, destruction, and/or revocation) of keys as implemented to require the retirement of keys when deemed necessary when the integrity of the key has the integrity of the key has been weakened. been weakened (for example, departure of an employee with knowledge of a clear-text key), or keys are suspected of being compromised. Note: If retired or replaced cryptographic keys need to be retained, these keys must be securely archived (for example, by using a key encryption key). Archived cryptographic keys should only be used for decryption/verification purposes. 3.6.5.b Verify that the key-management procedures are implemented to require the replacement of known or suspected compromised keys.
No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013

PCI DSS Requirment Testing Procedure or Question
3.6.5.c If retired or replaced cryptographic keys are retained, verify that these keys are not used for encryption operations. 3.6.6 Verify that manual clear-text key-management procedures require split knowledge and dual control of keys.
Owner
Unassigned
Area
Unassigned
No
Notes / Questions
3.6.6 If manual clear-text cryptographic key management operations are used, these operations must be managed using split knowledge and dual control (for example, requiring two or three people, each knowing only their own key component, to reconstruct the whole key). Note: Examples of manual key management operations include, but are not limited to: key generation, transmission, loading, storage and destruction. 3.6.7 Prevention of unauthorized substitution of cryptographic keys.
Unassigned
Unassigned
No
3.6.7 Verify that key-management procedures are implemented to require the prevention of unauthorized substitution of keys. 3.6.8 Requirement for cryptographic key custodians to 3.6.8 Verify that key-management procedures are formally acknowledge that they understand and implemented to require key custodians to accept their key-custodian responsibilities. acknowledge (in writing or electronically) that they understand and accept their key-custodian responsibilities.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013

4.1 Use strong cryptography and security protocols (for example, SSL/TLS, IPSEC, SSH, etc.) to safeguard sensitive cardholder data during transmission over open, public networks. Examples of open, public networks that are in scope of the PCI DSS include but are not limited to: The Internet 4.1 Verify the use of security protocols wherever cardholder data is transmitted or received over open, public networks. Verify that strong cryptography is used during data transmission, as follows: 4.1.a Select a sample of transactions as they are received and observe transactions as they occur to verify that cardholder data is encrypted during transit. 4.1.b Verify that only trusted keys and/or certificates are accepted. 4.1.c Verify that the protocol is implemented to use only secure configurations, and does not support insecure versions or configurations. 4.1.d Verify that the proper encryption strength is implemented for the encryption methodology in use. (Check vendor recommendations/best practices.)
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Wireless technologies, Global System for Mobile communications (GSM)
No No
General Packet Radio Service (GPRS).
Unassigned
Unassigned
No
4.1.e For SSL/TLS implementations: Verify that HTTPS appears as a part of the browser Universal Record Locator (URL). Verify that no cardholder data is required when HTTPS does not appear in the URL. 4.1.1 Ensure wireless networks transmitting 4.1.1 For wireless networks transmitting cardholder cardholder data or connected to the cardholder data data or connected to the cardholder data environment, use industry best practices (for example, environment, verify that industry best practices (for IEEE 802.11i) to implement strong encryption for example, IEEE 802.11i) are used to implement strong authentication and transmission. encryption for authentication and transmission. Note: The use of WEP as a security control was prohibited as of 30 June 2010. 4.2 Never send unprotected PANs by end-user 4.2.a Verify that PAN is rendered unreadable or messaging technologies (for example, e-mail, instant secured with strong cryptography whenever it is sent messaging, chat, etc.). via end-user messaging technologies. 4.2.b Verify the existence of a policy stating that unprotected PANs are not to be sent via end-user messaging technologies.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013

5.1 Deploy anti-virus software on all systems 5.1 For a sample of system components including all commonly affected by malicious software (particularly operating system types commonly affected by personal computers and servers). malicious software, verify that anti-virus software is deployed if applicable anti-virus technology exists. 5.1.1 Ensure that all anti-virus programs are capable of detecting, removing, and protecting against all known types of malicious software.
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
5.1.1 For a sample of system components, verify that all anti-virus programs detect, remove, and protect against all known types of malicious software (for example, viruses, Trojans, worms, spyware, adware, and rootkits).
Unassigned
Unassigned
No
5.2 Ensure that all anti-virus mechanisms are current, 5.2 Verify that all anti-virus software is current, actively actively running, and generating audit logs. running, and generating logs by performing the following: 5.2.a Obtain and examine the policy and verify that it requires updating of anti-virus software and definitions. 5.2.b Verify that the master installation of the software is enabled for automatic updates and periodic scans. 5.2.c For a sample of system components including all operating system types commonly affected by malicious software, verify that automatic updates and periodic scans are enabled. 5.2.d For a sample of system components, verify that anti-virus software log generation is enabled and that such logs are retained in accordance with PCI DSS Requirement 10.7.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013

6.1 Ensure that all system components and software are protected from known vulnerabilities by having the latest vendor-supplied security patches installed. Install critical security patches within one month of release. Note: An organization may consider applying a riskbased approach to prioritize their patch installations. For example, by prioritizing critical infrastructure (for example, public-facing devices and systems, databases) higher than less-critical internal devices, to ensure high-priority systems and devices are addressed within one month, and addressing less critical devices and systems within three months. 6.2 Establish a process to identify and assign a risk ranking to newly discovered security vulnerabilities. Notes: Risk rankings should be based on industry best practices. For example, criteria for ranking High risk vulnerabilities may include a CVSS base score of 4.0 or above, and/or a vendor-supplied patch classified by the vendor as critical, and/or a vulnerability affecting a critical system component. 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. 6.3 Develop software applications (internal and external, and including web-based administrative access to applications) in accordance with PCI DSS (for example, secure authentication and logging), and based on industry best practices. Incorporate information security throughout the software development life cycle. These processes must include the following: 6.1.a For a sample of system components and related software, compare the list of security patches installed on each system to the most recent vendor security patch list, to verify that current vendor patches are installed. 6.1.b Examine policies related to security patch installation to verify they require installation of all critical new security patches within one month.
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
Unassigned
Unassigned
No
6.2.a Interview responsible personnel to verify that processes are implemented to identify new security vulnerabilities, and that a risk ranking is assigned to such vulnerabilities. (At minimum, the most critical, highest risk vulnerabilities should be ranked as High.
Unassigned
Unassigned
No
6.2.b Verify that processes to identify new security vulnerabilities include using outside sources for security vulnerability information. 6.3.a Obtain and examine written software development processes to verify that the processes are based on industry standards and/or best practices. 6.3.b Examine written software development processes to verify that information security is included throughout the life cycle. 6.3.c Examine written software development processes to verify that software applications are developed in accordance with PCI DSS. 6.3.d From an examination of written software development processes, and interviews of software developers, verify that: 6.3.1 Custom application accounts, user IDs and/or passwords are removed before system goes into production or is released to customers. 6.3.2.a Obtain and review policies to confirm that all custom application code changes must be reviewed (using either manual or automated processes) as follows: Code changes are reviewed by individuals other than the originating code author, and by individuals who are knowledgeable in code review techniques and secure coding practices. Code reviews ensure code is developed according to secure coding guidelines (see PCI DSS Requirement 6.5).
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
6.3.1 Removal of custom application accounts, user IDs, and passwords before applications become active or are released to customers 6.3.2 Review of custom code prior to release to production or customers in order to identify any potential coding vulnerability. Note: This requirement for code reviews applies to all custom code (both internal and public-facing), as part of the system development life cycle. Code reviews can be conducted by knowledgeable internal personnel or third parties. Web applications are also subject to additional controls, if they are public facing, to address ongoing threats and vulnerabilities after implementation, as defined at PCI DSS Requirement 6.6.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Appropriate corrections are implemented prior to release. Code review results are reviewed and approved by management prior to release. 6.3.2.b Select a sample of recent custom application changes and verify that custom application code is reviewed according to 6.3.2.a, above. 6.4 Follow change control processes and procedures 6.4 From an examination of change control for all changes to system components. The processes, interviews with system and network processes must include the following: administrators, and examination of relevant data (network configuration documentation, production and test data, etc.), verify the following: 6.4.1 Separate development/test and production environments 6.4.1 The development/test environments are separate from the production environment, with access control in place to enforce the separation.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
6.4.2 Separation of duties between development/test and production environments
6.4.2 There is a separation of duties between personnel assigned to the development/test environments and those assigned to the production environment. 6.4.3 Production data (live PANs) are not used for 6.4.3 Production data (live PANs) are not used for testing or development testing or development. 6.4.4 Removal of test data and accounts before 6.4.4 Test data and accounts are removed before a production systems become active production system becomes active. 6.4.5 Change control procedures for the 6.4.5.a Verify that change-control procedures related implementation of security patches and software to implementing security patches and software modifications. Procedures must include the following: modifications are documented and require items 6.4.5.1 6.4.5.4 below. 6.4.5.b For a sample of system components and recent changes/security patches, trace those changes back to related change control documentation. For each change examined, perform the following: 6.4.5.1 Documentation of impact. 6.4.5.1 Verify that documentation of impact is included in the change control documentation for each sampled change. 6.4.5.2 Verify that documented approval by authorized parties is present for each sampled change.
Unassigned
Unassigned
No
No No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
6.4.5.2 Documented change approval by authorized parties.
Unassigned
Unassigned
No
12/18/2013

PCI DSS Requirment
6.4.5.3 Functionality testing to verify that the change does not adversely impact the security of the system.

6.4.5.3.a For each sampled change, verify that functionality testing is performed to verify that the change does not adversely impact the security of the system. 6.4.5.3.b For custom code changes, verify that all updates are tested for compliance with PCI DSS Requirement 6.5 before being deployed into production. 6.4.5.4 Verify that back-out procedures are prepared for each sampled change. 6.5.a Obtain and review software development processes. Verify that processes require training in secure coding techniques for developers, based on industry best practices and guidance.
Owner
Unassigned
Area
Unassigned
No
Notes / Questions
Unassigned
Unassigned
No
6.4.5.4 Back-out procedures. 6.5 Develop applications based on secure coding guidelines. Prevent common coding vulnerabilities in software development processes, to include the following:
No No
Note: The vulnerabilities listed at 6.5.1 through 6.5.9 6.5.b Interview a sample of developers and obtain were current with industry best practices when this evidence that they are knowledgeable in secure version of PCI DSS was published. However, as coding techniques. industry best practices for vulnerability management are updated (for example, the OWASP Guide, SANS CWE Top 25, CERT Secure Coding, etc.), the current best practices must be used for these requirements. 6.5.c. Verify that processes are in place to ensure that applications are not vulnerable to, at a minimum, the following: 6.5.1 Injection flaws, particularly SQL injection. (Validate input to verify user data cannot modify meaning of commands and queries, utilize parameterized queries, etc.) 6.5.2 Buffer overflow (Validate buffer boundaries and truncate input strings.) 6.5.3 Insecure cryptographic storage (Prevent cryptographic flaws) 6.5.4 Insecure communications (Properly encrypt all authenticated and sensitive communications) 6.5.5 Improper error handling (Do not leak information via error messages) 6.5.6 All High vulnerabilities as identified in PCI DSS Requirement 6.2.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
6.5.1 Injection flaws, particularly SQL injection. Also consider OS Command Injection, LDAP and XPath injection flaws as well as other injection flaws. 6.5.2 Buffer overflow 6.5.3 Insecure cryptographic storage 6.5.4 Insecure communications
Unassigned
Unassigned
No
No No No
6.5.5 Improper error handling
No No
6.5.6 All High vulnerabilities identified in the vulnerability identification process (as defined in PCI DSS Requirement 6.2). Note: This requirement is considered a best practice until June 30, 2012, after which it becomes a requirement. Note: Requirements 6.5.7 through 6.5.9, below, apply to web applications and application interfaces (internal or external): 6.5.7 Cross-site scripting (XSS) 6.5.7 Cross-site scripting (XSS) (Validate all parameters before inclusion, utilize context-sensitive escaping, etc.) 6.5.8 Improper Access Control (such as insecure 6.5.8 Improper Access Control, such as insecure direct object references, failure to restrict URL direct object references, failure to restrict URL access, access, and directory traversal) and directory traversal (Properly authenticate users and sanitize input. Do not expose internal object references to users.) 6.5.9 Cross-site request forgery (CSRF) 6.5.9 Cross-site request forgery (CSRF). (Do not reply on authorization credentials and tokens automatically submitted by browsers.) 6.6 For public-facing web applications, ensure that either one of the following methods are in place as follows:
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
6.6 For public-facing web applications, address
Unassigned
Unassigned
No
new threats and vulnerabilities on an ongoing basis and ensure these applications are protected against known attacks by either of the following methods:
Reviewing public-facing web applications via manual or automated application vulnerability security assessment tools or methods, at least annually and after any changes Installing a web-application firewall in
Verify that public-facing web applications are reviewed (using either manual or automated vulnerability security assessment tools or methods), as follows: - At least annually - After any changes - By an organization that specializes in application security - That all vulnerabilities are corrected - That the application is re-evaluated after the corrections Verify that a web-application firewall is in place in front of public-facing web applications to detect and prevent web-based attacks. Note: An organization that specializes in application secuirty" can be either a third party company or an internal organization, as long as the reviewers specialize in application secuirty and can demonstrate independence from the development team.
front of public-facing web applications
12/18/2013

7.1 Limit access to system components and cardholder data to only those individuals whose job requires such access. Access limitations must include the following: 7.1.1 Restriction of access rights to privileged user IDs to least privileges necessary to perform job responsibilities 7.1.2 Assignment of privileges is based on individual personnels job classification and function 7.1 Obtain and examine written policy for data control, and verify that the policy incorporates the following:
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
7.1.1 Confirm that access rights for privileged user IDs are restricted to least privileges necessary to perform job responsibilities. 7.1.2 Confirm that privileges are assigned to individuals based on job classification and function (also called role-based access control or RBAC).
Unassigned
Unassigned
No
Unassigned
Unassigned
No
7.1.3 Requirement for a documented approval by authorized parties specifying required privileges.
7.1.3 Confirm that documented approval by authorized parties is required (in writing or electronically) for all access, and that it must specify required privileges. 7.1.4 Implementation of an automated access control 7.1.4 Confirm that access controls are implemented system via an automated access control system. 7.2 Establish an access control system for systems components with multiple users that restricts access based on a users need to know, and is set to deny all unless specifically allowed. This access control system must include the following: 7.2.1 Coverage of all system components 7.2 Examine system settings and vendor documentation to verify that an access control system is implemented as follows:
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
7.2.1 Confirm that access control systems are in place on all system components. 7.2.2 Assignment of privileges to individuals based on 7.2.2 Confirm that access control systems are job classification and function configured to enforce privileges assigned to individuals based on job classification and function. 7.2.3 Default deny-all setting Note: Some access control systems are set by default to allow-all, thereby permitting access unless/until a rule is written to specifically deny it. 7.2.3 Confirm that the access control systems have a default deny-all setting.
No No
Unassigned
Unassigned
No
12/18/2013

8.1 Assign all users a unique ID before allowing them 8.1 Verify that all users are assigned a unique ID for to access system components or cardholder data. access to system components or cardholder data. 8.2 In addition to assigning a unique ID, employ at least one of the following methods to authenticate all users: 8.2 To verify that users are authenticated using unique ID and additional authentication (for example, a password) for access to the cardholder data environment, perform the following: Obtain and examine documentation describing the authentication method(s) used. For each type of authentication method used and for each type of system component, observe an authentication to verify authentication is functioning consistent with documented authentication method(s). 8.3 To verify that two-factor authentication is implemented for all remote network access, observe an employee (for example, an administrator) connecting remotely to the network and verify that two of the three authentication methods are used.
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Something you know, such as a password or passphrase Something you have, such as a token device or smart card
Something you are, such as a biometric 8.3 Incorporate two-factor authentication for remote access (network-level access originating from outside the network) to the network by employees, administrators, and third parties. (For example, remote authentication and dial-in service (RADIUS) with tokens; terminal access controller access control system (TACACS) with tokens; or other technologies that facilitate two-factor authentication.)
Unassigned
Unassigned
No
Note: Two-factor authentication requires that two of the three authentication methods (see Requirement 8.2 for descriptions of authentication methods) be used for authentication. Using one factor twice (for example, using two separate passwords) is not considered two-factor authentication. 8.4 Render all passwords unreadable during transmission and storage on all system components using strong cryptography. 8.4.a For a sample of system components, examine password files to verify that passwords are unreadable during transmission and storage. 8.4.b For service providers only, observe password files to verify that customer passwords are encrypted. 8.5 Ensure proper user identification and authentication management for non-consumer users and administrators on all system components as follows: 8.5.1 Control addition, deletion, and modification of user IDs, credentials, and other identifier objects. 8.5 Review procedures and interview personnel to verify that procedures are implemented for user identification and authentication management, by performing the following: 8.5.1 Select a sample of user IDs, including both administrators and general users. Verify that each user is authorized to use the system according to policy by performing the following: Obtain and examine an authorization form for each ID. Verify that the sampled user IDs are implemented in accordance with the authorization form (including with privileges as specified and all signatures obtained), by tracing information from the authorization form to the system. 8.5.2 Examine password/authentication procedures and observe security personnel to verify that, if a user requests a password reset by phone, e-mail, web, or other non-face-to-face method, the users identity is verified before the password is reset. 8.5.3 Examine password procedures and observe security personnel to verify that first-time passwords for new users, and reset passwords for existing users, are set to a unique value for each user and changed after first use. 8.5.4 Select a sample of users terminated in the past six months, and review current user access lists to verify that their IDs have been deactivated or removed. 8.5.5 Verify that inactive accounts over 90 days old are either removed or disabled. 8.5.6.a Verify that any accounts used by vendors to access, support and maintain system components are disabled, and enabled only when needed by the vendor. 8.5.6.b Verify that vendor remote access accounts are monitored while being used. 8.5.7 Interview the users from a sample of user IDs, to verify that they are familiar with authentication procedures and policies. 8.5.8.a For a sample of system components, examine user ID lists to verify the following: Generic user IDs and accounts are disabled or removed Shared user IDs for system administration activities and other critical functions do not exist Shared and generic user IDs are not used to administer any system components 8.5.8.b Examine authentication policies/procedures to verify that group and shared passwords or other authentication methods are explicitly prohibited. 8.5.8.c Interview system administrators to verify that group and shared passwords or other authentication methods are not distributed, even if requested. 8.5.9 Change user passwords at least every 90 days. 8.5.9.a For a sample of system components, obtain and inspect system configuration settings to verify that user password parameters are set to require users to change passwords at least every 90 days.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
8.5.2 Verify user identity before performing password resets.
Unassigned
Unassigned
No
8.5.3 Set passwords for first-time use and resets to a unique value for each user and change immediately after the first use.
Unassigned
Unassigned
No
8.5.4 Immediately revoke access for any terminated users.
Unassigned
Unassigned
No
8.5.5 Remove/disable inactive user accounts at least every 90 days. 8.5.6 Enable accounts used by vendors for remote access only during the time period needed. Monitor vendor remote access accounts when in use.
No No
No No
8.5.7 Communicate authentication procedures and policies to all users who have access to cardholder data. 8.5.8 Do not use group, shared, or generic accounts and passwords, or other authentication methods.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013
8.5.9 Change user passwords at least every 90 days.

8.5.9.b For service providers only, review internal processes and customer/user documentation to verify that non-consumer user passwords are required to change periodically and that non-consumer users are given guidance as to when, and under what circumstances, passwords must change.
PCI DSS Requirment
Owner
Unassigned
Area
Unassigned
No
Notes / Questions
8.5.10 Require a minimum password length of at least 8.5.10.a For a sample of system components, obtain seven characters. and inspect system configuration settings to verify that password parameters are set to require passwords to be at least seven characters long. 8.5.10.b For service providers only, review internal processes and customer/user documentation to verify that that non-consumer user passwords are required to meet minimum length requirements. 8.5.11 Use passwords containing both numeric and alphabetic characters. 8.5.11.a For a sample of system components, obtain and inspect system configuration settings to verify that password parameters are set to require passwords to contain both numeric and alphabetic characters. 8.5.11.b For service providers only, review internal processes and customer/user documentation to verify that non-consumer user passwords are required to contain both numeric and alphabetic characters. 8.5.12 Do not allow an individual to submit a new password that is the same as any of the last four passwords he or she has used. 8.5.12.a For a sample of system components, obtain and inspect system configuration settings to verify that password parameters are set to require that new passwords cannot be the same as the four previously used passwords. 8.5.12.b For service providers only, review internal processes and customer/user documentation to verify that new non-consumer user passwords cannot be the same as the previous four passwords. 8.5.13.a For a sample of system components, obtain and inspect system configuration settings to verify that authentication parameters are set to require that a users account be locked out after not more than six invalid logon attempts. 8.5.13.b For service providers only, review internal processes and customer/user documentation to verify that non-consumer user accounts are temporarily locked-out after not more than six invalid access attempts. 8.5.14 For a sample of system components, obtain and inspect system configuration settings to verify that password parameters are set to require that once a user account is locked out, it remains locked for a minimum of 30 minutes or until a system administrator resets the account. 8.5.15 For a sample of system components, obtain and inspect system configuration settings to verify that system/session idle time out features have been set to 15 minutes or less. 8.5.16.a Review database and application configuration settings and verify that all users are authenticated prior to access.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
8.5.13 Limit repeated access attempts by locking out the user ID after not more than six attempts.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
8.5.14 Set the lockout duration to a minimum of 30 minutes or until administrator enables the user ID.
Unassigned
Unassigned
No
8.5.15 If a session has been idle for more than 15 minutes, require the user to re-authenticate to reactivate the terminal or session.
Unassigned
Unassigned
No
8.5.16 Authenticate all access to any database containing cardholder data. This includes access by applications, administrators, and all other users.
Unassigned
Unassigned
No
Restrict user direct access or queries to databases to 8.5.16.b Verify that database and application database administrators. configuration settings ensure that all user access to, user queries of, and user actions on (for example, move, copy, delete), the database are through programmatic methods only (for example, through stored procedures). 8.5.16.c Verify that database and application configuration settings restrict user direct access or queries to databases to database administrators. 8.5.16.d Review database applications and the related application IDs to verify that application IDs can only be used by the applications (and not by individual users or other processes).
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013

9.1 Use appropriate facility entry controls to limit and monitor physical access to systems in the cardholder data environment. 9.1 Verify the existence of physical security controls for each computer room, data center, and other physical areas with systems in the cardholder data environment. Verify that access is controlled with badge readers or other devices including authorized badges and lock and key. Observe a system administrators attempt to log into consoles for randomly selected systems in the cardholder environment and verify that they are locked to prevent unauthorized use. 9.1.1.a Verify that video cameras and/or access control mechanisms are in place to monitor the entry/exit points to sensitive areas.
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
9.1.1 Use video cameras and/or access control mechanisms to monitor individual physical access to sensitive areas. Review collected data and correlate with other entries. Store for at least three months, unless otherwise restricted by law.
Unassigned
Unassigned
No
Note: Sensitive areas refers to any data center, 9.1.1.b Verify that video cameras and/or access server room or any area that houses systems that control mechanisms are protected from tampering or store, process, or transmit cardholder data. This disabling. excludes the areas where only point-of-sale terminals are present, such as the cashier areas in a retail store. 9.1.1.c Verify that video cameras and/or access control mechanisms are monitored and that data from cameras or other mechanisms is stored for at least three months. 9.1.2 Restrict physical access to publicly accessible 9.1.2 Verify by interviewing network administrators and network jacks. by observation that network jacks are enabled only when needed by authorized onsite personnel. For example, areas accessible to visitors should not have network ports enabled unless network access is Alternatively, verify that visitors are escorted at all times in areas with active network jacks. explicitly authorized. 9.1.3 Restrict physical access to wireless access points, gateways, handheld devices, networking/communications hardware, and telecommunication lines. 9.1.3 Verify that physical access to wireless access points, gateways, handheld devices, networking/communications hardware, and telecommunication lines is appropriately restricted.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
9.2 Develop procedures to easily distinguish between 9.2.a Review processes and procedures for assigning onsite personnel and visitors, especially in areas badges to onsite personnel and visitors, and verify where cardholder data is accessible. these processes include the following: Granting new badges, Changing access requirements, and Revoking terminated onsite personnel and expired visitor badges 9.2.b Verify that access to the badge system is limited to authorized personnel. 9.2.c Examine badges in use to verify that they clearly identify visitors and it is easy to distinguish between onsite personnel and visitors. 9.3 Make sure all visitors are handled as follows: 9.3.1 Authorized before entering areas where cardholder data is processed or maintained. 9.3 Verify that visitor controls are in place as follows: 9.3.1 Observe the use of visitor ID badges to verify that a visitor ID badge does not permit unescorted access to physical areas that store cardholder data.
Unassigned
Unassigned
No
No No
No No
9.3.2 Given a physical token (for example, a badge or 9.3.2.a Observe people within the facility to verify the access device) that expires and that identifies the use of visitor ID badges, and that visitors are easily visitors as not onsite personnel. distinguishable from onsite personnel. 9.3.2.b Verify that visitor badges expire. 9.3.3 Asked to surrender the physical token before 9.3.3 Observe visitors leaving the facility to verify leaving the facility or at the date of expiration. visitors are asked to surrender their ID badge upon departure or expiration. 9.4 Use a visitor log to maintain a physical audit trail of 9.4.a Verify that a visitor log is in use to record visitor activity. Document the visitors name, the firm physical access to the facility as well as for computer represented, and the onsite personnel authorizing rooms and data centers where cardholder data is physical access on the log. Retain this log for a stored or transmitted. minimum of three months, unless otherwise restricted 9.4.b Verify that the log contains the visitors name, by law. the firm represented, and the onsite personnel authorizing physical access, and is retained for at least three months. 9.5 Store media back-ups in a secure location, 9.5.a Observe the storage locations physical security preferably an off-site facility, such as an alternate or to confirm that backup media storage is secure. back-up site, or a commercial storage facility. Review the locations security at least annually. 9.5.b Verify that the storage location security is reviewed at least annually. 9.6 Physically secure all media. 9.6 Verify that procedures for protecting cardholder data include controls for physically securing all media (including but not limited to computers, removable electronic media, paper receipts, paper reports, and faxes). 9.7 Maintain strict control over the internal or external 9.7 Verify that a policy exists to control distribution of distribution of any kind of media, including the media, and that the policy covers all distributed media following: including that distributed to individuals. 9.7.1 Classify media so the sensitivity of the data can be determined. 9.7.2 Send the media by secured courier or other delivery method that can be accurately tracked. 9.7.1 Verify that all media is classified so the sensitivity of the data can be determined. 9.7.2 Verify that all media sent outside the facility is logged and authorized by management and sent via secured courier or other delivery method that can be tracked. 9.8 Ensure management approves any and all media 9.8 Select a recent sample of several days of offsite that is moved from a secured area (especially when tracking logs for all media, and verify the presence in media is distributed to individuals). the logs of tracking details and proper management authorization. 9.9 Maintain strict control over the storage and 9.9 Obtain and examine the policy for controlling accessibility of media. storage and maintenance of all media and verify that the policy requires periodic media inventories. 9.9.1 Properly maintain inventory logs of all media and conduct media inventories at least annually. 9.9.1 Obtain and review the media inventory log to verify that periodic media inventories are performed at least annually.
Unassigned
Unassigned
No
No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
No No
Unassigned
Unassigned
No
No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013

PCI DSS Requirment
9.10 Destroy media when it is no longer needed for business or legal reasons as follows: 9.10.1 Shred, incinerate, or pulp hardcopy materials so that cardholder data cannot be reconstructed.

9.10 Obtain and examine the periodic media destruction policy and verify that it covers all media, and confirm the following: 9.10.1.a Verify that hard-copy materials are crosscut shredded, incinerated, or pulped such that there is reasonable assurance the hard-copy materials cannot be reconstructed. 9.10.1.b Examine storage containers used for information to be destroyed to verify that the containers are secured. For example, verify that a tobe-shredded container has a lock preventing access to its contents. 9.10.2 Verify that cardholder data on electronic media is rendered unrecoverable via a secure wipe program in accordance with industry-accepted standards for secure deletion, or otherwise physically destroying the media (for example, degaussing).
Owner
Unassigned
Area
Unassigned
No
Notes / Questions
Unassigned
Unassigned
No
Unassigned
Unassigned
No
9.10.2 Render cardholder data on electronic media unrecoverable so that cardholder data cannot be reconstructed.
Unassigned
Unassigned
No
12/18/2013

10.1 Establish a process for linking all access to system components (especially access done with administrative privileges such as root) to each individual user. 10.2 Implement automated audit trails for all system components to reconstruct the following events: 10.2.1 All individual accesses to cardholder data 10.2.2 All actions taken by any individual with root or administrative privileges 10.2.3 Access to all audit trails 10.2.4 Invalid logical access attempts 10.2 5 Use of identification and authentication mechanisms 10.2.6 Initialization of the audit logs 10.2.7 Creation and deletion of system-level objects 10.1 Verify through observation and interviewing the system administrator, that audit trails are enabled and active for system components. 10.2 Through interviews, examination of audit logs, and examination of audit log settings, perform the following: 10.2.1 Verify all individual access to cardholder data is logged. 10.2.2 Verify actions taken by any individual with root or administrative privileges are logged. 10.2.3 Verify access to all audit trails is logged. 10.2.4 Verify invalid logical access attempts are logged. 10.2.5 Verify use of identification and authentication mechanisms is logged. 10.2.6 Verify initialization of audit logs is logged.
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned Unassigned Unassigned Unassigned Unassigned Unassigned Unassigned Unassigned
Unassigned Unassigned Unassigned Unassigned Unassigned Unassigned Unassigned Unassigned
No No No No No No No No
10.2.7 Verify creation and deletion of system level objects are logged. 10.3 Record at least the following audit trail entries for 10.3 Through interviews and observation, for each all system components for each event: auditable event (from 10.2), perform the following: 10.3.1 User identification 10.3.2 Type of event 10.3.3 Date and time 10.3.4 Success or failure indication 10.3.5 Origination of event 10.3.6 Identity or name of affected data, system component, or resource. 10.4 Using time-synchronization technology, synchronize all critical system clocks and times and ensure that the following is implemented for acquiring, distributing, and storing time. Note: One example of time synchronization technology is Network Time Protocol (NTP). 10.3.1 Verify user identification is included in log entries. 10.3.2 Verify type of event is included in log entries. 10.3.3 Verify date and time stamp is included in log entries. 10.3.4 Verify success or failure indication is included in log entries. 10.3.5 Verify origination of event is included in log entries. 10.3.6 Verify identity or name of affected data, system component, or resources is included in log entries. 10.4.a Verify that time-synchronization technology is implemented and kept current per PCI DSS Requirements 6.1 and 6.2. 10.4.b Obtain and review the process for acquiring, distributing and storing the correct time within the organization, and review the time-related systemparameter settings for a sample of system components. Verify the following is included in the process and implemented: 10.4.1.a Verify that only designated central time servers receive time signals from external sources, and time signals from external sources are based on International Atomic Time or UTC. 10.4.1.b Verify that the designated central time servers peer with each other to keep accurate time, and other internal servers receive time only from the central time servers. 10.4.2.a Review system configurations and timesynchronization settings to verify that access to time data is restricted to only personnel with a business need to access time data. 10.4.2.b Review system configurations and time synchronization settings and processes to verify that any changes to time settings on critical systems are logged, monitored, and reviewed. 10.4.3 Verify that the time servers accept time updates from specific, industry-accepted external sources (to prevent a malicious individual from changing the clock). Optionally, those updates can be encrypted with a symmetric key, and access control lists can be created that specify the IP addresses of client machines that will be provided with the time updates (to prevent unauthorized use of internal time servers).
Unassigned Unassigned Unassigned Unassigned Unassigned Unassigned
Unassigned Unassigned Unassigned Unassigned Unassigned Unassigned
No No No No No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
10.4.1 Critical systems have the correct and consistent time.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
10.4.2 Time data is protected.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
10.4.3 Time settings are received from industryaccepted time sources.
Unassigned
Unassigned
No
10.5 Secure audit trails so they cannot be altered.
10.5 Interview system administrator and examine permissions to verify that audit trails are secured so that they cannot be altered as follows:
Unassigned
Unassigned
No
10.5.1 Limit viewing of audit trails to those with a jobrelated need. 10.5.2 Protect audit trail files from unauthorized modifications.
10.5.1 Verify that only individuals who have a jobrelated need can view audit trail files. 10.5.2 Verify that current audit trail files are protected from unauthorized modifications via access control mechanisms, physical segregation, and/or network segregation. 10.5.3 Promptly back up audit trail files to a 10.5.3 Verify that current audit trail files are promptly centralized log server or media that is difficult to alter. backed up to a centralized log server or media that is difficult to alter. 10.5.4 Write logs for external-facing technologies onto 10.5.4 Verify that logs for external-facing technologies a log server on the internal LAN. (for example, wireless, firewalls, DNS, mail) are offloaded or copied onto a secure centralized internal log server or media. 10.5.5 Use file-integrity monitoring or change10.5.5 Verify the use of file-integrity monitoring or detection software on logs to ensure that existing log change-detection software for logs by examining data cannot be changed without generating alerts system settings and monitored files and results from (although new data being added should not cause an monitoring activities. alert). 10.6 Review logs for all system components at least 10.6.a Obtain and examine security policies and daily. Log reviews must include those servers that procedures to verify that they include procedures to perform security functions like intrusion-detection review security logs at least daily and that follow-up to system (IDS) and authentication, authorization, and exceptions is required. accounting protocol (AAA) servers (for example, RADIUS). Note: Log harvesting, parsing, and alerting tools may 10.6.b Through observation and interviews, verify that be used to meet compliance with Requirement 10.6 . regular log reviews are performed for all system components.
No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12/18/2013

PCI DSS Requirment
10.7 Retain audit trail history for at least one year, with a minimum of three months immediately available for analysis (for example, online, archived, or restorable from back-up).

10.7.a Obtain and examine security policies and procedures and verify that they include audit log retention policies and require audit log retention for at least one year. 10.7.b Verify that audit logs are available for at least one year and processes are in place to immediately restore at least the last three months logs for analysis.
Owner
Unassigned
Area
Unassigned
No
Notes / Questions
Unassigned
Unassigned
No
12/18/2013

11.1 Test for the presence of wireless access points and detect unauthorized wireless access points on a quarterly basis. Note: Methods that may be used in the process include but are not limited to wireless network scans, physical/logical inspections of system components and infrastructure, network access control (NAC), or wireless IDS/IPS. Whichever methods are used, they must be sufficient to detect and identify any unauthorized devices. 11.1.a Verify that the entity has a documented process to detect and identify wireless access points on a quarterly basis. 11.1.b Verify that the methodology is adequate to detect and identify any unauthorized wireless access points, including at least the following:
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
Unassigned
Unassigned
No
WLAN cards inserted into system components
Portable wireless devices connected to system components (for example, by USB, etc.) Wireless devices attached to a network port or network device 11.1.c Verify that the documented process to identify unauthorized wireless access points is performed at least quarterly for all system components and facilities. 11.1.d If automated monitoring is utilized (for example, wireless IDS/IPS, NAC, etc.), verify the configuration will generate alerts to personnel. 11.1.e Verify the organizations incident response plan (Requirement 12.9) includes a response in the event unauthorized wireless devices are detected. 11.2 Run internal and external network vulnerability 11.2 Verify that internal and external vulnerability scans are performed as follows: scans at least quarterly and after any significant change in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades). Note: It is not required that four passing quarterly scans must be completed for initial PCI DSS compliance if the assessor verifies 1) the most recent scan result was a passing scan, 2) the entity has documented policies and procedures requiring quarterly scanning, and 3) vulnerabilities noted in the scan results have been corrected as shown in a rescan. For subsequent years after the initial PCI DSS review, four passing quarterly scans must have occurred. 11.2.1 Perform quarterly internal vulnerability scans. 11.2.1.a Review the scan reports and verify that four quarterly internal scans occurred in the most recent 12-month period. 11.2.1.b Review the scan reports and verify that the scan process includes rescans until passing results are obtained, or all High vulnerabilities as defined in PCI DSS Requirement 6.2 are resolved. 11.2.1.c Validate that the scan was performed by a qualified internal resource(s) or qualified external third party, and if applicable, organizational independence of the tester exists (not required to be a QSA or ASV). 11.2.2 Perform quarterly external vulnerability scans via an Approved Scanning Vendor (ASV), approved by the Payment Card Industry Security Standards Council (PCI SSC). Note: Quarterly external vulnerability scans must be performed by an Approved Scanning Vendor (ASV), approved by the Payment Card Industry Security Standards Council (PCI SSC). Scans conducted after network changes may be performed by internal staff. 11.2.2.a Review output from the four most recent quarters of external vulnerability scans and verify that four quarterly scans occurred in the most recent 12month period. 11.2.2.b Review the results of each quarterly scan to ensure that they satisfy the ASV Program Guide requirements (for example, no vulnerabilities rated higher than a 4.0 by the CVSS and no automatic failures). 11.2.2.c Review the scan reports to verify that the scans were completed by an Approved Scanning Vendor (ASV), approved by the PCI SSC. 11.2.3 Perform internal and external scans after any significant change. 11.2.3.a Inspect change control documentation and scan reports to verify that system components subject to any significant change were scanned. 11.2.3.b Review scan reports and verify that the scan process includes rescans until: For external scans, no vulnerabilities exist that are scored greater than a 4.0 by the CVSS, For internal scans, a passing result is obtained or all High vulnerabilities as defined in PCI DSS Requirement 6.2 are resolved. 11.2.3.c Validate that the scan was performed by a qualified internal resource(s) or qualified external third party, and if applicable, organizational independence of the tester exists (not required to be a QSA or ASV). 11.3.a Obtain and examine the results from the most recent penetration test to verify that penetration testing is performed at least annually and after any significant changes to the environment. 11.3.b Verify that noted exploitable vulnerabilities were corrected and testing repeated. 11.3.c Verify that the test was performed by a qualified internal resource or qualified external third party, and if applicable, organizational independence of the tester exists (not required to be a QSA or ASV). 11.3.1 Verify that the penetration test includes networklayer penetration tests. These tests should include components that support network functions as well as operating systems.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Note: Scans conducted after changes may be performed by internal staff.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
11.3 Perform external and internal penetration testing at least once a year and after any significant infrastructure or application upgrade or modification (such as an operating system upgrade, a sub-network added to the environment, or a web server added to the environment). These penetration tests must include the following:
Unassigned
Unassigned
No
No No
11.3.1 Network-layer penetration tests
Unassigned
Unassigned
No
12/18/2013

PCI DSS Requirment
11.3.2 Application-layer penetration tests
Owner
Unassigned
Area
Unassigned
No
Notes / Questions
11.3.2 Verify that the penetration test includes application-layer penetration tests. The tests should include, at a minimum, the vulnerabilities listed in Requirement 6.5. 11.4 Use intrusion-detection systems, and/or intrusion- 11.4.a Verify the use of intrusion-detection systems prevention systems to monitor all traffic at the and/or intrusion-prevention systems and that all traffic perimeter of the cardholder data environment as well at the perimeter of the cardholder data environment as at critical points inside of the cardholder data as well as at critical points in the cardholder data environment, and alert personnel to suspected environment is monitored. compromises. Keep all intrusion-detection and prevention engines, baselines, and signatures up-to-date. 11.4.b Confirm IDS and/or IPS are configured to alert personnel of suspected compromises. 11.4.c Examine IDS/IPS configurations and confirm IDS/IPS devices are configured, maintained, and updated per vendor instructions to ensure optimal protection. 11.5.a Verify the use of file-integrity monitoring tools within the cardholder data environment by observing system settings and monitored files, as well as reviewing results from monitoring activities.
Unassigned
Unassigned
No
No No
11.5 Deploy file-integrity monitoring tools to alert personnel to unauthorized modification of critical system files, configuration files, or content files; and configure the software to perform critical file comparisons at least weekly. Note: For file-integrity monitoring purposes, critical Examples of files that should be monitored: files are usually those that do not regularly change, but the modification of which could indicate a system compromise or risk of compromise. File-integrity monitoring products usually come pre-configured with critical files for the related operating system. Other critical files, such as those for custom applications, must be evaluated and defined by the entity (that is, the merchant or service provider). System executables Application executables Configuration and parameter files
Unassigned
Unassigned
No
Centrally stored, historical or archived, log and audit files 11.5.b Verify the tools are configured to alert personnel to unauthorized modification of critical files, and to perform critical file comparisons at least weekly.
Unassigned
Unassigned
No
12/18/2013

12.1 Establish, publish, maintain, and disseminate a security policy that accomplishes the following: 12.1 Examine the information security policy and verify that the policy is published and disseminated to all relevant personnel (including vendors and business partners). 12.1.1 Addresses all PCI DSS requirements. 12.1.1 Verify that the policy addresses all PCI DSS requirements. 12.1.2 Includes an annual process that identifies 12.1.2.a Verify that an annual risk assessment threats, and vulnerabilities, and results in a formal risk process is documented that identifies threats, assessment. vulnerabilities, and results in a formal risk assessment. (Examples of risk assessment methodologies include 12.1.2.b Review risk assessment documentation to but are not limited to OCTAVE, ISO 27005 and NIST verify that the risk assessment process is performed at SP 800-30.) least annually. 12.1.3 Includes a review at least annually and 12.1.3 Verify that the information security policy is updates when the environment changes. reviewed at least annually and updated as needed to reflect changes to business objectives or the risk environment. 12.2 Develop daily operational security procedures 12.2 Examine the daily operational security that are consistent with requirements in this procedures. Verify that they are consistent with this specification (for example, user account maintenance specification, and include administrative and technical procedures, and log review procedures). procedures for each of the requirements. 12.3 Develop usage policies for critical technologies 12.3 Obtain and examine the usage policies for critical (for example, remote-access technologies, wireless technologies and perform the following: technologies, removable electronic media, laptops, tablets, personal data/digital assistants (PDAs), e-mail usage and Internet usage) and define proper use of these technologies. Ensure these usage policies require the following: 12.3.1 Explicit approval by authorized parties 12.3.1 Verify that the usage policies require explicit approval from authorized parties to use the technologies. 12.3.2 Verify that the usage policies require that all technology use be authenticated with user ID and password or other authentication item (for example, token). 12.3.3 Verify that the usage policies require a list of all devices and personnel authorized to use the devices. 12.3.4 Verify that the usage policies require labeling of devices with information that can be correlated to owner, contact information and purpose.
Owner
Area
Notes / Questions
Unassigned
Unassigned
No
No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12.3.2 Authentication for use of the technology
Unassigned
Unassigned
No
12.3.3 A list of all such devices and personnel with access 12.3.4 Labeling of devices to determine owner, contact information and purpose
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12.3.5 Acceptable uses of the technology
12.3.5 Verify that the usage policies require acceptable uses for the technology. 12.3.6 Acceptable network locations for the 12.3.6 Verify that the usage policies require technologies acceptable network locations for the technology. 12.3.7 List of company-approved products 12.3.7 Verify that the usage policies require a list of company-approved products. 12.3.8 Automatic disconnect of sessions for remote- 12.3.8 Verify that the usage policies require automatic access technologies after a specific period of inactivity disconnect of sessions for remote-access technologies after a specific period of inactivity. 12.3.9 Activation of remote-access technologies for vendors and business partners only when needed by vendors and business partners, with immediate deactivation after use 12.3.9 Verify that the usage policies require activation of remote-access technologies used by vendors and business partners only when needed by vendors and business partners, with immediate deactivation after use. 12.3.10 For personnel accessing cardholder data via 12.3.10.a Verify that the usage policies prohibit remote-access technologies, prohibit copy, move, and copying, moving, or storing of cardholder data onto storage of cardholder data onto local hard drives and local hard drives and removable electronic media removable electronic media, unless explicitly when accessing such data via remote-access authorized for a defined business need. technologies. 12.3.10.b For personnel with proper authorization, verify that usage policies require the protection of cardholder data in accordance with PCI DSS Requirements. 12.4 Ensure that the security policy and procedures 12.4 Verify that information security policies clearly clearly define information security responsibilities for define information security responsibilities for all all personnel. personnel. 12.5 Assign to an individual or team the following 12.5 Verify the formal assignment of information information security management responsibilities: security to a Chief Security Officer or other securityknowledgeable member of management. Obtain and examine information security policies and procedures to verify that the following information security responsibilities are specifically and formally assigned: 12.5.1 Establish, document, and distribute security policies and procedures. 12.5.2 Monitor and analyze security alerts and information, and distribute to appropriate personnel. 12.5.1 Verify that responsibility for creating and distributing security policies and procedures is formally assigned. 12.5.2 Verify that responsibility for monitoring and analyzing security alerts and distributing information to appropriate information security and business unit management personnel is formally assigned. 12.5.3 Verify that responsibility for creating and distributing security incident response and escalation procedures is formally assigned. 12.5.4 Verify that responsibility for administering user account and authentication management is formally assigned. 12.5.5 Verify that responsibility for monitoring and controlling all access to data is formally assigned.
Unassigned Unassigned Unassigned Unassigned
Unassigned Unassigned Unassigned Unassigned
No No No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12.5.3 Establish, document, and distribute security incident response and escalation procedures to ensure timely and effective handling of all situations. 12.5.4 Administer user accounts, including additions, deletions, and modifications 12.5.5 Monitor and control all access to data.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12.6 Implement a formal security awareness program 12.6.a Verify the existence of a formal security to make all personnel aware of the importance of awareness program for all personnel. cardholder data security. 12.6.b Obtain and examine security awareness program procedures and documentation and perform the following:
No No
12/18/2013

PCI DSS Requirment
12.6.1 Educate personnel upon hire and at least annually.

12.6.1.a Verify that the security awareness program provides multiple methods of communicating awareness and educating personnel (for example, posters, letters, memos, web based training, meetings, and promotions). 12.6.1.b Verify that personnel attend awareness training upon hire and at least annually. 12.6.2 Verify that the security awareness program requires personnel to acknowledge, in writing or electronically, at least annually that they have read and understand the information security policy. 12.7 Inquire with Human Resource department management and verify that background checks are conducted (within the constraints of local laws) on potential personnel prior to hire who will have access to cardholder data or the cardholder data environment.
Owner
Unassigned
Area
Unassigned
No
Notes / Questions
Note: Methods can vary depending on the role of the personnel and their level of access to the cardholder data. 12.6.2 Require personnel to acknowledge at least annually that they have read and understood the security policy and procedures.
Unassigned
Unassigned
No
Unassigned
Unassigned
No
12.7 Screen potential personnel prior to hire to minimize the risk of attacks from internal sources. (Examples of background checks include previous employment history, criminal record, credit history, and reference checks.) Note: For those potential personnel to be hired for certain positions such as store cashiers who only have access to one card number at a time when facilitating a transaction, this requirement is a recommendation only. 12.8 If cardholder data is shared with service providers, maintain and implement policies and procedures to manage service providers, to include the following:
Unassigned
Unassigned
No
12.8 If the entity shares cardholder data with service providers (for example, back-up tape storage facilities, managed service providers such as Web hosting companies or security service providers, or those that receive data for fraud modeling purposes), through observation, review of policies and procedures, and review of supporting documentation, perform the following: 12.8.1 Verify that a list of service providers is maintained. 12.8.2 Verify that the written agreement includes an acknowledgement by the service providers of their responsibility for securing cardholder data. 12.8.3 Verify that policies and procedures are documented and were followed including proper due diligence prior to engaging any service provider. 12.8.4 Verify that the entity maintains a program to monitor its service providers PCI DSS compliance status at least annually. 12.9 Obtain and examine the Incident Response Plan and related procedures and perform the following: 12.9.1.a Verify that the incident response plan includes:
Unassigned
Unassigned
No
12.8.1 Maintain a list of service providers. 12.8.2 Maintain a written agreement that includes an acknowledgement that the service providers are responsible for the security of cardholder data the service providers possess. 12.8.3 Ensure there is an established process for engaging service providers including proper due diligence prior to engagement. 12.8.4 Maintain a program to monitor service providers PCI DSS compliance status at least annually. 12.9 Implement an incident response plan. Be prepared to respond immediately to a system breach. 12.9.1 Create the incident response plan to be implemented in the event of system breach. Ensure the plan addresses the following, at a minimum: Roles, responsibilities, and communication and contact strategies in the event of a compromise including notification of the payment brands, at a minimum Specific incident response procedures Business recovery and continuity procedures Data back-up processes Analysis of legal requirements for reporting compromises
No No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Unassigned
Unassigned
No
Roles, responsibilities, and communication strategies in the event of a compromise including notification of the payment brands, at a minimum: Specific incident response procedures Business recovery and continuity procedures Data back-up processes Analysis of legal requirements for reporting compromises (for example, California Bill 1386 which requires notification of affected consumers in the event of an actual or suspected compromise for any business with California residents in their database) Coverage and responses for all critical system components Reference or inclusion of incident response procedures from the payment brands 12.9.1.b Review documentation from a previously reported incident or alert to verify that the documented incident response plan and procedures were followed. 12.9.2 Verify that the plan is tested at least annually.
Coverage and responses of all critical system components Reference or inclusion of incident response procedures from the payment brands
Unassigned
Unassigned
No
12.9.2 Test the plan at least annually.
No No
12.9.3 Designate specific personnel to be available on 12.9.3 Verify through observation and review of a 24/7 basis to respond to alerts. policies, that designated personnel are available for 24/7 incident response and monitoring coverage for any evidence of unauthorized activity, detection of unauthorized wireless access points, critical IDS alerts, and/or reports of unauthorized critical system or content file changes. 12.9.4 Provide appropriate training to staff with security breach response responsibilities. 12.9.4 Verify through observation and review of policies that staff with responsibilities for security breach response are periodically trained. 12.9.5 Verify through observation and review of processes that monitoring and responding to alerts from security systems including detection of unauthorized wireless access points are covered in the Incident Response Plan. 12.9.6 Verify through observation and review of policies that there is a process to modify and evolve the incident response plan according to lessons learned and to incorporate industry developments.
Unassigned
Unassigned
No
12.9.5 Include alerts from intrusion-detection, intrusion-prevention, and file-integrity monitoring systems.
Unassigned
Unassigned
No
12.9.6 Develop a process to modify and evolve the incident response plan according to lessons learned and to incorporate industry developments.
Unassigned
Unassigned
No
12/18/2013
Responses on SAQ D Template

Requirement Req. 1 Req. 2 Req. 3 Req. 4 Req. 5 Req. 6 Req. 7 Req. 8 Req. 9 Req. 10 Req. 11 Req. 12 Subtotal Total 28 26 37 9 7 36 9 33 29 33 25 44 316 N/A 0 0 0 0 0 0 0 0 0 0 0 0 0 0% SubTotal 28 26 37 9 7 36 9 33 29 33 25 44 316 100% Yes 0 0 0 0 0 0 0 0 0 0 0 0 0 0% No 28 26 37 9 7 36 9 33 29 33 25 44 316 100% Complete 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0% 0%
45 40 35 30 25 20 15 10 5 0 N/A No Yes
Req. 1 0 28 0
Req. 2 0 26 0
Req. 3 0 37 0
Req. 4 0 9 0
Req. 5 0 7 0
Req. 6 0 36 0
Req. 7 0 9 0
Req. 8 0 33 0
Req. 9
N/A No Yes
Req. 9 0 29 0
Req. 10 0 33 0
Req. 11 0 25 0
Req. 12 0 44 0
Name>>
Responses Yes Yes - Comp. Ctrl. No N/A
Owners Corp. Prop. Corp. & Prop. Unassigned
Corporate Property Both Corporate and Property
Areas IT Finance & Ops Legal HR IT / Finance & Ops Facilities Mgmt. Unassigned

PCI DSS Self Assessment Questionnaire (SAQ) Form D

Uploaded by

Copyright:

Available Formats

PCI DSS Self Assessment Questionnaire (SAQ) Form D

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PCI DSS Self Assessment Questionnaire (SAQ) Form D

Uploaded by

Copyright:

Available Formats

PCI DSS Self Assessment Questionnaire (SAQ) Form D

PCI DSS Requirment Requirement Section 1

Testing Procedure or Question