trio.so
Explained

PCI Compliance Audit: How a PCI DSS Audit Works (v4.0.1)

PCI compliance audit guide for PCI DSS v4.0.1: QSA, ISA or SAQ, ROC vs AOC, ASV scans, pen tests, the evidence auditors ask for and how to prepare.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A PCI compliance audit is the yearly check that your business protects card data the way PCI DSS requires. The standard itself calls it an assessment. Depending on your size and how you take payments, a Qualified Security Assessor (QSA) audits you and writes a Report on Compliance (ROC), or your own team completes a Self-Assessment Questionnaire (SAQ). Either way, you sign an Attestation of Compliance (AOC) and send it to your acquiring bank.

This guide covers who audits whom under PCI DSS v4.0.1, the documents an audit produces, the scans and penetration tests behind it, the evidence assessors ask for under each of the 12 requirements, and how to prepare.

TL;DR

In short

  • A PCI audit ends in a ROC written by a QSA or ISA, or an SAQ you complete yourself, plus a signed AOC. There is no PCI certificate.
  • The card brands and your acquirer decide which route you take. Visa, for example, asks for a QSA-led ROC from merchants with over 6 million Visa transactions a year.
  • Quarterly internal scans, quarterly external scans by an Approved Scanning Vendor (ASV) and yearly penetration tests apply when they are in your SAQ or ROC scope.
  • PCI DSS v4.0.1 is the current version. The 51 requirements that were future-dated have been mandatory since 31 March 2025, so check them first.

What Is a PCI Compliance Audit?

PCI DSS is published by the PCI Security Standards Council (PCI SSC), founded by American Express, Discover, JCB International, Mastercard and Visa. It applies to any business that stores, processes or transmits cardholder data, or could affect its security (PCI SSC). A PCI audit checks whether the controls it asks for are in place in your cardholder data environment (CDE): the people, processes and systems that handle card data, plus the systems connected to them.

PCI SSC doesn't audit anyone or enforce the standard. Each card brand runs its own compliance program and decides who validates and how, usually through your acquiring bank (PCI SSC FAQ 1212).

Three points trip people up:

  • There is no PCI certification. A completed assessment produces a ROC or SAQ and an AOC on PCI SSC's official templates. PCI SSC issues no seal or logo, and it warns that third-party "compliance certificates" are not accepted as proof (PCI SSC).
  • Validation is yearly, and the result describes your controls at the time they were assessed. A control you plan to add later counts as not in place.
  • The audit covers every applicable requirement in PCI DSS v4.0.1, including the ones that were future-dated until 31 March 2025.

Who Performs a PCI DSS Audit: QSA, ISA or Self-Assessment

Four roles show up in a PCI DSS audit. PCI SSC publishes the lists of QSA companies and ASVs on its website (PCI SSC listings).

RoleWho they areWhat they produce
Qualified Security Assessor (QSA)An independent assessor company qualified by PCI SSC; usually what people mean by a PCI compliance auditorThe ROC and the assessor's sections of the AOC
Internal Security Assessor (ISA)One of your own employees, trained and qualified by PCI SSCYour assessment, where your acquirer or card brand accepts an ISA
Your own teamWhoever owns PCI DSS at your companyAn SAQ and AOC, if you are eligible to self-assess
Approved Scanning Vendor (ASV)A scanning company on PCI SSC's ASV listQuarterly external vulnerability scans only

Which route you take depends on your merchant level, which each card brand defines; PCI DSS doesn't. Visa expects an annual ROC by a QSA from Level 1 merchants, with over 6 million Visa transactions a year, and an SAQ from Levels 2 and 3, all three with quarterly ASV scans. For Level 4, under 20,000 e-commerce transactions and other merchants up to 1 million, Visa recommends an SAQ and leaves the rules to the acquirer (Visa). Service providers handling more than 300,000 Visa transactions a year need a QSA-led ROC too.

Mastercard, American Express, Discover and JCB set their own levels, and your acquirer decides how its program applies to you, so ask it in writing. For levels and SAQ types from a smaller merchant's point of view, see PCI compliance for small business.

ROC vs SAQ vs AOC

Every PCI audit ends in paperwork on PCI SSC's templates, and the three names get mixed up.

DocumentWho completes itWhat it is
Report on Compliance (ROC)A QSA, or an ISA where allowedThe full assessment report, written on PCI SSC's mandatory ROC Template. It records how each requirement was tested and what the assessor found.
Self-Assessment Questionnaire (SAQ)YouA questionnaire for businesses that are eligible to self-assess. Each type (A, A-EP, B, B-IP, C, C-VT, P2PE, SPoC, D) fits one payment setup and lists only the requirements that apply to it.
Attestation of Compliance (AOC)You, plus the QSA or ISA if one assessed youThe signed statement of your compliance status. It goes to your acquirer or the card brand with the ROC or SAQ and any ASV scan reports.

The PCI DSS attestation of compliance comes in a merchant and a service provider version, and the official forms are available only from the PCI SSC website (Document Library). PCI DSS doesn't treat the AOC as sensitive, so service providers share theirs with customers. Requirement 12.8.4 asks you to check your service providers' PCI DSS status at least every 12 months, and their AOC is the usual way to do it.

Two ways to validate PCI DSS: a ROC by a QSA or ISA, or an SAQ completed by your team, both ending in a signed AOC
Two ways to validate PCI DSS: a ROC by a QSA or ISA, or an SAQ completed by your team, both ending in a signed AOC

PCI ASV Scans, Internal Scans and Penetration Tests

Requirement 11 sets the testing that runs between assessments, and your assessor will want results from across the year.

TestRequirementHow oftenWho runs it
Internal vulnerability scans11.3.1At least every three months; high-risk and critical findings fixed and rescannedYour team or a provider. Scans must be authenticated (11.3.1.2).
External vulnerability scans11.3.2At least every three months, with a passing resultAn ASV
Penetration tests, internal and external11.4.2, 11.4.3At least every 12 months and after significant changesA qualified tester who is organizationally independent; not necessarily a QSA or ASV
Segmentation tests11.4.5Every 12 months and after changes, if segmentation reduces your scope (every six months for service providers)As for penetration tests

A PCI ASV scan is an external scan of your internet-facing systems by a company on PCI SSC's ASV list. It has to pass under the ASV Program Guide's rules, so you fix findings and rescan until it does. After a significant change you scan again, and that rescan can be done by qualified, independent staff instead of an ASV (11.3.2.1). Which tests apply depends on your SAQ or ROC scope: SAQ D covers every requirement, penetration testing included, while shorter SAQs leave out tests that don't fit their payment setup.

The PCI DSS year: daily log review, quarterly internal and ASV scans, six-monthly account reviews and yearly penetration tests, scope confirmation, risk analysis reviews, training and service provider checks
The PCI DSS year: daily log review, quarterly internal and ASV scans, six-monthly account reviews and yearly penetration tests, scope confirmation, risk analysis reviews, training and service provider checks

PCI Audit Requirements: What Assessors Ask for in v4.0.1

PCI DSS v4.0.1 groups 12 principal requirements under six goals, and an assessor works through every one that applies to you. If your audit checklist still names "firewall configuration" or "anti-virus software" as requirements, it was written for v3.2.1, which was retired on 31 March 2024. v4.0 was retired on 31 December 2024, and v4.0.1, published in June 2024, is the only active version (PCI SSC).

No.RequirementEvidence an assessor typically asks for
1Install and Maintain Network Security ControlsNetwork and card data flow diagrams, rule sets, records of rule reviews
2Apply Secure Configurations to All System ComponentsConfiguration standards per system type, changed vendor defaults, settings on sampled systems
3Protect Stored Account DataRetention policy, where card numbers (PAN) are stored and how they are made unreadable, key management
4Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public NetworksEncryption settings for data in transit, the inventory of trusted keys and certificates (4.2.1.1)
5Protect All Systems and Networks from Malicious SoftwareAnti-malware coverage and updates, anti-phishing controls (5.4.1)
6Develop and Maintain Secure Systems and SoftwareCritical patches within one month (6.3.3), custom software records, payment-page script inventory (6.4.3)
7Restrict Access to System Components and Cardholder Data by Business Need to KnowAccess policy, role definitions, six-monthly account reviews (7.2.4)
8Identify Users and Authenticate Access to System ComponentsUnique IDs, 12-character passwords (8.3.6), MFA into the CDE (8.4.2), inactive accounts removed within 90 days
9Restrict Physical Access to Cardholder DataVisitor and media records, the list and inspection log of card-reading devices (9.5.1)
10Log and Monitor All Access to System Components and Cardholder DataDaily log reviews, automated review (10.4.1.1), 12 months of logs with three immediately available
11Test Security of Systems and Networks RegularlyA year of internal and ASV scans, penetration test reports, payment-page change detection (11.6.1)
12Support Information Security with Organizational Policies and ProgramsPolicy, targeted risk analyses (12.3.1), scope confirmation (12.5.2), training, service providers, incident response plan

In v4, the first section of every requirement (1.1, 2.1 and so on) asks for documented policies, procedures and roles, so expect to show those for all 12. For every sub-requirement as a working list, use our PCI compliance checklist.

How to Prepare for a PCI DSS Audit

PCI DSS doesn't set a length for the assessment itself. The yearly cycle is fixed, though: scope confirmation, four quarters of scans and a yearly penetration test have to fit inside it, so start the gap assessment months before your AOC is due.

How to prepare for a PCI DSS audit: confirm scope, confirm the validation path, gap assessment, fix gaps, collect evidence, readiness review, assessment, report and attest
How to prepare for a PCI DSS audit: confirm scope, confirm the validation path, gap assessment, fix gaps, collect evidence, readiness review, assessment, report and attest

Step 1: Confirm Your Scope

Map where card data enters, moves and is stored, and list every system in or connected to the CDE. Requirement 12.5.2 asks you to confirm scope at least every 12 months and after significant changes (every six months for service providers, 12.5.2.1). Tokenization, P2PE terminals and hosted payment pages keep card data off your systems, and shrinking scope usually saves more than anything else.

Step 2: Confirm How You Validate

Ask your acquirer whether you need a ROC or an SAQ, which SAQ type, and when the AOC is due. If a QSA will assess you, agree on dates and evidence format early.

Step 3: Run a Gap Assessment

Mark every applicable requirement in place, not in place or not applicable. PCI SSC's free Prioritized Approach tool sorts the requirements into six milestones if you need an order to work in (FAQ 1170).

Step 4: Fix the Gaps

Start with card data you store but don't need, then the future-dated requirements below. A control that is scheduled but not yet running counts as not in place.

Step 5: Collect Evidence All Year

Scan reports, log and access reviews, training records and policy approvals all carry dates. File them by requirement number as you go.

Step 6: Do a Readiness Review

Ask your QSA whether it offers one. Otherwise, have someone who didn't build a control try to show it working from the evidence alone.

Step 7: The Assessment

The assessor reviews documents and settings, interviews the people who run each control and samples systems and locations. Keep each requirement's owner on hand.

Step 8: Report and Attest

The QSA writes the ROC, or you complete the SAQ. The signed AOC goes to your acquirer with any ASV scan reports.

Common PCI Audit Findings in v4.0.1

PCI DSS v4.0 added 64 new requirements. 13 applied straight away, and the other 51 were best practice until 31 March 2025; since then they count in every assessment (Summary of Changes). v4.0.1 only clarified wording. A program built for v3.2.1 will usually have gaps here:

  • Targeted risk analyses (12.3.1): a written justification, reviewed every 12 months, wherever a requirement lets you pick how often to do something.
  • MFA for all non-console access into the CDE (8.4.2), beyond administrators and remote access. A v4.0.1 note exempts accounts that sign in only with phishing-resistant factors.
  • Passwords of at least 12 characters (8.3.6), or 8 where a system can't support 12. The old minimum was 7.
  • Payment-page scripts (6.4.3) and change detection on payment pages (11.6.1). The January 2025 SAQ A revision took both out of SAQ A in exchange for a new eligibility criterion; they still apply everywhere else (PCI SSC).
  • Automated mechanisms against phishing (5.4.1), and training that covers phishing and social engineering (12.6.3.1).
  • Automated log reviews (10.4.1.1) and authenticated internal scans (11.3.1.2).
  • Disk encryption used to protect stored card numbers (3.5.1.2). Full-disk encryption on its own is now acceptable only on removable media.
  • Reviews of all user accounts, including vendor accounts, every six months (7.2.4).

Check two older problems at the same time: a CDE that has grown since the scope was last written down, and evidence that covers one quarter but not the other three.

After the Audit

If every applicable requirement is in place, the signed AOC goes to your acquirer or the card brand with the ROC or SAQ and any ASV reports. If something isn't in place, you have options before the report is final:

  • Fix it and give the assessor the evidence.
  • Use a compensating control, if a legitimate technical or documented business constraint stops you from following the requirement as written. Compensating controls exist only under the defined approach.
  • Design your own control under the customized approach, aimed at the requirement's stated objective. It needs a targeted risk analysis for each requirement (12.3.2) and a QSA or ISA; SAQ users can't use it.
  • Report the requirement as not in place. Your AOC then shows that you are not in compliance, and your acquirer decides what happens next.

Consequences come from the card brands and your merchant agreement, not from PCI SSC. Its guide for small merchants lists financial penalties, lawsuits and losing the ability to accept cards as possible outcomes after a breach (Guide to Safe Payments). Then the cycle starts again, and next year's assessor will ask for the same evidence.

Where trio.so Fits

Assessors sample the laptops, desktops and phones in scope, and each one has to match your configuration standard. trio.so is device management software that enforces and reports those device settings on Windows, Mac, iOS and Android from one console:

See how trio.so handles the device side of PCI DSS, area by area, with the evidence you can show your assessor.

  • A compliance engine with PCI DSS among its frameworks. It checks device settings against the framework's device controls and shows compliance status for each device.
  • Encryption: BitLocker on Windows and FileVault on Mac, with FileVault recovery key escrow, plus encryption on iOS and Android phones, with encryption status shown per device. Requirement 3.5.1.2 says full-disk encryption alone does not make stored card numbers unreadable on a laptop or desktop drive, so keep PAN off endpoints or protect it another way as well.
  • Passcode and screen-lock policies, part of the device configuration standards that Requirement 2.2 asks for.
  • OS update management on Windows, macOS, iOS and Android, which helps you keep to the patch deadlines in Requirement 6.3.3.
  • App allow and block lists, so in-scope devices carry only the software you approved (Requirements 2.2 and 12.2.1).
  • Device inventory, including installed apps, for the in-scope system component inventory in Requirement 12.5.1.
  • Lock for lost Macs, iPhones and Android devices, and wipe for company-owned devices.
  • Evidence export, so device status goes to your assessor or into your SAQ file as a dated record.

trio.so does not assess, certify or validate PCI DSS compliance, and PCI SSC is clear that no single product can make an organization compliant (FAQ 1258). Your QSA, ISA or SAQ process validates compliance. Network security controls, logging, vulnerability scans, MFA, anti-malware and payment-page scripts need other tools and processes. Learn more about compliance automation.

Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

For related work, see vulnerability management, third-party risk management and device encryption.

Sources. Last reviewed October 2026, against PCI DSS v4.0.1 (June 2024), the current version on 26 October 2026. This article is guidance, not legal or assessment advice; your acquirer, card brand and assessor have the final word. PCI DSS is © PCI Security Standards Council, LLC. Requirement numbers and titles are used for reference; descriptions are our own paraphrase. trio.so is not affiliated with or endorsed by PCI SSC.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

A PCI compliance audit, formally a PCI DSS assessment, checks whether a business that handles payment cards has the controls PCI DSS v4.0.1 requires. It ends in a Report on Compliance written by a QSA or ISA, or a Self-Assessment Questionnaire, plus a signed Attestation of Compliance that goes to the acquiring bank.

No. PCI SSC does not certify merchants or service providers and issues no compliance seal or logo. What you get is a ROC or SAQ and an AOC on PCI SSC's official templates, and you validate again every year.

Merchants and service providers whose card brand or acquirer requires a Report on Compliance, which usually means the largest ones. Visa, for example, expects a QSA-led ROC from merchants with more than 6 million Visa transactions a year and from service providers with more than 300,000. Smaller businesses usually self-assess with an SAQ.

The Attestation of Compliance (AOC) is a signed PCI SSC form in which a merchant or service provider declares its PCI DSS compliance status. It accompanies the ROC or SAQ and any ASV scan reports, and service providers share it with customers as proof of their status.

At least once every three months under Requirement 11.3.2, when external scanning is in your SAQ or ROC scope. A PCI SSC Approved Scanning Vendor runs the scan, and you fix findings and rescan until it passes. Internal scans are also due every three months (11.3.1).

Yes, where Requirement 11.4 is in your scope. Internal and external penetration tests are due at least every 12 months and after significant changes, run by a qualified tester who is organizationally independent. The tester doesn't have to be a QSA or ASV.

Validation is annual under the card brands' programs. Your ROC or SAQ and AOC describe your controls at the time of the assessment, so the controls have to keep running and you validate again the following year.

PCI DSS has no overall grade: each requirement is either in place or not. You can fix gaps before the report is final, use compensating controls where allowed, or report the requirement as not in place, in which case your acquirer decides what happens next.

Related

From the blog

The related industry news, interviews, technologies, and resources.