How PCI DSS Compliance Works: From Scoping to Validation

PCI DSS compliance works as a repeating cycle. You confirm your scope, assess your controls against the requirements, and document results in a Report on Compliance or Self-Assessment Questionnaire. You then complete an Attestation of Compliance, submit it to the requesting organization, and keep your controls running.

The cycle at a glance

PCI DSS outlines the same high-level steps for most assessments. The roles in each step vary by assessment type and by compliance program.

  1. Confirm your scope. Identify where account data is stored, processed, and transmitted, and which systems, people, and processes could affect it.
  2. Assess your environment. Test the applicable requirements through examination of evidence, observation, and interviews.
  3. Complete the report. Document the results in a Report on Compliance or the applicable Self-Assessment Questionnaire.
  4. Complete the attestation. Fill out the Attestation of Compliance for merchants or service providers, in its entirety.
  5. Submit your documents. Send the report, attestation, and any requested items, such as ASV scan reports, to the requesting organization.
  6. Remediate if required. Address requirements that are not in place, then provide an updated report.
  7. Repeat and maintain. Keep recurring controls running, reconfirm scope, and prepare for the next assessment.

Step one: define the scope

Accurate scope is the first step in preparing for an assessment. You identify all locations and flows of account data, and every system that connects to the cardholder data environment (CDE). Include systems that could affect the CDE if compromised, along with backup and failover sites.

Requirement 12.5.2 calls for documenting and confirming scope at least once every 12 months and upon significant change. Service providers do this at least once every six months under Requirement 12.5.2.1. Your assessor also validates the scope, and that check is separate from your own confirmation.

Without adequate segmentation, your entire network is in scope. PCI DSS doesn’t require segmentation, but it strongly recommends it as a way to reduce scope, cost, and difficulty.

Step two: assess the controls

The assessment tests whether each applicable requirement is met. Assessors use three methods: examining evidence, observing activities, and interviewing personnel.

The defined approach uses the requirement as written and its listed testing procedures. The customized approach lets an entity design a control to meet the stated objective. Entities completing an SAQ aren’t eligible for it. They may instead have a Qualified Security Assessor (QSA) or Internal Security Assessor (ISA) assess them and document it in a ROC.

A legitimate, documented constraint may prevent you from meeting a requirement as written. You can then use a compensating control, an alternative that meets the requirement’s intent and rigor, documented for assessor review.

Step three: validate the results

The right validation path depends on your payment brand or acquirer. They decide whether you validate at all, and how.

Document What it is Who typically completes it
Report on Compliance (ROC) Detailed results of the assessment A QSA or ISA
Self-Assessment Questionnaire (SAQ) Self-assessment results for a defined environment An eligible merchant or service provider
Attestation of Compliance (AOC) Official form attesting to the results in a ROC or SAQ The assessed entity, with assessor sign-off where one is involved

The Attestation of Compliance

The AOC records one overall status. Compliant means all assessed requirements are In Place or Not Applicable. Non-Compliant means sections are incomplete or a requirement is Not in Place, and it records a target date for compliance.

A third status, Compliant but with Legal exception, applies where a legal restriction prevents a requirement from being met. Official AOC forms are available only on the PCI SSC website.

ASV scans

Requirement 11.3.2 calls for external vulnerability scans at least once every three months by a PCI SSC Approved Scanning Vendor (ASV). You resolve vulnerabilities and rescan as needed until you meet the ASV Program Guide requirements for a passing scan.

Your initial assessment against this requirement doesn’t need four passing scans within 12 months, as long as the assessor verifies three things. The most recent scan passed, your policies require scanning every three months, and a rescan shows corrected vulnerabilities. In later years, passing scans must have occurred at least every three months.

Step four: report to the requesting organization

Merchants submit their documents to the organization managing their compliance program, such as a payment brand or acquirer. Service providers submit to the payment brands, acquirers, or customers that request them. Your requester can tell you what else they need.

PCI SSC doesn’t sit at the end of this chain as an approver. It doesn’t technically approve ROCs, and it reviews them as part of assessor quality assurance. It also doesn’t certify merchants or service providers.

Step five: repeat and maintain

Compliance holds up best when it is part of normal operations. PCI DSS encourages these business-as-usual processes because they help confirm that controls keep working between assessments.

Activity Minimum frequency Requirement
Internal vulnerability scans Every three months 11.3.1
External ASV scans Every three months 11.3.2
Internal and external penetration testing Every 12 months and after significant change 11.4.2, 11.4.3
Segmentation testing Every 12 months and after segmentation changes 11.4.5
Scope confirmation Every 12 months and upon significant change 12.5.2
Monitoring provider compliance status Every 12 months 12.8.4

Service providers have some shorter intervals. For example, segmentation testing under Requirement 11.4.6 runs at least once every six months.

Where to go from here

Now that you know the cycle, you can prepare for your assessment. You can also review what each requirement asks for or see how to keep things running with ongoing maintenance.

Frequently asked questions

What is the difference between a ROC and an SAQ?
Both document the results of a PCI DSS assessment. A Report on Compliance records detailed results and is prepared by a QSA or ISA, while a Self-Assessment Questionnaire documents self-assessment results for eligible entities. Your acquirer or payment brand determines which one you need.
How often does PCI DSS validation happen?
The standard refers to an annual PCI DSS assessment, and payment brands and acquirers set the validation expectations for their programs. Some controls run more often, such as vulnerability scans at least once every three months.
Who signs the Attestation of Compliance?
An executive officer of the assessed merchant signs the merchant attestation. When a QSA is involved, the lead QSA and an authorized officer of the QSA company also sign their acknowledgment.
Is an ASV scan the same as a penetration test?
No. An ASV scan is an external vulnerability scan performed at least once every three months under Requirement 11.3.2. Penetration testing falls under Requirement 11.4 and has its own methodology and frequency.
What happens if an assessment finds a requirement not in place?
You address the open item, and the assessor reassesses to validate that remediation is complete. You then provide an updated report. A control scheduled for a future date doesn’t count as in place.

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

  • PCI DSS v4.0.1 (Section 12, PCI DSS Assessment Process)
  • PCI DSS v4.0.1 (Section 4, Annual PCI DSS Scope Confirmation, and Segmentation)
  • PCI DSS v4.0.1 (Section 10, Testing Methods for PCI DSS Requirements)
  • PCI DSS v4.0.1 (Section 5, Best Practices for Implementing PCI DSS into Business-as-Usual Processes)
  • PCI DSS v4.0.1 (Requirements 11.3.1, 11.3.2, 11.4.2, 11.4.3, 11.4.5, 12.5.2, 12.5.2.1, and 12.8.4)
  • PCI DSS v4.0.1 (Appendix D, Customized Approach)
  • PCI DSS v4.0.1 ROC Attestation of Compliance for Merchants (Section 3, Validation and Attestation Details)
  • PCI DSS v4.0.1 SAQ A r1 (PCI DSS Self-Assessment Completion Steps)
  • PCI QSA Program Guide v4.1 (Sections 2.1 and 2.3, Roles and Responsibilities)

Request a consultation