Skip to content

Framework brief · Contractual standard

PCI-DSS is a boundary. Draw it small.

The card brands require it, and your acquirer enforces it. It governs the cardholder data environment — not your culture deck, and not systems that never touch a primary account number.

Current as of November 2026. Operator brief, not legal advice. PCI DSS v4.0.1 is the version referenced here.

All six frameworks

What it is

Not a law. A condition of taking cards.

PCI-DSS is the Payment Card Industry Data Security Standard, maintained by the PCI Security Standards Council. It applies to anyone who stores, processes, or transmits cardholder data, and to service providers who can affect the security of that data. The obligation is contractual. The card brands impose it through the bank that lets you accept cards.

Version 4.0 became the required standard, and v4.0.1 is a limited revision of it — clarification, not a new regime. v4.0 also allows a customized approach: meet the stated objective by a control you design, if you can justify it. That is not a loophole. It is a higher burden of proof, and many teams are better off meeting the defined requirement.

Scope is the strategy. Everything else is a test you may not have needed to take.

Scope

If the number never lands, the standard shrinks.

The cardholder data environment is the people, processes, and technology that store, process, or transmit cardholder data or sensitive authentication data — plus systems connected to those, unless you have actually segmented them.

“Connected” is where companies lie to themselves. A flat network, an admin workstation that can reach the payment zone, a log pipeline that receives the full PAN: those pull systems into scope. Tokenization, a hosted payment field, or a processor that never shares the number with you can keep them out. The design decision is the compliance decision.

Sensitive authentication data — full track data, card verification codes, PINs — is not yours to keep after authorization. Storing it because a debug log was convenient is a finding, not an edge case.

What done looks like

An Attestation of Compliance. How you get there depends on volume and role, and your acquirer tells you which, not a blog post.

  • Higher-volume merchants and many service providers need a Qualified Security Assessor and a Report on Compliance.
  • Others complete a Self-Assessment Questionnaire. There are several SAQs. Picking the short one because it is short, when your architecture does not match it, is a false attestation.
  • Quarterly vulnerability scans by an approved vendor are part of the calendar for many scopes. The attestation is not the end of the year.

Done, commercially, is an acquirer who will keep you in the program. A PDF your marketing team prefers is not the artifact.

What does not cross over

Access control, encryption, logging, and change management rhyme with SOC 2 and with the HIPAA Security Rule. Reuse that evidence where the scope matches. Then stop.

PCI-DSS does not care about PHI, and HIPAA does not care about a primary account number. A company that does both — a health product that also takes cards — has two boundaries. Collapsing them into one “security program” paragraph is how both reviewers send the package back.

It also does not answer GDPR. Cardholder data can be personal data. The card brand’s standard is not a lawful basis, and it is not a transfer mechanism.

What the company has to be able to show

A data-flow that a stranger can read: where the PAN enters, where it is stored, where it is rendered unreadable, where it leaves. The segmentation that keeps the rest of the company out, and the test that proves the segmentation holds. Who administers the payment zone. How long you keep cardholder data, and why that long is defensible.

If you cannot draw the boundary, you do not have a scope. You have a hope. Assessors assess the hope last.

Where Carbon stops

We do not sign the attestation.

If PCI-DSS is a cue, Carbon generates the documentation that describes the boundary, the requirements, and the evidence story — in your environment. It does not produce an Attestation of Compliance, and it does not replace a QSA or your acquirer. HardStack does not claim a PCI validation of its own.

Request a trial

Related briefs