PCI Assessment or Audit? What Your Report Actually Tells You

Core-Infosec blog illustration

Ask around and you will hear “our PCI audit” used for almost anything: a questionnaire, a scan, a visit from an outside assessor. The word matters, because it shapes what people believe the result proves. This is general information, not advice for your situation.

Two different jobs

An assessment measures your environment against a defined standard. Here the standard is PCI DSS, and the output is a statement of which requirements were in place when the work was done.

An audit, in the strict accounting sense, is a long-running examination that ends in a professional opinion, usually about a full period such as a financial year. The auditor samples evidence across that period and gives assurance about the whole.

A PCI assessment looks much more like the first. Most of the testing is a snapshot: an assessor examines configurations, interviews staff and reviews evidence on or around the assessment dates. Some requirements, such as change records or log review, do look back over time, but the overall result is still a picture of a moment.

The three common formats

  • Report on Compliance (ROC). Written by a Qualified Security Assessor (QSA) or an internal assessor with the right accreditation. It is the most detailed output and records the testing performed.
  • Self-Assessment Questionnaire (SAQ). The organization answers a set of questions matched to how it takes payments. Nobody independent checks the answers unless the acquirer asks.
  • Attestation of Compliance (AOC). The signed summary that goes to acquirers and customers. It is short, so it is only as good as the work behind it.

What a clean report does not tell you

  • That nothing has changed since the assessment. A new payment page, a new vendor or a new office can alter your scope within weeks.
  • That the controls will keep working on a bad day. A control that existed during testing may lapse afterward.
  • That every system was in scope. The report covers the scope that was agreed, and scope mistakes are among the most frequent causes of surprise findings.

Make it a habit, not an event

PCI SSC guidance encourages building the requirements into everyday operations, so that evidence is produced as a side effect of normal work instead of in a rush before the assessor arrives. In practice that means:

1. Keep a current diagram of how card data moves, and review it whenever something changes.

2. Assign an owner to each requirement who checks it on a schedule.

3. Log changes and review them against the scope.

4. Track vendors in the same place, with the date of each attestation you hold.

5. Run mini-reviews between annual assessments so surprises surface early.

PCI DSS v4.0.1 is the current version. It added and removed no requirements compared with v4.0, which was retired on 31 December 2024, and the future-dated requirements became effective on 31 March 2025.

The sensible reading of a PCI report is: “At the time of testing, in the agreed scope, these controls were found in place.” That is useful. It is not the same as an opinion about your security over the whole year, and nobody should present it that way.

See how we help with incident response and security services.

Sources


Discover more from Core-Infosec

Subscribe to get the latest posts sent to your email.

Picture of mweisler

mweisler

Read More