01Define scope, criteria, and framework mapping
Start by defining the audit scope and the criteria against which the committee will be tested. Then map the committee's mandate to your adopted framework, so that each test traces back to a stated responsibility rather than to an informal expectation.
02Test design effectiveness
With the mandate mapped, test design effectiveness: whether the committee's mandate, as defined, covers the responsibilities in your adopted framework and the criteria set for the audit.
03Test operating effectiveness and trace decisions to runtime
Operating effectiveness is tested by sampling committee decisions and tracing each one to deployed configuration and runtime logs. Reviewing documents alone shows what the committee decided; the trace shows whether the decision took effect in production.
Evidence trace for one sampled decision
| Label | Description |
|---|---|
| 1. Committee decision | Approval, rejection, condition, or exception with criteria and date. |
| 2. Deployed policy | Permissions, tool-use restrictions, and settings in effect for the system. |
| 3. Runtime log | Records showing the policy was applied, including denied actions. |
| 4. Audit finding | Pass, deficiency, or untested, with the evidence reference. |
04Where manual review ends and runtime enforcement begins
Manual review can establish what the committee decided and when. Whether a decision is enforced is a separate question, and it is answered by deployed policy and runtime logs.
05Indicators to measure outcomes
Use defined indicators to measure outcomes alongside the control tests.
| Indicator | What it measures |
|---|---|
| Inventory coverage | Share of production systems and agents with a recorded risk classification and committee review. |
| Review turnaround | Time from submission to decision, reported by risk tier. |
| Classification consistency | Agreement rate when a sample is independently reclassified. |
| Exception rate and age | Number of policy exceptions, and how many are expired or have no owner. |
| Enforcement match | Share of sampled decisions whose conditions are confirmed in deployed configuration and runtime logs. |
| Incident follow-through | Share of incidents with a documented review, corrective action, and closure. |
06Report findings and prioritize remediation
Report each finding as a pass, a deficiency, or untested, with the evidence reference. Prioritize remediation so that the deficiencies with the greatest effect on production behavior are addressed first.