
In this article
Suppose an AI tool checks your access-review folder and reports that the work is complete. It points to a spreadsheet called "Access review". The file exists and contains a list of accounts. But it does not show which systems the reviewer checked, why those people still need access, or whether anyone followed up on accounts that should have been removed.
The summary sounds reassuring. The evidence leaves questions unanswered. If you are preparing for a Payment Card Industry Data Security Standard (PCI DSS) assessment, someone on your team still has to resolve those questions. Asking AI to write a more convincing summary will not resolve them.
AI becomes useful when it helps that person find the records, identify gaps and reach a supported conclusion. We recommend judging AI in PCI DSS preparation by how much it helps the responsible person verify the evidence.
The useful job is to make checking easier
PCI SSC’s 3 November 2026 interview with Shopify offers a practical example. Shopify describes an AI system that flags questionable compliance statements in internal conversations and brings the relevant source passage to a human reviewer. The person decides whether there is a problem and what to do about it.
That approach gives the reviewer something specific to investigate. Instead of searching a long discussion and trying to remember the relevant wording in a standard, they can examine a particular claim alongside its source. Shopify reports benefits from its own implementation; another team would need to test whether a similar approach helps in its environment.
PCI SSC’s interview with Shopify
For a smaller business, the starting point could be much simpler. Choose a repeated task that takes time today, such as locating the records for one access review. Ask the tool to bring the records together, identify their dates and coverage, and show the questions it cannot answer from the material supplied. The result should help the control owner check the work.
Follow one finding back to the records
In this illustrative example, the review should cover three systems in your payment environment, but the spreadsheet contains accounts from only two. Following that gap through to its resolution shows how AI-assisted preparation could work.
Before using the tool, the security team agrees which systems belong in this review and provides that list with the relevant records. If both the spreadsheet and the system list are incomplete, comparing them may reveal no difference. Someone who understands the environment needs to check the starting material.
A useful AI response would say that it found records for two systems and could not find evidence for the third in the supplied material. It would link to the files, identify the gap and leave the conclusion open. That gives the owner a clear next step: look for the missing record and check whether the system was reviewed.
Suppose the owner investigates and confirms that the third system was missed. They arrange the outstanding review, address any access issues it identifies and keep the follow-up linked to the original gap. They also correct the initial claim that the review was complete. A review performed today does not show that it happened earlier; the record should reflect what occurred.
The team now has a record of the omission, the follow-up and the outcome. It can explain what was missing and what happened next. That resolves a specific evidence question; it does not establish the organisation’s overall PCI DSS compliance, which requires the applicable assessment work.
Source links alone do not make an AI answer reliable. NIST’s Generative AI Profile describes how a model can confidently generate false information, including misleading explanations or citations. Open the original record and check whether it supports the conclusion.
NIST on confidently stated errors, section 2.2
Make the human decision visible
Keep a record of the human review, too. A status marked "approved" identifies an action, but it may leave the next person unable to tell what was checked or why the finding was accepted.
A discussion in r/Compliance raises this concern about evidence of human review. Some contributors suggest tracking time spent on a page. Others explain why that can mislead: an open screen does not establish understanding, and a quick decision is not necessarily careless. These are practitioner views, not PCI SSC guidance.
The practitioner discussion about review records
For the access-review example, we recommend retaining a short record that lets someone else follow the decision. It should keep the original AI output, the evidence the owner checked, who made the decision and when, and the reason for accepting, correcting or escalating the finding. Link any follow-up to that record. Use enough detail to explain the work without creating another report nobody has time to maintain.
The owner needs time and authority to investigate a finding, even when it delays assessment preparation. If a missing record is dismissed to meet a deadline, an approval button adds little. The reviewer must be able to ask for more information and leave the issue unresolved when the evidence is insufficient.
For formal assessment work, PCI SSC’s March 2025 guidance announcement is clear that human assessors retain responsibility for findings and final decisions. A tool can help prepare material for an assessor; a team’s internal approval of that material does not replace the assessor’s judgment.
PCI SSC on using AI during assessments
Count time spent checking and correcting
Checking AI output can cancel the time saved in producing it. Finding scattered files and drawing attention to a missing system may save effort. Producing vague warnings that all need investigation may add work. A pilot needs to distinguish between those results.
Test a small set of records that your team has already checked. Include a complete example, a known omission and a case where the supplied information is insufficient. Compare the AI-assisted process with the way you currently do the work. Count the time spent locating records, checking answers, correcting mistakes and following up. Also record problems the tool misses; a fast answer that overlooks the missing system is not a good result.
A successful pilot should help the reviewer reach a supported conclusion with less avoidable work. If the tool struggles, narrow its task. It may be useful for finding and organising files even when its interpretation of them is unreliable. If checking its output costs more effort than it saves, there is little reason to expand that use.
Start with one task you can control
Before a pilot, agree what information the tool may receive and who may access the output. Assessment material can contain sensitive details about accounts, systems and security settings. Check the tool’s storage and retention arrangements before supplying it. PCI SSC’s assessment guidance announcement also highlights informing clients about AI use, obtaining consent and handling their data securely.
Keep the first task limited to reviewing approved material, with no automatic changes to production systems. If the proposed tool needs access to payment data or connections to the payment environment, review those data flows and access arrangements with the people responsible for assessment scope before proceeding. PCI SSC’s September 2026 AI guidance announcement says AI should be considered like other technology when determining the PCI requirements that apply. It describes the supplement as guidance, not new mandatory requirements.
PCI SSC on AI deployment and applicable requirements
A practical first pilot is one evidence pack, one clear question and a named reviewer. Agree what a useful answer would contain before running it: the relevant records, the gap they leave and the follow-up needed. Then work through the result together. Expand the tool’s role only when that exercise shows it helps the person responsible make a better-supported decision.
Prepare your evidence for review
443 Labs can help you review a proposed AI-assisted evidence workflow, clarify the assessment scope and identify the records your team needs to support its conclusions.
Get in TouchRelated Services















