Fill - Free fillable PCI-DSS-v3 2-SAQ-D Merchant-rev1 1 PDF form

Payment Card Industry (PCI)

Data Security Standard

Self-Assessment Questionnaire D

and Attestation of Compliance for

Merchants

All other SAQ-Eligible Merchants

For use with PCI DSS Version 3.2

Revision 1.1

January 2017

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 January 2017

Document Changes

Date

PCI DSS

Version

SAQ

Revision

Description

October

2008

1.2

To align content with new PCI DSS v1.2 and to implement

minor changes noted since original v1.1.

October

2010

2.0

To align content with new PCI DSS v2.0 requirements and

testing procedures.

February

2014

3.0

To align content with PCI DSS v3.0 requirements and testing

procedures and incorporate additional response options.

April 2015

3.1

Updated to align with PCI DSS v3.1. For details of PCI DSS

changes, see PCI DSS – Summary of Changes from PCI DSS

Version 3.0 to 3.1.

July 2015

3.1

1.1

Updated to remove references to “best practices” prior to June

30, 2015, and remove the PCI DSS v2 reporting option for

Requirement 11.3.

April 2016

3.2

1.0

Updated to align with PCI DSS v3.2. For details of PCI DSS

changes, see PCI DSS – Summary of Changes from PCI DSS

Version 3.1 to 3.2.

January 2017

3.2

1.1

Updated version numbering to align with other SAQs

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 January 2017

Table of Contents

Document Changes .................................................................................................................. i

Before You Begin .....................................................................................................................iii

PCI DSS Self-Assessment Completion Steps ...................................................................................... iii

Understanding the Self-Assessment Questionnaire ........................................................................... iii

Expected Testing ................................................................................................................................... iv

Completing the Self-Assessment Questionnaire ................................................................................. iv

Guidance for Non-Applicability of Certain, Specific Requirements .................................................... v

Understanding the difference between Not Applicable and Not Tested .................................................. v

Legal Exception .................................................................................................................................... v

Section 1: Assessment Information ..................................................................................... 1

Section 2: Self-Assessment Questionnaire D for Merchants ............................................. 4

Build and Maintain a Secure Network and Systems ............................................................................. 4

Requirement 1: Install and maintain a firewall configuration to protect data ........................................ 4

Requirement 2: Do not use vendor-supplied defaults for system passwords and other security

parameters .................................................................................................................. 9

Protect Cardholder Data ........................................................................................................................ 14

Requirement 3: Protect stored cardholder data .................................................................................. 14

Requirement 4: Encrypt transmission of cardholder data across open, public networks ................... 22

Maintain a Vulnerability Management Program .................................................................................. 24

Requirement 5: Protect all systems against malware and regularly update anti-virus software or

programs ................................................................................................................... 24

Requirement 6: Develop and maintain secure systems and applications .......................................... 26

Implement Strong Access Control Measures ...................................................................................... 36

Requirement 7: Restrict access to cardholder data by business need to know ................................. 36

Requirement 8: Identify and authenticate access to system components ......................................... 38

Requirement 9: Restrict physical access to cardholder data ............................................................. 44

Regularly Monitor and Test Networks .................................................................................................. 52

Requirement 10: Track and monitor all access to network resources and cardholder data ................ 52

Requirement 11: Regularly test security systems and processes ........................................................ 58

Maintain an Information Security Policy .............................................................................................. 65

Requirement 12: Maintain a policy that addresses information security for all personnel ................... 65

Appendix A: Additional PCI DSS Requirements ........................................................................ 72

Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers ............................ 72

Appendix A2: Additional PCI DSS Requirements for Entities using SSL/early TLS ....................... 72

Appendix A3: Designated Entities Supplemental Validation (DESV).............................................. 73

Appendix B: Compensating Controls Worksheet ...................................................................... 74

Appendix C: Explanation of Non-Applicability ........................................................................... 75

Appendix D: Explanation of Requirements Not Tested ............................................................ 76

Section 3: Validation and Attestation Details .....................................................................77

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 January 2017

Before You Begin

SAQ D for Merchants applies to SAQ-eligible merchants not meeting the criteria for any other SAQ type.

Examples of merchant environments that would use SAQ D may include but are not limited to:

 E-commerce merchants who accept cardholder data on their website.

 Merchants with electronic storage of cardholder data

 Merchants that don’t store cardholder data electronically but that do not meet the criteria of

another SAQ type

 Merchants with environments that might meet the criteria of another SAQ type, but that have

additional PCI DSS requirements applicable to their environment

While many organizations completing SAQ D will need to validate compliance with every PCI DSS

requirement, some organizations with very specific business models may find that some requirements do

not apply. See the guidance below for information about the exclusion of certain, specific requirements.

PCI DSS Self-Assessment Completion Steps

1. Identify the applicable SAQ for your environment – refer to the Self-Assessment Questionnaire

Instructions and Guidelines document on PCI SSC website for information.

2. Confirm that your environment is properly scoped and meets the eligibility criteria for the SAQ you are

using.

3. Assess your environment for compliance with PCI DSS requirements.

4. Complete all sections of this document:

 Section 1 (Parts 1 & 2 of the AOC) – Assessment Information and Executive Summary.

 Section 2 – PCI DSS Self-Assessment Questionnaire (SAQ D)

 Section 3 (Parts 3 & 4 of the AOC) – Validation and Attestation Details and Action Plan for Non-

Compliant Requirements (if applicable)

5. Submit the SAQ and Attestation of Compliance (AOC), along with any other requested

documentation—such as ASV scan reports—to your acquirer, payment brand or other requester.

Understanding the Self-Assessment Questionnaire

The questions contained in the “PCI DSS Question” column in this self-assessment questionnaire are

based on the requirements in the PCI DSS.

Additional resources that provide guidance on PCI DSS requirements and how to complete the self-

assessment questionnaire have been provided to assist with the assessment process. An overview of

some of these resources is provided below:

Document

Includes:

PCI DSS

(PCI Data Security Standard

Requirements and Security Assessment

Procedures)

 Guidance on Scoping

 Guidance on the intent of all PCI DSS Requirements

 Details of testing procedures

 Guidance on Compensating Controls

SAQ Instructions and Guidelines

documents

 Information about all SAQs and their eligibility criteria

 How to determine which SAQ is right for your

organization

PCI DSS and PA-DSS Glossary of

Terms, Abbreviations, and Acronyms

 Descriptions and definitions of terms used in the PCI

DSS and self-assessment questionnaires

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 January 2017

These and other resources can be found on the PCI SSC website (www.pcisecuritystandards.org).

Organizations are encouraged to review the PCI DSS and other supporting documents before beginning

an assessment.

Expected Testing

The instructions provided in the “Expected Testing” column are based on the testing procedures in the

PCI DSS, and provide a high-level description of the types of testing activities that should be performed in

order to verify that a requirement has been met. Full details of testing procedures for each requirement

can be found in the PCI DSS.

Completing the Self-Assessment Questionnaire

For each question, there is a choice of responses to indicate your company’s status regarding that

requirement. Only one response should be selected for each question.

A description of the meaning for each response is provided in the table below:

Response

When to use this response:

Yes

The expected testing has been performed, and all elements of the requirement

have been met as stated.

Yes with CCW

(Compensating

Control Worksheet)

The expected testing has been performed, and the requirement has been met

with the assistance of a compensating control.

All responses in this column require completion of a Compensating Control

Worksheet (CCW) in Appendix B of the SAQ.

Information on the use of compensating controls and guidance on how to

complete the worksheet is provided in the PCI DSS.

No

Some or all elements of the requirement have not been met, or are in the

process of being implemented, or require further testing before it will be known

if they are in place.

N/A

(Not Applicable)

The requirement does not apply to the organization’s environment. (See

Guidance for Non-Applicability of Certain, Specific Requirements below for

examples.)

All responses in this column require a supporting explanation in Appendix C of

the SAQ.

Not Tested

The requirement was not included for consideration in the assessment, and

was not tested in any way. (See Understanding the difference between Not

Applicable and Not Tested below for examples of when this option should be

used.)

All responses in this column require a supporting explanation in Appendix D of

the SAQ.

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 January 2017

Guidance for Non-Applicability of Certain, Specific Requirements

While many organizations completing SAQ D will need to validate compliance with every PCI DSS

requirement, some organizations with very specific business models may find that some requirements do

not apply. For example, a company that does not use wireless technology in any capacity would not be

expected to validate compliance with the sections of the PCI DSS that are specific to managing wireless

technology. Similarly, an organization that does not store any cardholder data electronically at any time

would not need to validate requirements related to secure storage of cardholder data (for example,

Requirement 3.4).

Examples of requirements with specific applicability include:

 The questions specific to securing wireless technologies (for example, Requirements 1.2.3, 2.1.1,

and 4.1.1) only need to be answered if wireless is present anywhere in your network. Note that

Requirement 11.1 (use of processes to identify unauthorized wireless access points) must still be

answered even if you don’t use wireless technologies in your network, since the process detects

any rogue or unauthorized devices that may have been added without your knowledge.

 The questions specific to application development and secure coding (Requirements 6.3 and 6.5)

only need to be answered if your organization develops its own custom applications.

 The questions for Requirements 9.1.1 and 9.3 only need to be answered for facilities with

“sensitive areas” as defined here: “Sensitive areas” refers to any data center, server room or any

area that houses systems that store, process, or transmit cardholder data. This excludes the

areas where only point-of-sale terminals are present, such as the cashier areas in a retail store,

but does include retail store back-office server rooms that store cardholder data, and storage

areas for large quantities of cardholder data.

If any requirements are deemed not applicable to your environment, select the “N/A” option for that

specific requirement, and complete the “Explanation of Non-Applicability” worksheet in Appendix C for

each “N/A” entry.

Understanding the difference between Not Applicable and Not Tested

Requirements that are deemed to be not applicable to an environment must be verified as such. Using

the wireless example above, for an organization to select “N/A” for Requirements 1.2.3, 2.1.1, and 4.1.1,

the organization would first need to confirm that there are no wireless technologies used in their CDE or

that connect to their CDE. Once this has been confirmed, the organization may select “N/A” for those

specific requirements.

If a requirement is completely excluded from review without any consideration as to whether it could

apply, the “Not Tested” option should be selected. Examples of situations where this could occur may

include:

 An organization may be asked by their acquirer to validate a subset of requirements—for

example: using the prioritized approach to validate certain milestones.

 An organization may wish to validate a new security control that impacts only a subset of

requirements—for example, implementation of a new encryption methodology that requires

assessment of PCI DSS Requirements 2, 3 and 4.

 A service provider organization might offer a service which covers only a limited number of PCI

DSS requirements—for example, a physical storage provider may only wish to validate the

physical security controls per PCI DSS Requirement 9 for their storage facility.

In these scenarios, the organization only wishes to validate certain PCI DSS requirements even though

other requirements might also apply to their environment.

Legal Exception

If your organization is subject to a legal restriction that prevents the organization from meeting a PCI DSS

requirement, check the “No” column for that requirement and complete the relevant attestation in Part 3.

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 1: Assessment Information January 2017

Part 2f. Third-Party Service Providers

Does your company use a Qualified Integrator & Reseller (QIR)?

If Yes:

Name of QIR Company:

QIR Individual Name:

Description of services provided by QIR:

Yes No

Does your company share cardholder data with any third-party service providers (for

example, Qualified Integrator & Resellers (QIR), gateways, payment processors, payment

service providers (PSP), web-hosting companies, airline booking agents, loyalty program

agents, etc.)?

Yes No

If Yes:

Name of service provider:

Description of services provided:

Note: Requirement 12.8 applies to all entities in this list.

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Section 2: Self-Assessment Questionnaire D for Merchants

Note: The following questions are numbered according to PCI DSS requirements and testing procedures, as defined in the PCI DSS

Requirements and Security Assessment Procedures document.

Self-assessment completion date:

Build and Maintain a Secure Network and Systems

Requirement 1: Install and maintain a firewall configuration to protect data

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

1.1

Are firewall and router configuration standards

established and implemented to include the following:

1.1.1

Is there a formal process for approving and testing all

network connections and changes to the firewall and

router configurations?

 Review documented process

 Interview personnel

 Examine network configurations

1.1.2

(a) Is there a current network diagram that documents

all connections between the cardholder data

environment and other networks, including any

wireless networks?

 Review current network diagram

 Examine network configurations

(b) Is there a process to ensure the diagram is kept

current?

 Interview responsible personnel

1.1.3

(a) Is there a current diagram that shows all cardholder

data flows across systems and networks?

 Review current dataflow diagram

 Examine network configurations.

(b) Is there a process to ensure the diagram is kept

current?

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

1.1.4

(a) Is a firewall required and implemented at each

Internet connection and between any demilitarized

zone (DMZ) and the internal network zone?

 Review firewall configuration

standards

 Observe network configurations to

verify that a firewall(s) is in place

(b) Is the current network diagram consistent with the

firewall configuration standards?

 Compare firewall configuration

standards to current network

diagram

1.1.5

Are groups, roles, and responsibilities for logical

management of network components assigned and

documented in the firewall and router configuration

standards?

 Review firewall and router

configuration standards

 Interview personnel

1.1.6

(a) Do firewall and router configuration standards

include a documented list of services, protocols, and

ports, including business justification and approval

for each?

 Review firewall and router

configuration standards

(b) Are all insecure services, protocols, and ports

identified, and are security features documented and

implemented for each identified service?

 Review firewall and router

configuration standards

 Examine firewall and router

configurations

1.1.7

(a) Do firewall and router configuration standards

require review of firewall and router rule sets at least

every six months?

 Review firewall and router

configuration standards

(b) Are firewall and router rule sets reviewed at least

every six months?

 Examine documentation from

firewall reviews

1.2

Do firewall and router configurations restrict connections

between untrusted networks and any system in the

cardholder 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.

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

1.2.1

(a) Is inbound and outbound traffic restricted to that

which is necessary for the cardholder data

environment?

 Review firewall and router

configuration standards

 Examine firewall and router

configurations

(b) Is all other inbound and outbound traffic specifically

denied (for example by using an explicit “deny all”

or an implicit deny after allow statement)?

 Review firewall and router

configuration standards

 Examine firewall and router

configurations

1.2.2

Are router configuration files secured from unauthorized

access and synchronized—for example, the running (or

active) configuration matches the start-up configuration

(used when machines are booted)?

 Review firewall and router

configuration standards

 Examine router configuration files

and router configurations

1.2.3

Are perimeter firewalls installed between all wireless

networks and the cardholder data environment, and are

these firewalls configured to deny or, if traffic is

necessary for business purposes, permit only authorized

traffic between the wireless environment and the

cardholder data environment?

 Review firewall and router

configuration standards

 Examine firewall and router

configurations

1.3

Is direct public access prohibited between the Internet

and any system component in the cardholder data

environment, as follows:

1.3.1

Is a DMZ implemented to limit inbound traffic to only

system components that provide authorized publicly

accessible services, protocols, and ports?

 Examine firewall and router

configurations

1.3.2

Is inbound Internet traffic limited to IP addresses within

the DMZ?

 Examine firewall and router

configurations

1.3.3

Are anti-spoofing measures implemented to detect and

block forged sourced IP addresses from entering the

network?

(For example, block traffic originating from the internet

with an internal address.)

 Examine firewall and router

configurations

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

1.3.4

Is outbound traffic from the cardholder data environment

to the Internet explicitly authorized?

 Examine firewall and router

configurations

1.3.5

Are only established connections permitted into the

network?

 Examine firewall and router

configurations

1.3.6

Are system components that store cardholder data (such

as a database) placed in an internal network zone,

segregated from the DMZ and other untrusted networks?

 Examine firewall and router

configurations

1.3.7

(a) Are methods in place to prevent the disclosure of

private IP addresses and routing information to the

Internet?

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,

 Removal or filtering of route advertisements for

private networks that employ registered

addressing,

 Internal use of RFC1918 address space instead of

registered addresses.

 Examine firewall and router

configurations

(b) Is any disclosure of private IP addresses and routing

information to external entities authorized?

 Examine firewall and router

configurations

 Interview personnel

1.4

(a) Is personal firewall software (or equivalent

functionality) installed and active on any portable

computing devices (including company and/or

employee-owned) that connect to the Internet when

outside the network (for example, laptops used by

employees), and which are also used to access the

CDE?

 Review policies and configuration

standards

 Examine mobile and/or employee-

owned devices

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

(b) Is the personal firewall software (or equivalent

functionality) configured to specific configuration

settings, actively running, and not alterable by users

of mobile and/or employee-owned devices?

 Review policies and configuration

standards

 Examine mobile and/or employee-

owned devices

1.5

Are security policies and operational procedures for

managing firewalls:

 Documented

 In use

 Known to all affected parties?

 Review security policies and

operational procedures

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Requirement 2: Do not use vendor-supplied defaults for system passwords and other security parameters

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

2.1

(a) Are vendor-supplied defaults always changed before

installing a system on the network?

This applies to ALL default passwords, including but not

limited to those used by operating systems, software that

provides security services, application and system

accounts, point-of-sale (POS) terminals, payment

applications, Simple Network Management Protocol

(SNMP) community strings, etc.).

 Review policies and procedures

 Examine vendor documentation

 Observe system configurations

and account settings

 Interview personnel

(b) Are unnecessary default accounts removed or

disabled before installing a system on the network?

 Review policies and procedures

 Review vendor documentation

 Examine system configurations

and account settings

 Interview personnel

2.1.1

For wireless environments connected to the cardholder

data environment or transmitting cardholder data, are ALL

wireless vendor defaults changed at installations, as

follows:

(a) Are encryption keys changed from default at

installation, and changed anytime anyone with

knowledge of the keys leaves the company or

changes positions?

 Review policies and procedures

 Review vendor documentation

 Interview personnel

(b) Are default SNMP community strings on wireless

devices changed at installation?

 Review policies and procedures

 Review vendor documentation

 Interview personnel

 Examine system configurations

(c) Are default passwords/passphrases on access points

changed at installation?

 Review policies and procedures

 Interview personnel

 Examine system configurations

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each

question)

Yes

with

CCW

No

N/A

Not

Tested

3.6.3

Do cryptographic key procedures include secure

cryptographic key storage?

 Review key-management

procedures

 Observe the method for secure

storage of keys

3.6.4

Do cryptographic key procedures include cryptographic

key changes for keys that have reached the end of their

defined cryptoperiod (for example, after a defined period

of time has passed and/or after 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)?

 Review key-management

procedures

 Interview personnel

3.6.5

(a) Do cryptographic key procedures include retirement

or replacement (for example, archiving, destruction,

and/or revocation) of cryptographic keys when the

integrity of the key has been weakened (for

example, departure of an employee with knowledge

of a clear-text key)?

 Review key-management

procedures

 Interview personnel

(b) Do cryptographic key procedures include

replacement of known or suspected compromised

keys?

 Review key-management

procedures

 Interview personnel

(c) If retired or replaced cryptographic keys are retained,

are these keys only used for decryption/verification

purposes, and not used for encryption operations?

 Review key-management

procedures

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each

question)

Yes

with

CCW

No

N/A

Not

Tested

3.6.6

If manual clear-text key-management operations are

used, do cryptographic key procedures include split

knowledge and dual control of cryptographic keys as

follows:

 Do split knowledge procedures require that key

components are under the control of at least two

people who only have knowledge of their own key

components?

AND

 Do dual control procedures require that at least two

people are required to perform any key

management operations and no one person has

access to the authentication materials (for example,

passwords or keys) of another?

Note: Examples of manual key management operations

include, but are not limited to: key generation,

transmission, loading, storage and destruction.

 Review key-management

procedures

 Interview personnel and/or

 Observe processes

3.6.7

Do cryptographic key procedures include the prevention

of unauthorized substitution of cryptographic keys?

 Review procedures

 Interview personnel and/or

 Observe processes

3.6.8

Are cryptographic key custodians required to formally

acknowledge (in writing or electronically) that they

understand and accept their key-custodian

responsibilities?

 Review procedures

 Review documentation or other

evidence

3.7

Are security policies and operational procedures for

protecting stored cardholder data:

 Documented

 In use

 Known to all affected parties?

 Review security policies and

operational procedures

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Requirement 4: Encrypt transmission of cardholder data across open, public networks

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

4.1

(a) Are strong cryptography and security protocols used to

safeguard sensitive cardholder data during transmission

over open, public networks?

Note: Where SSL/early TLS is used, the requirements in

Appendix A2 must be completed.

Examples of open, public networks include but are not limited

to the Internet; wireless technologies, including 802.11 and

Bluetooth; cellular technologies, for example, Global System

for Mobile communications (GSM), Code division multiple

access (CDMA); and General Packet Radio Service (GPRS).

 Review documented

standards

 Review policies and

procedures

 Review all locations where

CHD is transmitted or received

 Examine system

configurations

(b) Are only trusted keys and/or certificates accepted?

 Observe inbound and

outbound transmissions

 Examine keys and certificates

(c) Are security protocols implemented to use only secure

configurations, and to not support insecure versions or

configurations?

 Examine system

configurations

(d) Is the proper encryption strength implemented for the

encryption methodology in use (check vendor

recommendations/best practices)?

 Review vendor documentation

 Examine system

configurations

(e) For TLS implementations, is TLS enabled whenever

cardholder data is transmitted or received?

For example, for browser-based implementations:

 “HTTPS” appears as the browser Universal Record

Locator (URL) protocol, and

 Cardholder data is only requested if “HTTPS” appears as

part of the URL.

 Examine system

configurations

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

4.1.1

Are industry best practices used to implement strong

encryption for authentication and transmission for wireless

networks transmitting cardholder data or connected to the

cardholder data environment?

 Review documented

standards

 Review wireless networks

 Examine system configuration

settings

4.2

(a) Are PANs rendered unreadable or secured with strong

cryptography whenever they are sent via end-user

messaging technologies (for example, e-mail, instant

messaging, SMS, chat, etc.)?

 Observe processes

 Review outbound

transmissions

(b) Are policies in place that state that unprotected PANs are

not to be sent via end-user messaging technologies?

 Review policies and

procedures

4.3

Are security policies and operational procedures for

encrypting transmissions of cardholder data:

 Documented

 In use

 Known to all affected parties?

 Review security policies and

operational procedures

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Maintain a Vulnerability Management Program

Requirement 5: Protect all systems against malware and regularly update anti-virus software or programs

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

5.1

Is anti-virus software deployed on all systems commonly

affected by malicious software?

 Examine system configurations

5.1.1

Are anti-virus programs capable of detecting, removing,

and protecting against all known types of malicious

software (for example, viruses, Trojans, worms, spyware,

adware, and rootkits)?

 Review vendor documentation

 Examine system configurations

5.1.2

Are periodic evaluations performed to identify and

evaluate evolving malware threats in order to confirm

whether those systems considered to not be commonly

affected by malicious software continue as such?

 Interview personnel

5.2

Are all anti-virus mechanisms maintained as follows:

(a) Are all anti-virus software and definitions kept

current?

 Examine policies and procedures

 Examine anti-virus

configurations, including the

master installation

 Examine system components

(b) Are automatic updates and periodic scans enabled

and being performed?

 Examine anti-virus

configurations, including the

master installation

 Examine system components

(c) Are all anti-virus mechanisms generating audit logs,

and are logs retained in accordance with PCI DSS

Requirement 10.7?

 Examine anti-virus configurations

 Review log retention processes

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

5.3

Are all anti-virus mechanisms:

 Actively running?

 Unable to be disabled or altered by users?

Note: Anti-virus solutions may be temporarily disabled

only if there is legitimate technical need, as authorized by

management on a case-by-case basis. If anti-virus

protection needs to be disabled for a specific purpose, it

must be formally authorized. Additional security measures

may also need to be implemented for the period of time

during which anti-virus protection is not active.

 Examine anti-virus configurations

 Examine system components

 Observe processes

 Interview personnel

5.4

Are security policies and operational procedures for

protecting systems against malware:

 Documented

 In use

 Known to all affected parties?

 Review security policies and

operational procedures

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Implement Strong Access Control Measures

Requirement 7: Restrict access to cardholder data by business need to know

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

7.1

Is access to system components and cardholder data

limited to only those individuals whose jobs require such

access, as follows:

 Is there a written policy for access control that

incorporates the following?

 Defining access needs and privilege assignments

for each role

 Restriction of access to privileged user IDs to least

privileges necessary to perform job responsibilities,

 Assignment of access based on individual

personnel’s job classification and function

 Documented approval (electronically or in writing)

by authorized parties for all access, including

listing of specific privileges approved

 Examine written access

control policy

7.1.1

Are access needs for each role defined, including:

 System components and data resources that each

role needs to access for their job function?

 Level of privilege required (for example, user,

administrator, etc.) for accessing resources?

 Examine roles and access

needs

7.1.2

Is access to privileged user IDs restricted as follows:

 To least privileges necessary to perform job

responsibilities?

 Assigned only to roles that specifically require that

privileged access?

 Interview personnel

 Interview management

 Review privileged user IDs

7.1.3

Is access assigned based on individual personnel’s job

classification and function?

 Interview management

 Review user IDs

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

7.1.4

Is documented approval by authorized parties required,

specifying required privileges?

 Review user IDs

 Compare with documented

approvals

 Compare assigned privileges

with documented approvals

7.2

Is an access control system(s) in place for system

components to restrict access based on a user’s need to

know, and is it set to “deny all” unless specifically allowed,

as follows:

7.2.1

Is the access control system(s) in place on all system

components?

 Review vendor documentation

 Examine configuration

settings

7.2.2

Is the access control system(s) configured to enforce

privileges assigned to individuals based on job

classification and function?

 Review vendor documentation

 Examine configuration

settings

7.2.3

Does the access control system(s) have a default “deny-

all” setting?

 Review vendor documentation

 Examine configuration

settings

7.3

Are security policies and operational procedures for

restricting access to cardholder data:

 Documented

 In use

 Known to all affected parties?

 Examine security policies and

operational procedures

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Requirement 8: Identify and authenticate access to system components

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

8.1

Are policies and procedures for user identification

management controls defined and in place for non-

consumer users and administrators on all system

components, as follows:

8.1.1

Are all users assigned a unique ID before allowing them

to access system components or cardholder data?

 Review password procedures

 Interview personnel

8.1.2

Are additions, deletions, and modifications of user IDs,

credentials, and other identifier objects controlled such

that user IDs are implemented only as authorized

(including with specified privileges)?

 Review password procedures

 Examine privileged and general

user IDs and associated

authorizations

 Observe system settings

8.1.3

Is access for any terminated users immediately

deactivated or removed?

 Review password procedures

 Examine terminated users

accounts

 Review current access lists

 Observe returned physical

authentication devices

8.1.4

Are inactive user accounts either removed or disabled

within 90 days?

 Review password procedures

 Observe user accounts

8.1.5

(a) Are accounts used by third parties to access,

support, or maintain system components via remote

access enabled only during the time period needed

and disabled when not in use?

 Review password procedures

 Interview personnel

 Observe processes

(b) Are third party remote access accounts monitored

when in use?

 Interview personnel

 Observe processes

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

8.1.6

(a) Are repeated access attempts limited by locking out

the user ID after no more than six attempts?

 Review password procedures

 Examine system configuration

settings

(b) This testing procedure applies only to service

providers.

8.1.7

Once a user account is locked out, is the lockout duration

set to a minimum of 30 minutes or until an administrator

enables the user ID?

 Review password procedures

 Examine system configuration

settings

8.1.8

If a session has been idle for more than 15 minutes, are

users required to re-authenticate (for example, re-enter

the password) to re-activate the terminal or session?

 Review password procedures

 Examine system configuration

settings

8.2

In addition to assigning a unique ID, is one or more of the

following methods employed to authenticate all users?

 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

 Review password procedures

 Observe authentication

processes

8.2.1

(a) Is strong cryptography used to render all

authentication credentials (such as

passwords/passphrases) unreadable during

transmission and storage on all system components?

 Review password procedures

 Review vendor documentation

 Examine system configuration

settings

 Observe password files

 Observe data transmissions

(b) This testing procedure applies only to service

providers.

8.2.2

Is user identity verified before modifying any

authentication credential (for example, performing

password resets, provisioning new tokens, or generating

new keys)?

 Review authentication

procedures

 Observe personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

8.2.3

(a) Are user password parameters configured to require

passwords/passphrases meet the following?

 A minimum password length of at least seven

characters

 Contain both numeric and alphabetic characters

Alternatively, the passwords/passphrases must have

complexity and strength at least equivalent to the

parameters specified above.

 Examine system configuration

settings to verify password

parameters

(b) This testing procedure applies only to service

providers.

8.2.4

(a) Are user passwords/passphrases changed at least

once every 90 days?

 Review password procedures

 Examine system configuration

settings

(b) This testing procedure applies only to service

providers.

8.2.5

(a) Must an individual submit a new

password/passphrase that is different from any of the

last four passwords/passphrases he or she has

used?

 Review password procedures

 Sample system components

 Examine system configuration

settings

(b) This testing procedure applies only to service

providers.

8.2.6

Are passwords/passphrases set to a unique value for

each user for first-time use and upon reset, and must

each user change their password immediately after the

first use?

 Review password procedures

 Examine system configuration

settings

 Observe security personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

8.3

Is all individual non-console administrative access and all

remote access to the CDE secured using multi-factor

authentication as follows:

Note: Multi-factor authentication requires that a minimum

of two of the three authentication methods (see PCI DSS

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 multi-factor authentication.

8.3.1

Is multi-factor authentication incorporated for all non-

console access into the CDE for personnel with

administrative access?

Note: This requirement is a best practice until January

31, 2018, after which it becomes a requirement.

 Examine system configurations

 Observe administrator logging

into CDE

8.3.2

Is multi-factor authentication incorporated for all remote

network access (both user and administrator, and

including third party access for support or maintenance)

originating from outside the entity’s network?

 Examine system configurations

 Observe personnel connecting

remotely

8.4

(a) Are authentication policies and procedures

documented and communicated to all users?

 Review policies and procedures

 Review distribution method

 Interview personnel

 Interview users

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Requirement 9: Restrict physical access to cardholder data

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

9.1

Are appropriate facility entry controls in place to limit and

monitor physical access to systems in the cardholder

data environment?

 Observe physical access controls

 Observe personnel

9.1.1

(a) Are either video cameras or access-control

mechanisms (or both) in place to monitor individual

physical access to sensitive areas?

Note: “Sensitive areas” refers to any data center, server

room, or any area that houses systems that store,

process, or transmit cardholder data. This excludes

public-facing areas where only point-of-sale terminals

are present such as the cashier areas in a retail store.

 Review policies and procedures

 Observe physical monitoring

mechanisms

 Observe security features

(b) Are either video cameras or access-control

mechanisms (or both) protected from tampering or

disabling?

 Observe processes

 Interview personnel

(c) Is data collected from video cameras and/or access

control mechanisms reviewed and correlated with

other entries?

 Review policies and procedures

 Interview security personnel

(d) Is data collected from video cameras and/or access

control mechanisms stored for at least three months

unless otherwise restricted by law?

 Review data retention processes

 Observe data storage

 Interview security personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Regularly Monitor and Test Networks

Requirement 10: Track and monitor all access to network resources and cardholder data

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

10.1

(a) Are audit trails enabled and active for system

components?

 Observe processes

 Interview system

administrator

(b) Is access to system components linked to

individual users?

 Observe processes

 Interview system

administrator

10.2

Are automated audit trails implemented for all system

components to reconstruct the following events:

10.2.1

All individual user accesses to cardholder data?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.2.2

All actions taken by any individual with root or

administrative privileges?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.2.3

Access to all audit trails?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.2.4

Invalid logical access attempts?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.2.5

Use of and changes to identification and authentication

mechanisms–including but not limited to creation of

new accounts and elevation of privileges – and all

changes, additions, or deletions to accounts with root or

administrative privileges?

 Interview personnel

 Observe audit logs

 Examine audit log settings

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

10.2.6

Initialization, stopping, or pausing of the audit logs?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.2.7

Creation and deletion of system-level objects?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.3

Are the following audit trail entries recorded for all

system components for each event:

10.3.1

User identification?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.3.2

Type of event?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.3.3

Date and time?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.3.4

Success or failure indication?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.3.5

Origination of event?

 Interview personnel

 Observe audit logs

 Examine audit log settings

10.3.6

Identity or name of affected data, system component, or

resource?

 Interview personnel

 Observe audit logs

 Examine audit log settings

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

10.4

Are all critical system clocks and times synchronized

through use of time synchronization technology, and is

the technology kept current?

Note: One example of time synchronization technology

is Network Time Protocol (NTP).

 Review time configuration

standards and processes

10.4.1

Are the following processes implemented for critical

systems to have the correct and consistent time:

(a) Do only designated central time server(s) receive

time signals from external sources, and are time

signals from external sources based on

International Atomic Time or UTC?

 Review time configuration

standards and processes

 Examine time-related system

parameters

(b) Where there is more than one designated time

server, do the time servers peer with each other to

keep accurate time?

 Review time configuration

standards and processes

 Examine time-related system

parameters

(c) Do systems receive time only from designated

central time server(s)?

 Review time configuration

standards and processes

 Examine time-related system

parameters

10.4.2

Is time data is protected as follows:

(a) Is access to time data restricted to only personnel

with a business need to access time data?

 Examine system

configurations and time-

synchronization settings

(b) Are changes to time settings on critical systems

logged, monitored, and reviewed?

 Examine system

configurations and time-

synchronization settings and

logs

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

10.4.3

Are time settings received from specific, industry-

accepted time sources? (This is 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).

 Examine system

configurations

10.5

Are audit trails secured so they cannot be altered, as

follows:

10.5.1

Is viewing of audit trails limited to those with a job-

related need?

 Interview system

administrators

 Examine system

configurations and

permissions

10.5.2

Are audit trail files protected from unauthorized

modifications via access control mechanisms, physical

segregation, and/or network segregation?

 Interview system

administrators

 Examine system

configurations and

permissions

10.5.3

Are audit trail files promptly backed up to a centralized

log server or media that is difficult to alter?

 Interview system

administrators

 Examine system

configurations and

permissions

10.5.4

Are logs for external-facing technologies (for example,

wireless, firewalls, DNS, mail) written onto a secure,

centralized, internal log server or media?

 Interview system

administrators

 Examine system

configurations and

permissions

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

10.5.5

Is file-integrity monitoring or change-detection software

used on logs to ensure that existing log data cannot be

changed without generating alerts (although new data

being added should not cause an alert)?

 Examine settings, monitored

files, and results from

monitoring activities

10.6

Are logs and security events for all system components

reviewed to identify anomalies or suspicious activity as

follows?

Note: Log harvesting, parsing, and alerting tools may

be used to achieve compliance with Requirement 10.6.

10.6.1

(a) Are written policies and procedures defined for

reviewing the following at least daily, either

manually or via log tools?

 All security events

 Logs of all system components that store,

process, or transmit CHD and/or SAD

 Logs of all critical system components

 Logs of all servers and system components that

perform security functions (for example,

firewalls, intrusion-detection systems/intrusion-

prevention systems (IDS/IPS), authentication

servers, e-commerce redirection servers, etc.)

 Review security policies and

procedures

(b) Are the above logs and security events reviewed at

least daily?

 Observe processes

 Interview personnel

10.6.2

(a) Are written policies and procedures defined for

reviewing logs of all other system components

periodically—either manually or via log tools—

based on the organization’s policies and risk

management strategy?

 Review security policies and

procedures

(b) Are reviews of all other system components

performed in accordance with organization’s

policies and risk management strategy?

 Review risk assessment

documentation

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

10.6.3

(a) Are written policies and procedures defined for

following up on exceptions and anomalies

identified during the review process?

 Review security policies and

procedures

(b) Is follow up to exceptions and anomalies

performed?

 Observe processes

 Interview personnel

10.7

(a) Are audit log retention policies and procedures in

place and do they require that logs are retained for

at least one year, with a minimum of three months

immediately available for analysis (for example,

online, archived, or restorable from backup)?

 Review security policies and

procedures

(b) Are audit logs retained for at least one year?

 Interview personnel

 Examine audit logs

(c) Are at least the last three months’ logs immediately

available for analysis?

 Interview personnel

 Observe processes

10.8

This requirement applies only to service providers

10.9

Are security policies and operational procedures for

monitoring all access to network resources and

cardholder data:

 Documented

 In use

 Known to all affected parties?

 Review security policies and

operational procedures

 Interview personnel

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Requirement 11: Regularly test security systems and processes

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

11.1

(a) Are processes implemented for detection and

identification of both authorized and 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.

 Review policies and procedures

(b) Does the methodology detect and identify any

unauthorized wireless access points, including at least

the following?

 WLAN cards inserted into system components;

 Portable or mobile devices attached to system

components to create a wireless access point (for

example, by USB, etc.); and

 Wireless devices attached to a network port or

network device.

 Evaluate the methodology

(c) If wireless scanning is utilized to identify authorized and

unauthorized wireless access points, is the scan

performed at least quarterly for all system components

and facilities?

 Examine output from recent

wireless scans

(d) If automated monitoring is utilized (for example, wireless

IDS/IPS, NAC, etc.), is monitoring configured to

generate alerts to notify personnel?

 Examine configuration settings

11.1.1

Is an inventory of authorized wireless access points

maintained and a business justification documented for all

authorized wireless access points?

 Examine inventory records

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

11.1.2

(a) Does the incident response plan define and require a

response in the event that an unauthorized wireless

access point is detected?

 Examine incident response plan

(see Requirement 12.10)

(b) Is action taken when unauthorized wireless access points

are found?

 Interview responsible personnel

 Inspect recent wireless scans

and related responses

11.2

Are internal and external network vulnerability scans run 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), as follows?

Note: Multiple scan reports can be combined for the

quarterly scan process to show that all systems were

scanned and all applicable vulnerabilities have been

addressed. Additional documentation may be required to

verify non-remediated vulnerabilities are in the process of

being addressed.

For initial PCI DSS compliance, it is not required that four

quarters of passing scans be completed 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 re-scan(s). For

subsequent years after the initial PCI DSS review, four

quarters of passing scans must have occurred.

11.2.1

(a) Are quarterly internal vulnerability scans performed?

 Review scan reports

(b) Does the quarterly internal scan process address all

“high risk” vulnerabilities and include rescans to verify all

“high-risk” vulnerabilities (as defined in PCI DSS

Requirement 6.1) are resolved?

 Review scan reports

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

12.5.4

Administering user accounts, including additions, deletions,

and modifications?

 Review information security

policy and procedures

12.5.5

Monitoring and controlling all access to data?

 Review information security

policy and procedures

12.6

(a) Is a formal security awareness program in place to

make all personnel aware of the cardholder data

security policy and procedures?

 Review security awareness

program

(b) Do security awareness program procedures include

the following:

12.6.1

(a) Does the security awareness program provide multiple

methods of communicating awareness and educating

personnel (for example, posters, letters, memos, web

based training, meetings, and promotions)?

Note: Methods can vary depending on the role of the

personnel and their level of access to the cardholder data.

 Review security awareness

program

 Review security awareness

program procedures

 Review security awareness

program attendance records

(b) Are personnel educated upon hire and at least

annually?

 Examine security awareness

program procedures and

documentation

(c) Have employees completed awareness training and

are they aware of the importance of cardholder data

security?

 Interview personnel

12.6.2

Are personnel required to acknowledge at least annually

that they have read and understood the security policy and

procedures?

 Examine security awareness

program procedures and

documentation

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

12.7

Are potential personnel (see definition of “personnel”

above) screened 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.

 Interview Human Resource

department management

12.8

Are policies and procedures maintained and implemented

to manage service providers with whom cardholder data is

shared, or that could affect the security of cardholder data,

as follows:

12.8.1

Is a list of service providers maintained, including a

description of the service(s) provided?

 Review policies and procedures

 Observe processes

 Review list of service providers

12.8.2

Is a written agreement maintained that includes an

acknowledgement that the service providers are

responsible for the security of cardholder data the service

providers possess or otherwise store, process, or transmit

on behalf of the customer, or to the extent that they could

impact the security of the customer’s cardholder data

environment?

Note: The exact wording of an acknowledgement will

depend on the agreement between the two parties, the

details of the service being provided, and the

responsibilities assigned to each party. The

acknowledgement does not have to include the exact

wording provided in this requirement.

 Observe written agreements

 Review policies and procedures

12.8.3

Is there an established process for engaging service

providers, including proper due diligence prior to

engagement?

 Observe processes

 Review policies and procedures

and supporting documentation

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

12.8.4

Is a program maintained to monitor service providers’ PCI

DSS compliance status at least annually?

 Observe processes

 Review policies and procedures

and supporting documentation

12.8.5

Is information maintained about which PCI DSS

requirements are managed by each service provider, and

which are managed by the entity?

 Observe processes

 Review policies and procedures

and supporting documentation

12.9

This requirement applies only to service providers.

12.10

Has an incident response plan been implemented in

preparation to respond immediately to a system breach, as

follows:

12.10.1

(a) Has an incident response plan been created to be

implemented in the event of system breach?

 Review the incident response

plan

 Review incident response plan

procedures

(b) Does the plan address 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?

 Review incident response plan

procedures

 Specific incident response procedures?

 Review incident response plan

procedures

 Business recovery and continuity procedures?

 Review incident response plan

procedures

 Data backup processes?

 Review incident response plan

procedures

 Analysis of legal requirements for reporting

compromises?

 Review incident response plan

procedures

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

 Coverage and responses of all critical system

components?

 Review incident response plan

procedures

 Reference or inclusion of incident response

procedures from the payment brands?

 Review incident response plan

procedures

12.10.2

Is the plan reviewed and tested at least annually, including

all elements listed in Requirement 12.10.1?

 Review incident response plan

procedures

 Interview responsible personnel

12.10.3

Are specific personnel designated to be available on a

24/7 basis to respond to alerts?

 Observe processes

 Review policies

 Interview responsible personnel

12.10.4

Is appropriate training provided to staff with security breach

response responsibilities?

 Observe processes

 Review incident response plan

procedures

 Interview responsible personnel

12.10.5

Are alerts from security monitoring systems included in the

incident response plan?

 Observe processes

 Review incident response plan

procedures

12.10.6

Is a process developed and in place to modify and evolve

the incident response plan according to lessons learned

and to incorporate industry developments?

 Observe processes

 Review incident response plan

procedures

 Interview responsible personnel

12.11

This requirement applies only to service providers

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

Appendix A: Additional PCI DSS Requirements

Appendix A1: Additional PCI DSS Requirements for Shared Hosting Providers

This appendix is not used for merchant assessments.

Appendix A2: Additional PCI DSS Requirements for Entities using SSL/early TLS

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

A2.1

For POS POI terminals (and the SSL/TLS termination

points to which they connect) using SSL and/or early TLS:

 Are the devices confirmed to not be susceptible to any

known exploits for SSL/early TLS

Or:

 Is there a formal Risk Mitigation and Migration Plan in

place per Requirement A2.2?

 Review documentation (for

example, vendor documentation,

system/network configuration

details, etc.) that verifies POS POI

devices are not susceptible to any

known exploits for SSL/early TLS

A2.2

Is there a formal Risk Mitigation and Migration Plan in place

for all implementations that use SSL and/or early TLS

(other than as allowed in A2.1), that includes:

 Description of usage, including; what data is

being transmitted, types and number of systems

that use and/or support SSL/early TLS, type of

environment;

 Risk assessment results and risk reduction

controls in place;

 Description of processes to monitor for new

vulnerabilities associated with SSL/early TLS;

 Description of change control processes that are

implemented to ensure SSL/early TLS is not

implemented into new environments;

 Overview of migration project plan including

target migration completion date no later than

30th June 2018?

 Review the documented Risk

Mitigation and Migration Plan

PCI DSS v3.2 SAQ D for Merchants, Rev. 1.1 – Section 2: Self-Assessment Questionnaire January 2017

PCI DSS Question

Expected Testing

Response

(Check one response for each question)

Yes

with

CCW

No

N/A

Not

Tested

A2.3

This requirement applies only to service providers

Appendix A3: Designated Entities Supplemental Validation (DESV)

This Appendix applies only to entities designated by a payment brand(s) or acquirer as requiring additional validation of existing PCI DSS

requirements. Entities required to validate to this Appendix should use the DESV Supplemental Reporting Template and Supplemental Attestation

of Compliance for reporting, and consult with the applicable payment brand and/or acquirer for submission procedures.

Fill Online, Printable, Fillable, Blank PCI-DSS-v3 2-SAQ-D Merchant-rev1 1 Form

Related forms

Fillable PCI-DSS-v3 2-SAQ-D Merchant-rev1 1

Fill Online, Printable, Fillable, Blank PCI-DSS-v3 2-SAQ-D Merchant-rev1 1 Form

Related forms

First 20 documents completely FREE!