What an audit-readiness package looks like
A small extract of the package RAMP prepares for an auditor or a continuous monitoring tool, built for a fictional company, Northwind Software.
1. Gap summary
The page leadership reads first: where the design holds up and where it does not.
14
controls in scope (extract)
10
designed
4
with a design gap
| Control | Gap | Remediation | Target date |
|---|---|---|---|
| AIS-07 Application Vulnerability Remediation | No documented remediation time limits for high-severity findings | Define and approve remediation SLAs | 2026-12-15 |
| DSP-02 Secure Disposal | Disposal procedure does not cover cloud storage snapshots | Extend procedure and name an owner | 2027-01-15 |
| DSP-03 Data Inventory | No current inventory of systems holding customer data | Build the data inventory | 2027-01-31 |
| DSP-09 Data Protection Impact Assessment | No impact assessment for the new AI summaries feature | Complete and approve the assessment | 2026-12-31 |
2. Control matrix (excerpt)
Every control with its owner and its test of design and test of effectiveness status.
| ID | Control | Owner | Test of design | Test of effectiveness |
|---|---|---|---|---|
| AIS-02 | Application Security Baseline Requirements | Engineering lead | Designed | Not yet tested |
| AIS-07 | Application Vulnerability Remediation | Engineering lead | Design gap | Not yet tested |
| CEK-01 | Encryption and Key Management Policy and Procedures | Security | Designed | Not yet tested |
| CEK-03 | Data Encryption | Security | Designed | Sample requested |
What is in the full package
Gap summary
The summary leadership reads first: scope, test of design results and the gaps found, with next steps.
Control matrix
Each control with its test of design and test of effectiveness status, gaps, owners and target dates.
Evidence requests
Requests generated per control, with who is asked, how often, and examples of acceptable evidence.
Policy map
Policies mapped to the controls they support, with their status.
Audit plan
How design and effectiveness testing proceeds, step by step, from sampling to exceptions to hand-off.
Sign-off record
Where the human reviews and approvals are recorded for the file.
Want one for your organization?
Check where you stand first, or schedule a walkthrough.
