Draftv0.2Open for reviewer comment
Testing change management when AI writes or approves code
Seven tests an IT auditor can run with git and the code host's audit log. No product is needed.
About this document
A draft procedure for IT auditors, proposing how to test a change-management control when AI assistants write code, or bots and agents approve or merge it. It sets out seven vendor-neutral tests that run with git, the code host's audit log and standard tools, and maps them to SOC 2, ISO 27001, SOX ITGC and PCI DSS change controls. It is not an audit standard or an opinion on any control.
Who it is for
External and internal IT auditors testing SOC 2, ISO 27001, SOX ITGC or PCI DSS change controls, and the teams preparing for them.
What's inside
- T0Repositories are tiered by risk
- T1Population includes every change, however it was made
- T2Every actor is identified as a person, a bot or an agent
- T3The approver is independent of the author
- T4A person reviewed the change where policy requires one
- T5The controls themselves stayed on
- T6AI involvement is declared where policy requires it
Preview
Open in browserVersions
| Version | Date | What changed | Size | SHA-256 | |
|---|---|---|---|---|---|
| Draft v0.2 | Adds "Sample size": test what the data can prove on every change (T1, T2, T3 and T5 across the whole population by analytics once the data source is validated), sample only what needs judgement (around 25 to 60 items, weighted towards high-risk repositories and agent-authored changes), and investigate every exception individually. | 175 kB | f6243405…8ee8bb | Download PDFOpen in browser | |
| Draft v0.1 | Adds "Known limit, by design": AI authorship cannot be verified, and the procedure does not depend on it. Question 1 now asks about T0 to T5 and whether T6 is worth keeping as a policy test. | 166 kB | 0d637a6e…452273 | Download PDFOpen in browser | |
| Draft v0 | First published version | 163 kB | 154e6c53…edc6bf | Download PDFOpen in browser |
A link you received always shows that version. A later version is a new file and a new row here; no file is ever replaced.