Why Manual Infrastructure Cannot Pass a PCI Audit
NIST calls manual configuration tracking an almost impossible task. PCI DSS v4.0 now requires the specific things that task cannot reliably produce.

- PCI DSS v4.0 Requirement 10.4.1.1 requires audit log reviews to be automated. It became mandatory on March 31, 2025, after three years as an optional best practice, and a manual log review process no longer satisfies it regardless of how diligently someone performs it.
- Requirement 6.3.2 requires a maintained inventory of bespoke and custom software, and Requirement 4.2.1.1 requires a maintained inventory of trusted keys and certificates. Both are specifically the kind of continuously accurate artifact NIST's own configuration management guidance says manual methods cannot reliably sustain.
- NIST Special Publication 800-128 states directly that managing configurations across system components using manual methods like spreadsheets has become an almost impossible task, and that it is impractical for most organizations to manually collect accurate inventory information at any real scale.
- A business that relies on tribal knowledge, spreadsheets, and periodic manual reviews is not failing these PCI DSS requirements through carelessness. It is attempting a task the standard's own underlying assumptions, and NIST's own guidance, both say manual methods cannot reliably do.
Why manual infrastructure cannot pass a PCI audit comes down to a mismatch between what the standard now requires and what a manual process is actually capable of sustaining. PCI DSS version 4.0 added specific requirements for automated audit log review and continuously maintained inventories, both of which became mandatory on March 31, 2025. NIST’s own federal guidance on configuration management states plainly that manual methods cannot reliably do either one at any real scale. A business relying on manual processes is not failing these requirements through negligence. It is attempting something the standard and the research behind it both say manual methods were never built to do.
The requirement that specifically rules out manual review
PCI DSS v4.0’s Requirement 10.4.1.1 does not ask for log reviews to happen regularly, or for someone qualified to perform them. It requires that audit log reviews be automated. This was introduced as an optional best practice when v4.0 first published, with a grace period running through March 31, 2025. That grace period has closed. The requirement is now mandatory, and a manual review process, however consistent and well-documented, does not satisfy a requirement that specifically asks for automation.
The standard goes a step further in a related provision. It adds a requirement to detect, alert, and report failures of the automated log review mechanism itself. That bullet only makes sense if automation is already the baseline. A business whose log review is still manual has not just failed to automate a nice-to-have. It has skipped a requirement the standard assumes is already satisfied before the next one can even apply.
Why two separate inventory requirements point at the same gap
PCI DSS v4.0 added two inventory requirements that look unrelated on the surface but share the same underlying demand. Requirement 6.3.2 requires a maintained inventory of bespoke and custom software, specifically to support vulnerability and patch management. Requirement 4.2.1.1 requires a maintained inventory of trusted keys and certificates. Both became mandatory on the same March 31, 2025 date as the automated log review requirement.
Neither requirement asks for a one-time list. Both ask for an inventory that stays accurate as the environment changes, every time a developer ships new custom code or a certificate gets issued, rotated, or retired. That is precisely the kind of artifact a manual process struggles to keep current, because manual inventory tracking depends entirely on someone remembering to update a document every time something changes, across every team and every system, without exception, indefinitely.
What NIST’s own guidance says about this exact problem
This is not a judgment call specific to payments or to PCI DSS. NIST Special Publication 800-128, the federal government’s own guidance on security-focused configuration management, addresses the general version of this problem directly. It states that managing the configurations found within system components using manual methods like spreadsheets has become an almost impossible task, and that organizations should look for automated solutions instead, which lower costs, improve efficiency, and improve reliability over the long run.
The same publication makes the point even more specifically about inventories. Discovery, the process of finding and recording what components actually exist in an environment, can be manual or automated, but NIST states plainly that in most organizations, it is impractical to manually collect this information accurately enough to analyze against the organization’s own authorized inventory. The use of automated tools for discovery and inventory management is described as the generally more effective and efficient approach, not as one option among equals.
Read against PCI DSS’s own new inventory requirements, this is not a coincidence. The standard is asking for exactly the kind of continuously accurate artifact that federal configuration management guidance says manual methods cannot reliably produce at scale.
NIST’s guidance adds one more detail worth noting, because it keeps the point honest rather than overstating it. Even with automated inventory management tools in place, some data elements still have to be entered manually: things like which team owns a component, or how a configuration item relates to the rest of the system. Automation does not eliminate every manual step entirely. It eliminates the part that manual methods are worst at, continuously detecting what actually exists and keeping that record synchronized with reality as the environment changes, while leaving the small amount of genuinely judgment-based data entry to a person.
A concrete example: the certificate nobody remembered
Picture a payments platform that tracks its TLS certificates and API keys in a shared spreadsheet, updated whenever someone remembers to add a row after provisioning a new one. The spreadsheet works fine for the first year, when the infrastructure is small enough that one engineer can reasonably hold most of it in their head as a backup to the document.
Two years and several new services later, long after the one engineer who kept most of the real picture in their head has moved to a different team, a certificate issued for an internal service that nobody uses much anymore quietly expires. Nobody notices immediately, because the spreadsheet was never updated when that certificate was issued in the first place, three engineering hires ago. The expiration causes an intermittent authentication failure between two internal systems that takes a support engineer most of a day to trace back to its actual cause, because the one artifact that should have made the cause obvious in minutes, a current certificate inventory, did not reflect reality. A PCI assessor asking to see the maintained inventory required under 4.2.1.1 would have found the same gap immediately, without needing an incident to surface it first.
What an assessor actually checks, and why a spreadsheet fails the test
A PCI DSS assessment does not take a business’s word that an inventory or a log review process exists. An assessor asks to see the artifact itself and tests whether it reflects current reality, not whether a policy document describes the right intention. For the log review requirement, that means asking how review actually happens today, who or what performs it, and what evidence exists that it ran on schedule rather than being described as a practice nobody can actually point to in a system.
For the inventory requirements, the test is more direct still. An assessor can pick a system component at random and ask whether it appears in the inventory, correctly described, with no update lag. A spreadsheet-based inventory almost always fails this specific test somewhere, not because the team is careless, but because the spreadsheet only reflects whatever was true the last time someone remembered to open it and make an edit. The gap between that last edit and the present moment is exactly where an assessor’s sample check lands, and it is exactly where a manual process has no way to guarantee it is still accurate.
This is also why a passing assessment one year does not guarantee a passing assessment the next. A manual inventory that happened to be reasonably current during one assessment cycle can drift substantially by the next one, as more changes accumulate between the moments anyone actually looked at it. An automated system does not have this problem in the same way, because the inventory is generated from the actual state of the infrastructure every time it is queried, rather than from whatever was true the last time a person updated a document.
Why this is a modernization decision, not a documentation fix
The instinct when an assessor flags a missing or stale inventory is often to assign someone to update the spreadsheet and commit to reviewing it more diligently going forward. That response treats the finding as a discipline problem rather than what NIST’s own guidance says it actually is: a structural mismatch between a manual process and a task that has outgrown what manual methods can sustain. A renewed commitment to updating a spreadsheet more carefully does not change the fact that the information still depends on someone remembering, every single time, across every change.
The actual fix is infrastructure and tooling that produces the inventory and the log review as a byproduct of how systems get built and operated, not as a separate task someone has to remember to perform. Infrastructure managed as code naturally produces an accurate, current record of what exists, because the record and the actual infrastructure are generated from the same source. Automated log aggregation and review tooling satisfies Requirement 10.4.1.1 directly, rather than requiring a person to somehow keep up with a volume of log data that was never realistic for manual review in the first place.
Building that foundation, so the artifacts a PCI assessment actually asks for exist automatically rather than depending on someone’s memory, is exactly the work behind Midcore’s infrastructure modernization engagements. Where the gap is specifically in the day-to-day operational discipline, monitoring, alerting, and keeping automated tooling actually running rather than quietly broken, CloudOps work is built to carry that ongoing responsibility. And for a team that wants the deployment pipeline itself to enforce these controls automatically rather than relying on a separate compliance process layered on top, DevOps practices are where automated log review, inventory generation, and change tracking actually get built into how every release happens.
Frequently Asked Questions
Why can’t a manual process satisfy PCI DSS’s automated log review requirement?
Requirement 10.4.1.1 of PCI DSS v4.0 specifically requires that audit log reviews be automated. It was an optional best practice through March 31, 2025, and is now mandatory. A manual review process, no matter how consistently performed, does not meet a requirement that specifically asks for automation rather than review by any method. The standard also added a related bullet requiring detection and reporting of failures in the automated review mechanism itself, which assumes automation is already in place to fail.
What does PCI DSS require for software and certificate inventories?
Requirement 6.3.2 requires a maintained inventory of bespoke and custom software to support vulnerability and patch management. Requirement 4.2.1.1 requires a maintained inventory of trusted keys and certificates. Both became mandatory on March 31, 2025, and both require the inventory to stay current as the environment changes, not just exist as a one-time snapshot.
Is it actually true that manual methods cannot keep an infrastructure inventory accurate?
NIST Special Publication 800-128 states this directly: managing the configurations found within system components using manual methods like spreadsheets has become an almost impossible task, and in most organizations it is impractical to manually collect accurate inventory information for analysis against the authorized inventory. This is federal guidance on configuration management generally, not an opinion specific to any vendor or industry.
Sources: PCI Security Standards Council, Summary of Changes from PCI DSS Version 3.2.1 to 4.0, Requirements 10.4.1.1, 6.3.2, and 4.2.1.1, and NIST Special Publication 800-128, Guide for Security-Focused Configuration Management of Information Systems.