Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

PCI DSS. Cardholder data discovery.

PCI DSS v4.0.1: find card numbers outside the cardholder data environment

Requirement 12.5.2: confirm scope each year, including account data outside the CDE. IRIS shows where card numbers sit in connected sources, by scan date.

By Dipal Panchal, co-founder and CEO · Last reviewed: November 9, 2026

Overview

Who PCI DSS applies to, and which version

The Payment Card Industry Data Security Standard (PCI DSS) applies to entities that store, process or transmit cardholder data or sensitive authentication data. It also applies to those that could affect the security of the cardholder data environment (CDE). That covers merchants, processors, acquirers, issuers and service providers (PCI SSC).

The current version is PCI DSS v4.0.1, a limited revision the PCI Security Standards Council (PCI SSC) published in June 2024 with no added or deleted requirements. Version 4.0 was retired on December 31, 2024, and the requirements that v4.0 future-dated took effect on March 31, 2025.

Cardholder data is at least the full primary account number (PAN). Qualified Security Assessor companies, or Internal Security Assessors inside an organization, carry out assessments; the PCI SSC qualifies both. This page is general information, not professional advice.

  • Applies to merchants, processors, acquirers, issuers and service providers
  • The CDE includes systems that store, process or transmit account data
  • It also includes systems with unrestricted connectivity to those
  • NCA ECC and SAMA CSF aren’t covered on this page
Requirements

What the assessor tests, and the evidence

The first two columns paraphrase the standard; the third is what IRIS produces, the fourth what the requirement still needs. Capabilities vary by edition.

What the assessor tests, and the evidence
RequirementWhat the assessor testsEvidence IRIS producesWhat it also needs
Requirement 12.5.2: scope confirmationYou document and confirm scope every 12 months and on significant change, including account data outside the CDE.Discovery supports it: values matching card-number patterns and the Luhn check, by source, table, column and file.Data-flow diagrams, segmentation, third-party links. A card number outside the CDE is an assessor scope question.
Requirement 3.2.1: retention and disposalA policy limiting retention of stored account data to business, legal or regulatory need, checked every three months.Supports the check: where card numbers sit, including old tables and exports, by scan date, against retention periods.The policy, its retention periods and the deletion process. A later scan records whether the data is still there.
Requirement 3.5.1: stored card numbers unreadableFull card number unreadable wherever stored: hashed, truncated, index tokens or strong cryptography with key management.Checks sampled sensitive-column values for encryption, masking, hashing or plain form, once activated on your install.Applying the protection and managing the keys. IRIS detects protection and doesn’t apply it.
Requirements 7.2.1, 7.2.2 and 7.2.4: accessAccess follows job function and least privileges, and accounts and privileges are reviewed at least every six months.Access mapping shows who can reach sensitive data where the source exposes permissions. Reviewers record each decision.The review, on your schedule. Scheduled campaigns and reminders aren’t in v1. IRIS doesn’t grant or revoke access.
Requirements 10.2.1 and 10.2.1.1: audit logsAudit logs are enabled and active, and capture all individual user access to cardholder data.Supports the review. Where a supported source keeps an audit log, IRIS shows who accessed card data and when.The logging itself, kept by the source system or your logging tool. IRIS doesn’t replace it.
Requirement 3.3.1 and the other requirementsNo sensitive authentication data kept after authorization, and the controls in the remaining requirements.Not mapped here. This page covers card numbers found by pattern and Luhn check. Ask us about anything beyond that.Network, configuration, transmission, malware, software, authentication, physical and testing evidence from your tools.

Five values, sorted for a scope check

How a reviewer labels what a card-number search finds in one merchant’s systems. All values are processor test numbers.

Records
ValueDetected typeLabelReasonKept or rejected
4111 1111 1111 1111 in support_notes.bodyCard numberCardholder data outside the CDEAn agent pasted it into a ticket note; passes the Luhn checkKept
5555 5555 5555 4444 in orders_export_2022.csvCard numberCardholder data in an old exportCompare its age with the retention policy, Requirement 3.2.1Kept
4242 4242 4242 4242 in billing.cards.panCard numberCardholder data in plain formInside the CDE; Requirement 3.5.1 asks for it to be unreadableKept
6011 1111 1111 1117 in dw.payments_rawCard numberCardholder data in an analytics warehouseA system the scope check may have missedKept
7788-1001-2203 in orders.refOrder referenceNot cardholder dataTwelve digits; fails the card-number pattern and the Luhn checkRejected
Questions

Questions assessors ask about card data

Where are card numbers stored?

Evidence from IRIS: values that match card-number patterns and pass the Luhn check, by source, table, column and file, with scan dates.

Are they stored in plain form?

Evidence from IRIS: whether sampled card-number values sit in plain form, by column and scan date.

Is any kept past your policy?

Evidence from IRIS: where card numbers sit in old tables and exports, by scan date, to compare with your retention periods.

What did your scope check miss?

Evidence from IRIS: a scope record of what was scanned, what failed and what was excluded, each with the reason.

Timeline

Status on November 9, 2026

Checked on pcisecuritystandards.org on November 9, 2026. Next review on December 7, 2026.

Status on November 9, 2026
ItemStatusSource
PCI DSS v4.0.1Current. Published June 2024 as a limited revision, with no added or deleted requirementsPCI SSC blog, June 11, 2024
PCI DSS v4.0Retired on December 31, 2024PCI SSC blog, June 11, 2024
Future-dated requirementsIn effect since March 31, 2025PCI SSC blog, August 20, 2024
ReviewEditorial review by Sylox; not reviewed by a Qualified Security AssessorLast reviewed November 9, 2026
With IRIS

IRIS produces evidence for these rows and maps it to PCI DSS controls; it doesn’t certify compliance. Mapping shows relevance; your auditors judge whether a control is met.

Requirement 12.5.2: where card numbers sit, by scan date: IRIS produces part of this, for the sources you connect; the data types IRIS detects.

Requirement 3.5.1: whether stored values are in plain form: IRIS produces part of this, on sampled values, once the check is activated on your install.

Requirement 7.2.1: who can reach the data: IRIS produces part of this, where the source exposes permission data.

Requirement 10.2.1.1: who accessed card data, and when: IRIS produces part of this, where the source keeps an audit log.

What each scan covered and couldn’t read: IRIS produces this.

Whether a requirement is met: Not produced by IRIS.

Explore evidence

Run the annual scope check on the data itself

An order of work we recommend; PCI DSS sets none. Requirement 12.5.2 asks for the confirmation, and your assessor does a separate scoping check.

1. List where you expect card numbers

Owner
Security lead
Tool or path
Your current scope document and data-flow diagrams
Expected output
The systems you already treat as the CDE, each with an owner.
How to verify
Every system in the diagrams is on the list, with a reason if it is out of scope.

2. Search every other store for card numbers

Owner
Data platform lead
Tool or path
A discovery scan, or pattern and Luhn queries run by each system’s administrator
Expected output
Tables, files and exports that hold values passing the card-number pattern and the Luhn check.
How to verify
The scan record names each source scanned, failed or excluded, with the reason.

3. Decide what to do with each find

Owner
Security lead and assessor
Tool or path
The findings, read against your retention policy
Expected output
Each find marked delete, protect or bring into scope.
How to verify
Each decision names its owner and a date.

4. Scan again after the change

Owner
Data platform lead
Tool or path
A second scan of the same scope
Expected output
The new state beside the first scan, with both dates.
How to verify
Deleted values are gone from the later scan; anything left has a decision.

The official texts behind each cell

  1. PCI Data Security Standard: who it applies to, PCI Security Standards Council. Opened November 9, 2026.
  2. PCI SSC document library: PCI DSS v4.0.1 listed as current, PCI Security Standards Council. Opened November 9, 2026.
  3. Just published: PCI DSS v4.0.1 (June 11, 2024), PCI Security Standards Council. Opened November 9, 2026.
  4. Now is the time to adopt the future-dated requirements (August 20, 2024), PCI Security Standards Council. Opened November 9, 2026.
  5. FAQ 1318: maximum period cardholder data can be stored, PCI Security Standards Council. Opened November 9, 2026.
  6. PCI SSC glossary: account data, cardholder data, CDE, PAN, least privileges, PCI Security Standards Council. Opened November 9, 2026.
  7. SAQ D for service providers, v4.0 (April 2022): the requirement text this page paraphrases, PCI Security Standards Council. Opened November 9, 2026.
FAQ

PCI DSS questions

Protect your brand. Start with your data.

Pick the database your assessor always asks about. We’ll show you what IRIS finds there, including card numbers.