Simulated portfolio. Everything here is a simulated case study using synthetic data about a fictional company. It is not client work, a real audit, a certification or an assurance opinion.
ASSURANCE: GRC, IT audit, technology risk

ITGC audit / Workpaper

Workpaper T-12: NS-CHG-04

Simulated. Fictional company; synthetic data; no real audit.

SIMULATED. Fictional company Northstar Financial Technologies; synthetic data; no real audit.

Field Value
Control NS-CHG-04
Objective Emergency changes receive retrospective approval within 2 business days.
Audit period 2026-01-01 to 2026-06-30
Population 14 Emergency changes (Emergency-type changes)
Method None: 100% of the population tested by script
Evidence n/a (see evidence register)
Rule(s) applied R-CHG-05
Preparer Audit analyst (simulated)
Reviewer Audit Manager (simulated role)

Selection rationale

The full population was tested by script because the evidence is a complete system export and scripted re-performance costs no more than sampling. No sample was drawn, so there is no sampling error and no statistical assurance is claimed. Source tickets and screenshots behind each record were not inspected (synthetic data); in a real engagement a risk-based sample of source records would be inspected as well. Selected records: the whole population; exceptions are listed below.

Pass / fail / inconclusive criteria

Pass: exceptions are within the tolerable deviation rate. Fail: exceptions exceed it. Inconclusive: the evidence is incomplete or unreliable, so a conclusion cannot be supported (does not apply to this test).

Steps

  1. Confirm retrospective approval exists. 2. Count business days from implementation to approval.

Expected result

Retrospective approval within 2 business days. Tolerable deviation: 0%.

Result

3 of 14 Emergency changes failed (21.4%)

Conclusion: Not operating effectively

Limitations

Small population; each exception is a large percentage.

Exceptions (3)

Rule Record Detail
R-CHG-05 CHG-0017 SYS-01 Emergency change: retrospective approval 6 business days after implementation (limit 2)
R-CHG-05 CHG-0032 SYS-01 Emergency change: retrospective approval 9 business days after implementation (limit 2)
R-CHG-05 CHG-0039 SYS-01 Emergency change: retrospective approval 15 business days after implementation (limit 2)

Reviewer notes

Reviewer role is simulated. This workpaper has not been independently reviewed by a human; the 'reviewer' field records who would review it in a real engagement.

Re-performance

Re-run with docker run --rm -v "$PWD":/work assurance-build python scripts/itgc_audit.py. Output is deterministic for the committed data.

Control tests (CSV) · Back to findings