Sample package

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.

Illustrative sample. Northwind is fictional, and its statuses, owners, dates and findings are made up. Control IDs and titles, evidence request templates and policy names come from RAMP's catalog. This is not an audit report, certification or attestation.

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

Gaps found in the Northwind sample
ControlGapRemediationTarget date
AIS-07 Application Vulnerability RemediationNo documented remediation time limits for high-severity findingsDefine and approve remediation SLAs2026-12-15
DSP-02 Secure DisposalDisposal procedure does not cover cloud storage snapshotsExtend procedure and name an owner2027-01-15
DSP-03 Data InventoryNo current inventory of systems holding customer dataBuild the data inventory2027-01-31
DSP-09 Data Protection Impact AssessmentNo impact assessment for the new AI summaries featureComplete and approve the assessment2026-12-31

2. Control matrix (excerpt)

Every control with its owner and its test of design and test of effectiveness status.

Control matrix excerpt
IDControlOwnerTest of designTest of effectiveness
AIS-02Application Security Baseline RequirementsEngineering leadDesignedNot yet tested
AIS-07Application Vulnerability RemediationEngineering leadDesign gapNot yet tested
CEK-01Encryption and Key Management Policy and ProceduresSecurityDesignedNot yet tested
CEK-03Data EncryptionSecurityDesignedSample 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.