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.
PCI DSS. Cardholder data discovery.
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
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.
The first two columns paraphrase the standard; the third is what IRIS produces, the fourth what the requirement still needs. Capabilities vary by edition.
| Requirement | What the assessor tests | Evidence IRIS produces | What it also needs |
|---|---|---|---|
| Requirement 12.5.2: scope confirmation | You 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 disposal | A 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 unreadable | Full 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: access | Access 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 logs | Audit 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 requirements | No 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. |
How a reviewer labels what a card-number search finds in one merchant’s systems. All values are processor test numbers.
| Value | Detected type | Label | Reason | Kept or rejected |
|---|---|---|---|---|
| 4111 1111 1111 1111 in support_notes.body | Card number | Cardholder data outside the CDE | An agent pasted it into a ticket note; passes the Luhn check | Kept |
| 5555 5555 5555 4444 in orders_export_2022.csv | Card number | Cardholder data in an old export | Compare its age with the retention policy, Requirement 3.2.1 | Kept |
| 4242 4242 4242 4242 in billing.cards.pan | Card number | Cardholder data in plain form | Inside the CDE; Requirement 3.5.1 asks for it to be unreadable | Kept |
| 6011 1111 1111 1117 in dw.payments_raw | Card number | Cardholder data in an analytics warehouse | A system the scope check may have missed | Kept |
| 7788-1001-2203 in orders.ref | Order reference | Not cardholder data | Twelve digits; fails the card-number pattern and the Luhn check | Rejected |
Evidence from IRIS: values that match card-number patterns and pass the Luhn check, by source, table, column and file, with scan dates.
Evidence from IRIS: whether sampled card-number values sit in plain form, by column and scan date.
Evidence from IRIS: where card numbers sit in old tables and exports, by scan date, to compare with your retention periods.
Evidence from IRIS: a scope record of what was scanned, what failed and what was excluded, each with the reason.
Checked on pcisecuritystandards.org on November 9, 2026. Next review on December 7, 2026.
| Item | Status | Source |
|---|---|---|
| PCI DSS v4.0.1 | Current. Published June 2024 as a limited revision, with no added or deleted requirements | PCI SSC blog, June 11, 2024 |
| PCI DSS v4.0 | Retired on December 31, 2024 | PCI SSC blog, June 11, 2024 |
| Future-dated requirements | In effect since March 31, 2025 | PCI SSC blog, August 20, 2024 |
| Review | Editorial review by Sylox; not reviewed by a Qualified Security Assessor | Last reviewed November 9, 2026 |
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 evidenceAn 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.
Find customer and payment-card data, and see who can reach it.
The questions auditors ask across frameworks, with the evidence that answers them.
Repeatable data audit evidence, with scope and gaps on the record.
IRIS maps its evidence to PCI DSS controls through its unified compliance framework. A scored PCI DSS readiness view isn’t in v1; ask us if you need one. Your assessor decides what it proves.
IRIS matches values against card-number patterns and validates them with the Luhn checksum. Stored samples are masked by default, and you can switch sample storage off.
Yes. By the PCI SSC’s definition, systems that store, process or transmit cardholder data are part of the CDE. Decide with your assessor whether to remove the data or bring the system into scope.
IRIS reads the audit log of each supported source and shows who accessed card data and when, where the source keeps one. The source remains the system of record for the log, and IRIS supports the Requirement 10 review without replacing it.
IRIS can be deployed in your own infrastructure, on-premises or in any cloud, so your data stays within your environment. Sylox-hosted environments are used only for demos and agreed pilots.
Pick the database your assessor always asks about. We’ll show you what IRIS finds there, including card numbers.