Regulation & Assurance

PCI DSS: QSA Assessment vs Self-Assessment

Understand PCI DSS assessment options, distinguish SAQ, ROC and AOC, and confirm validation requirements with the entity accepting your submission.

Two assessment folios and separate document sleeves sit beside a payment terminal and inspection lens.
In this article 6 sections
ShareLinkedInWhatsAppEmail

First confirm which validation route and documents the entity accepting your submission requires. Then determine the assessment help appropriate to that route. QSA involvement and document type are separate questions; a decision should start with the applicable requirements and your environment, not a generic company-size shortcut. PCI SSC explains SAQ eligibility and accepting entities. PCI SSC explains SAQ eligibility and accepting entities

What supports a PCI DSS compliance claim?

A PCI DSS compliance statement needs supporting documents and a defined scope. Document type, assessment responsibility and independent assessor involvement are separate questions; they cannot be reduced to a simple certified-or-not comparison.

Self-Assessment Questionnaire vs. Qualified Security Assessor review

An eligible organisation can complete the applicable Self-Assessment Questionnaire (SAQ), with or without assistance from a QSA. The organisation remains responsible for accurate responses and eligibility. Its payment brand, acquirer or other compliance-accepting entity determines the required validation route. PCI SSC FAQ 1215: SAQ eligibility

A Qualified Security Assessor (QSA) is qualified through the PCI Security Standards Council programme and works for a qualified QSA company. Where a Report on Compliance is required, the assessment records testing and findings. QSA assistance can also be used with an SAQ; the document type and the assessor’s involvement are separate questions.

The required validation path depends on applicable payment-brand or acquirer requirements and the organisation’s eligibility. It is not determined by a buyer’s risk appetite alone. Ask the entity accepting the compliance submission which assessment and documentation are required.

What to ask before you accept the claim

Ask which assessment path supports the compliance claim: the applicable SAQ or Report on Compliance, and who performed or assisted with the assessment.

Request the appropriate Attestation of Compliance (AOC), alongside a clear description of the assessed services. Confirm which assessment it accompanies and whether the relevant service, legal entity and assessment period match your purchase.

Ask what is in scope. PCI DSS compliance can be scoped narrowly to a specific system or environment; a vendor can be genuinely compliant for the systems in scope while other parts of their environment are outside it entirely. Define the PCI DSS scope

Match the evidence to the service you rely on

When the claim is about your own organisation, you control the scope and the evidence. When it is about a partner or vendor handling card data on your behalf, you are relying on their attestation being both accurate and current — which is exactly why asking the assessment-path question up front is worth the friction it creates in a vendor conversation. Explore security requirements for financial services

Read the four terms without confusing them

SAQ, ROC, AOC and QSA: what to confirm

SAQ, ROC, AOC and QSA orientation
TermWhat it representsQuestion to resolve
SAQSelf-Assessment QuestionnaireWhich questionnaire, if any, is appropriate and accepted for this environment?
ROCReport on ComplianceIs this reporting route required, and what assessment scope applies?
AOCAttestation of ComplianceWhich assessment, legal entity, service and period does it accompany?
QSAQualified Security AssessorWhat assessor involvement is required or appropriate for the agreed route?

These terms are an orientation aid. Confirm the current documents and instructions with the appropriate accepting entity and the official PCI SSC materials before commissioning work.

Prepare the assessment conversation

Complete this working record before requesting proposals. It is not an eligibility test or a substitute for an official assessment document.

Assessment preparation record
FieldRecord
Entity receiving the submissionOrganisation and responsible contact
Required validationAccepted route and document requirements, with confirmation reference
System/service boundaryEnvironment, relevant data flows, providers and exclusions to clarify
Responsibility splitCustomer, provider and assessor responsibilities to confirm
Evidence ownershipNamed owners and available records
Open decisionUnresolved question, responsible person and next action

Resolve the open questions before treating two assessment quotations as equivalent. Do not infer eligibility from a marketing statement or assume a provider’s evidence covers your whole environment.

Sources and further guidance

Regulatory applicability depends on the organisation and the provisions in force. Check the linked primary sources before acting.

Related reading and capabilities

Frequently asked questions

Can a QSA help with an SAQ?

Yes. Assistance and the required reporting route are separate matters. Confirm the organisation’s eligibility and required documentation first, then agree what help or independent assessment is appropriate.

Does an AOC cover every product sold by a vendor?

No. Read the assessed entity and service scope. Request clarification when your contracted service or deployment model is not clearly included; do not extend the claim using the vendor’s brand name alone.

Who decides whether an SAQ is acceptable?

The compliance-accepting entity, such as a payment brand or acquirer, determines validation requirements. PCI SSC publishes the standards and tools; a buyer’s preference alone does not establish eligibility.