Paste your change log. See every production change without an independent approval.
SOX Change Log Checker reads the change or pull-request export you paste and marks each production change the way an auditor will test it. Paste your change or pull-request export, and optionally the deployment log. Get every production change with no independent approval, approvals recorded after the merge or the deploy, changes authored by a bot or AI coding agent with no human approval, people who approved or deployed their own change, emergency changes with no approval after the fact, deployments with no matching change, each with the SOX, SOC 2, ISO 27001, PCI DSS or NIST clause behind it, quoted and cited.
- 29NL-2129normalRefactor invoice rounding helperauthored bycode-agent[bot]AI coding agent, set to work by t.nakamuraapproved byt.nakamura14 Jul 06:17set the agent to workdeployed bysvc-release-pipeline14 Jul 11:17automated author, no human approval
- 19NL-2119normalUsage chart on the account pageauthored bys.patelmerged 29 Jun 15:07approved byp.alvarez29 Jun 20:073 h after the deploydeployed bysvc-release-pipeline29 Jun 17:07approved after it shipped
- 50NL-2150normalCapacity reservation for close weekauthored byk.oseimerged 14 Aug 10:50in all three rolesapproved byk.osei14 Aug 07:50is the authordeployed byk.osei14 Aug 12:50is the authorno independent approvaldeployed their own changeone person, three roles
- 7NL-2107normalSession length for idle usersauthored byj.ruizmerged 11 Jun 11:31approved bynone recorded no approverdeployed byj.ruiz11 Jun 13:31is the authorno independent approvaldeployed their own changeno ticket reference

Paste the population and the log
The change or pull-request export for the period, header row and all, in the first box; the deployment log in the second. Column names are read from a published dictionary of 215 aliases, times in ISO, US or UK formats, with the time zone and the date order stated on the result.
Read each change as a custody record
Who wrote it, who approved it and who put it into production, in that order, with the times. A field that breaks the chain is struck and the finding ticked: ten findings in a fixed order, a change under every one it raises, the clause behind each.
Take the pack into the walkthrough
The exceptions CSV is the population an auditor samples from. The reconciliation sheet ties every deployment to a change. The walkthrough pack gives, per finding, the rows, the clause and the question the auditor is likely to ask.
Why read the log before the auditor does
The auditor asks for the change population, samples it, and tests each change for an approval by someone other than its author, dated before it shipped. When an agent writes the change, the person who prompted it cannot be its only approver, and the change log is where that shows first. Reading the whole population first turns the sample into rows you have already explained.
Production changes and approval: the questions auditors ask
What does SOX Change Log Checker do?
It reads the change or pull-request export you paste and marks each production change the way an auditor will test it. It lists every production change with no independent approval, approvals recorded after the merge or the deploy, changes authored by a bot or AI coding agent with no human approval, people who approved or deployed their own change, and emergency changes with no approval after the fact. Each row carries the SOX, SOC 2, ISO 27001, PCI DSS or NIST clause behind it.
What does an auditor test on a production change?
The auditor asks for the change population, samples it, and tests each change for an approval by someone other than its author, dated before it shipped. This tool reads the whole population first, so the sample becomes rows you have already explained. It gives no pass or fail and no audit opinion.
Why does it need the deployment log?
It cannot see your systems, so paste the deployment log beside the change tickets and it reconciles the two. That surfaces deployments with no matching change and changes that were never deployed. A specimen run reported 58 deployments reconciled, 56 matched, 2 with no matching change and 4 changes never deployed.
What if an AI coding agent wrote the change?
When an agent writes the change, the person who prompted it cannot be its only approver. The tool flags a change authored by a bot or AI coding agent with no human approval. The change log is where that shows first.
Does it give a pass or fail or an audit opinion?
No. It gives no pass or fail and no audit opinion; it lists the rows that need a look, with the clause behind each. It reads no code and no system, and gives no view on any control.
Which frameworks' clauses does it show?
You can tick SOX 404 (with COBIT and AS 2201), SOC 2, ISO 27001, PCI DSS and NIST SP 800-53, and the clauses shown are those of the ticked frameworks. It holds the text of SOX 404 / ICFR, PCAOB AS 2201, COBIT, ISO/IEC 27001:2022 and NIST SP 800-53 Rev 5, and where the page names an instrument without stating its requirements, it says so and does not state them.
Is it free?
Eight changes can be checked free with no account, and nothing leaves your browser until you save. The full specimen shows sixty changes on the page.
How does it handle emergency changes?
You set an emergency window in days, and emergency changes with no approval after the fact are flagged. That keeps an emergency deploy visible without treating the exception as automatically acceptable. The finding cites the clause and the question the auditor is likely to ask.
What does it produce for the walkthrough?
The exceptions CSV is the population an auditor samples from, and the reconciliation sheet ties every deployment to a change. The walkthrough pack gives, per finding, the rows, the clause and the question the auditor is likely to ask. Those are the three outputs you take into the walkthrough.
Does it connect to my code host or pipelines?
No. It works from the export you already have, in your browser, with no connection into your code host or your pipelines to approve first. Column names are read from a published dictionary of 215 aliases, and times in ISO, US or UK formats are read with the time zone and the date order stated on the result.
What columns does it read?
It recognises columns such as id, author, approver, approved_at, merged_at, type, ticket and tests by name. The deployment log takes deployment, change, system, deployed_at and deployed_by. A preamble line can set the approver list, the emergency window and the time zone.
How does it read each change?
It reads each change as a custody record: who wrote it, who approved it and who put it into production, in that order, with the times. A field that breaks the chain is struck and the finding ticked. Ten findings run in a fixed order, with a change under every one it raises.
How SOX Change Log Checker compares with the alternatives
A spreadsheet is better as the change log the auditor samples, because it is free and the export already arrives in that shape. An auditor, SOX consultant or lawyer is better on opinion and judgement, since whether a control is effective and what an exception means is their call, and an ERP or IT service management platform is better at enforcing the approval workflow at source rather than reading it after the fact. A general AI assistant is better at drafting the walkthrough narrative or explaining what PCAOB AS 2201 expects, but it does not reconcile a change export against a deployment log or test each change for approval by someone other than its author. The checker reads the population you paste and lists the rows that need a look — no independent approval, an approval recorded after the merge or deploy, an automated author with no human approval, self-approval, an emergency change with no approval after the fact — each with the SOX, SOC 2, ISO 27001, PCI DSS or NIST clause behind it; it gives no pass or fail and no audit opinion.
Primary source: PCAOB AS 2201