Site icon RSI Security

How to Prepare for a PCI DSS Assessment: A Readiness Guide

Preparing for a PCI DSS assessment starts with confirming how you must validate and what is in scope. Next, update your diagrams, compare your controls to the requirements, close the gaps, and gather evidence. Then complete your SAQ or support your assessor with records that show each control working.

Readiness steps at a glance

  1. Confirm how you must validate. Ask your acquirer or the requesting organization whether you need a Self-Assessment Questionnaire (SAQ) or a Report on Compliance (ROC), and when your results are due.
  2. Confirm your scope. Identify every location and flow of account data, plus the systems that connect to the cardholder data environment (CDE) or could affect its security.
  3. Update your diagrams. Bring your network and data flow diagrams up to date, and make sure they reconcile with each other.
  4. Run a gap assessment. Compare each applicable requirement to what you actually do, and assign an owner to each gap.
  5. Close the gaps. Finish remediation before you validate, since scheduled work does not count as in place.
  6. Gather evidence. Collect the documents, configurations, and records that show each control is in place and operating.
  7. Complete and submit. Finish your SAQ or assessment report and the Attestation of Compliance, then submit them to the requesting organization.

Confirm your validation route

Payment brands and acquirers decide who must validate and how. Merchants and service providers should confirm this first, because it sets the depth of the work. If you might qualify for an SAQ, use this table for a first look, then confirm the eligibility criteria.

If you are or use… Likely starting point Why
Service provider handling account data for others SAQ D for Service Providers Only for service providers a payment brand defines as eligible. Others report through a ROC, so confirm with the payment brand or your acquirer.
Merchant that stores account data electronically SAQ D for Merchants The other merchant SAQs exclude electronic storage of account data. SAQ D covers all applicable requirements.
E-commerce: site redirects to, or embeds, a provider page or iframe SAQ A For merchants that fully outsource all account data functions, where every element of the payment page comes only and directly from a compliant provider. SAQ A also has an eligibility criterion about script attacks, so check it closely.
E-commerce: your site hosts the form, but the browser sends card data directly to the provider SAQ A-EP Your website doesn’t receive account data but controls how it reaches the provider, so it can affect the security of the transaction.
E-commerce: card data reaches your server, and you pass it on SAQ D for Merchants Merchants that accept account data on their website don’t meet the SAQ A or SAQ A-EP criteria.
Mail or phone orders, fully outsourced to a provider SAQ A For card-not-present merchants that fully outsource all account data functions to PCI DSS compliant providers.
Terminal on the PCI-listed validated P2PE list SAQ P2PE All payment processing runs through a validated, PCI-listed P2PE solution. Phone or mail orders may qualify when keyed directly and only into those terminals.
Phone or tablet with a PCI-listed SPoC solution (in person only) SAQ SPoC Card-present only, using a validated software-based PIN entry solution with a secure card reader. Excludes phone and mail orders, e-commerce, and unattended payments.
Standalone, PCI-listed terminal with its own IP connection SAQ B-IP Only standalone, PCI-listed PTS devices with their own IP connection to the processor, not connected to other merchant systems. Card readers that pair with a phone or computer don’t qualify.
Imprint machines or a dial-out terminal SAQ B Only imprint machines or standalone dial-out terminals, with no electronic storage.
Typing cards into a provider website (virtual terminal) on an isolated computer SAQ C-VT Only keying single transactions into a third-party virtual terminal on an isolated computing device, with no attached card readers.
Payment application on an internet-connected system SAQ C A single location with payment application systems connected to the internet, isolated from other merchant systems, and no electronic account data storage. If locations connect to each other, SAQ D may apply.
Integrated or networked terminals, or not sure SAQ C or SAQ D Ask your acquirer which applies.
More than one of these channels Ask your acquirer Many SAQs require that channel to be your only one. SAQ D applies if you meet no other SAQ criteria.

This is a starting point only. Each SAQ has its own eligibility criteria, and your acquirer or payment brand has the final say on how you validate.

Scope your environment

PCI DSS calls accurate scoping the first step in preparing for an assessment. Requirement 12.5.2 sets the minimum steps:

Consider backup, recovery, and fail-over sites as well. Keep documentation showing how you determined scope. Your assessor will validate your scope, but that check does not replace your own confirmation.

Draw your network and data flow diagrams

Your network diagram (1.2.3) shows all connections between the CDE and other networks, including wireless networks. Your data flow diagram (1.2.4) shows how account data moves across systems and networks.

Walk one transaction through each channel, from where the data enters to its final disposition. PCI SSC suggests including authorization, capture, settlement, chargebacks, refunds, paper records, and file backups. Add the date of the last update and the people who made and approved it.

Some short SAQs do not include these two requirements. SAQ A is one example. Mapping your payment flow still helps you confirm that your setup fits the eligibility criteria.

Run a gap assessment

A gap assessment compares your current practice with the requirements that apply to you. Use the testing procedures in PCI DSS, or the Expected Testing column of your SAQ, as your test for each item. Record the status, the owner, the evidence you found, and the action needed.

Sort the results by effect and effort. Fix scope-related issues early, since removing data or systems can eliminate later work. If a legitimate, documented constraint prevents you from meeting a requirement as written, assess whether a compensating control fits. Our page on common mistakes shows what to watch for.

Check your frequencies as well. For a first assessment against a requirement, you generally show the activity in the most recent period and documented procedures to continue it. In later years, you show every period.

Gather your evidence

Assessment testing relies on examining evidence, observing activity, and interviewing personnel. Prepare for all three by naming the people who can explain each control.

Area Evidence to gather Requirement
Scope Scope confirmation records and in-scope component inventory 12.5.1, 12.5.2
Network Diagrams and control configuration reviews 1.2.3, 1.2.4, 1.2.7
Access Access review records and MFA configurations 7.2.4, 8.4.2, 8.4.3
Logging Audit log settings and review records 10.2.1, 10.4.1
Testing Approved Scanning Vendor (ASV) reports, internal scans, and penetration test results 11.3.1, 11.3.2, 11.4.2, 11.4.3
Risk Each required targeted risk analysis 12.3.1
Providers Provider list, written agreements, responsibility records, and status checks 12.8.1, 12.8.2, 12.8.4, 12.8.5
Program Policy reviews, training records, and incident response plan tests 12.1.2, 12.6.3, 12.10.2

Fill out your SAQ

Each SAQ follows the same pattern. First, confirm that you meet its eligibility criteria and that your environment is properly scoped. Then assess your environment and complete all three sections: assessment information, the questionnaire, and validation and attestation details.

Choose one response for each requirement:

Response When to use it
In Place You performed the expected testing and met every element
In Place with CCW You met the requirement with a compensating control and completed the worksheet
Not Applicable The requirement does not apply, and you explain why in the appendix
Not Tested You excluded it from review, where your SAQ offers this response
Not in Place Some elements are unmet, still in progress, or need more testing

A compliant result needs every assessed requirement marked In Place, In Place with CCW, or Not Applicable, with all sections complete. If a local law prevents you from meeting a requirement, follow the SAQ’s legal exception instructions. Contractual obligations and legal advice do not qualify.

SAQs cannot document the customized approach. After you finish, submit the SAQ and Attestation of Compliance to the requesting organization, along with anything else it asked for.

Working with an assessor

If you need a ROC, share your scope documents, diagrams, and evidence index early. Our page on how PCI DSS works explains the process, and our guide to choosing a provider covers selection.

Frequently asked questions

What is the difference between Not Applicable and Not Tested on an SAQ?
Not Applicable means you verified that a requirement does not apply to your environment. Not Tested means you excluded it from review without considering whether it could apply, which makes the assessment partial, and not every SAQ offers this response.
Is a gap assessment required for PCI DSS?
PCI DSS does not list a gap assessment as a requirement. It is a preparation practice that shows what to fix before you validate.
Can I use the customized approach on an SAQ?
No. SAQs cannot document the customized approach. Ask your acquirer or payment brand whether you may complete a ROC instead.
What do I submit after completing an SAQ?
You submit the SAQ and Attestation of Compliance, along with any other requested documentation such as ASV scan reports. They go to the organization that requested them, such as your acquirer or a payment brand.

Work with RSI Security

RSI Security is a PCI Qualified Security Assessor (QSA) company and an Approved Scanning Vendor (ASV). It performs PCI DSS assessments and quarterly ASV scans. Organizations that need help with scoping or readiness can work with RSI Security through a separate advisory engagement. RSI Security provides either advisory or assessment to a given client, never both.

Schedule a PCI DSS assessment · Talk to an advisor about readiness

Sources

Request a consultation

Exit mobile version