Scenario: preparing for an external audit

An external audit is booked for next quarter — this is the route one team takes through Aegis to arrive prepared, rather than assembling answers the night before.

An external audit (an independent check that your controls really work) is rarely a surprise: the date is usually known months ahead. This chapter follows a compliance lead, a Contributor named Priya, and her Manager, Tom, from "we have an audit coming" to a board pack on the morning of the assessment. The journey crosses five modules — the mock audit, the framework view, the evidence library, audit readiness, and board reports. No single screen does the whole job; what follows is the order to work in, with each module's own chapter linked as you go.

Who does what

Two steps in this journey are reserved. Running a mock audit — and deleting one, generating AI questions for it, or driving its simulator — needs the Run Mock Audits permission, held by Manager and Admin. Generating a board report is likewise Manager and above. Everything in between is ordinary Contributor work: mapping controls, uploading evidence, updating statuses, and raising a non-conformity from a mock audit's findings. Reading is open wider — a Viewer can open the Mock Audits list and the Audit Readiness page, but cannot start or change anything there. Every action is written to the audit log, so the record of who did what, and when, builds itself as you work.

What's on this screen

The journey starts at Mock Audits, at /compliance/mock-audit. Despite the route, the sidebar link sits in the Audit group, one below Compliance — the same group that holds Benchmarking, Audits and the audit log. The link itself reads Mock Audit, singular, where the page it opens is titled Mock Audits. The top bar above it — your organisation's name, search, language, the light/dark toggle, the ? button that slides in the help panel, the book-shaped User Guide button, the notification bell, your own name and Sign out — is constant across Aegis and is described in The screen layout. The round purple button in the bottom-right corner opens the AI assistant.

The page itself opens with the title Mock Audits and the line "Simulate audit scenarios to test compliance readiness across frameworks." Beneath it sits a single control: an All Frameworks dropdown that narrows the list to one framework at a time.

The rest of the page is a table of past runs with five columns — Framework, a Status badge (In Progress or Completed), a Readiness percentage, and the Completed and Created dates. There are no per-row buttons; the row itself is the control, and selecting one opens that run's detail dialog. Below the table a count ("Showing 1 to 10 of 10 mock audits" in the capture) sits opposite the pager: Previous, the page numbers, and Next. With a single page of results, both arrows are greyed out. The captured screen holds ten runs across NIS2, GDPR, CyFun and DORA. The newest, a DORA run, is still In Progress: its Readiness cell reads Pending and its Completed cell a dash. The nine finished runs score between 33.5% and 58.6%. The readiness figure is colour-coded — green at 80% and above, amber from 60%, red below — though the number itself carries the meaning.

One thing is missing from this capture, and its absence is worth knowing. There is no Run Mock Audit button in the header. The screenshot was taken as a Contributor, and that button is rendered only for roles holding the write permission. If you cannot see it, that is your role, not a fault.

Step 1 — Open the rehearsal and read the score

A mock audit (a rehearsal of a real assessment) runs in its own tracking space and does not move your live compliance score, so it is safe to practise with. The module sits behind two gates. Your operator provisions it for your tenant, and your licence tier has to include the feature, which ships with Professional and Enterprise. Without the module, the link is absent from the Audit group; with the module but not the licence, the page opens with a short notice that mock audits are not available on your current plan.

  1. Open the Audit group in the left sidebar and select Mock Audit. The list loads with the framework dropdown above it and one row per past run.
  2. If you want the module chapter open while you work, the book-shaped User Guide button in the top bar opens the in-app guide at the chapter for the screen you are on. It is a full page of its own, so use your browser's back button to return to the list. The ? button beside it is different: it slides a help panel in over the page instead.
  3. Check the name in the top bar. Your role decides what you get here: with Run Mock Audits you also see a Run Mock Audit button in the header; without it, the list is read-only.
Mock Audits seen as a Contributor — ten runs, the newest still In Progress, and no Run button in the header — /compliance/mock-audit.
Mock Audits seen as a Contributor — ten runs, the newest still In Progress, and no Run button in the header — /compliance/mock-audit.

Tom, as Manager, selects Run Mock Audit. A small dialog opens with one field: a Framework dropdown offering NIS2, GDPR, CyFun, DORA and NEN 7510. Under it, an expandable What will be checked section lists that framework's questions, the evidence each one expects, and what Aegis accepts as that evidence; questions outside your recorded scope, Statement of Applicability or CyFun target level are skipped when the run executes. He picks the framework the auditor will assess and selects Run Audit. The dialog cannot be dismissed while the run is being queued; once it closes, a message confirms the run is queued and the table refreshes with the new row. Until the score is computed, the Readiness cell reads Pending rather than a percentage, and while any run in the list is In Progress the table refreshes itself, so the score appears without a reload.

Step 2 — Read the findings inside the run

The percentage on the list is the headline. The useful detail is one click deeper, and this is where Priya starts her to-do list for the quarter.

  1. Select the run's row. A detail dialog opens, headed with the framework name — for example NIS2 Mock Audit — the status badge, and the readiness badge.
  2. Read the Summary and Overview sections: framework, total findings, and the created and completed timestamps. Where your organisation profile places you outside the framework's scope, a notice says the score is a voluntary benchmark rather than an in-scope result; where questions were skipped, a section lists them with the reason and, for CyFun, the target assurance level.
  3. Work through Findings Breakdown, which counts findings by type (Conforming, Observation, Minor NC, Major NC), then Evidence checks per question. Open a question there to see each expected evidence item marked Found or Missing, the records that matched, and the rule that decides what is accepted. A question conforms only when every expected item is found.
  4. Read Critical Gaps, which names each weak answer with an explanation and a suggested fix, and carries an Add evidence in the Evidence Locker link to the evidence library — then Recommendations.
  5. Where a gap warrants formal tracking, use the raise-a-non-conformity button in the dialog header. The form opens already anchored to this run and pre-titled with the framework, so finding and corrective action stay linked.
A mock audit points; it does not fix

The run puts the framework's audit questions to your records and checks each one for the evidence it expects — an approved Evidence Locker item, an approved policy, procedure or continuity plan, or a live record in the right register — then scores how well you could answer them. It tells you where you are weak. The remediation happens in the modules that follow. A person reviews the findings and decides what to act on; nothing is changed on your behalf.

Step 3 — Close the gaps in the framework

Armed with named gaps, Priya moves to the live framework view to do the real work.

  1. Open Compliance and select the framework that scored low. Its controls load.
  2. Work down the controls that carry no mappings — those are the gaps. For each one, link an existing policy, attach evidence, or correct the control's status so it reflects what is actually true today.
  3. Use the filters to split the work across the team, so several people can take different slices of the same framework rather than queuing behind one another.

This is the substantive part of getting ready: the mock audit told Priya where to look, and the framework view is where coverage improves. See Control mapping for how one policy can satisfy controls in several frameworks at once. Where a control genuinely will not be met in time, record it in the Exceptions register with an owner and an end date; an auditor treats a documented, time-boxed exception differently from an unexplained blank.

Step 4 — Assemble the proof behind each claim

Several controls will need fresh proof. Evidence is what an auditor can verify — a report, an export, a signed record — so a control claim with no artefact behind it will not survive the conversation.

  1. Open the Evidence library and start a new item. A form opens for the file and its details.
  2. Upload the artefacts the audit will ask for — often a penetration-test report and an access-review export — and set a Valid Until date on each, so Aegis can warn you before they lapse.
  3. Link each item to the controls it supports, so both the framework view and the readiness figures count it.

Dating each item matters more than it looks. An item with no Valid Until date counts as permanently valid; one whose date has passed stops counting towards completeness. That keeps the readiness picture honest, and it is why a figure can fall without anyone touching it. The mock audit's evidence checks look for approved items whose name, type or tags match what a question expects, so name and tag the new items plainly — then run the mock audit again to see the Missing marks turn to Found.

Step 5 — Check the aggregate picture

With gaps closed and evidence linked, Priya checks where the programme now stands. The figures on Audit Readiness are derived: they reflect work done in the other modules and cannot be edited on that page. Its own controls are few: a ranked Recommendations panel whose entries link out to the screen where each fix is made, and one AI triage that drafts a pre-audit plan from the score Aegis has already computed.

  1. Open Audit Readiness. Four stat cards head the page: Overall Readiness, with a line beneath the percentage reading Whole organisation, a High, Medium or Low label and the date the score was computed, then Frameworks, Controls Covered and Coverage Rate.
  2. Read the Readiness Trend card, which plots the stored readiness snapshots and the change since the first one. Until at least two snapshots exist it says there is not enough history yet.
  3. Scan the framework table below. Each row shows control coverage as a bar with the fraction and percentage beside it, an evidence percentage, and a readiness badge with its own percentage and a short note on how it was measured — so you can watch the framework you have been working on climb. Confirm the evidence column has picked up your new items. If a framework still reads Low, step back into Compliance and keep going.
  4. Work through the Recommendations panel under the table. Aegis ranks what is weakest — thin policy coverage, missing or stale evidence, open control gaps — and each entry carries a High, Medium or Low priority and a Take action link that opens the screen where the fix is made. When there is nothing left to rank, the panel says so instead of listing items.
  5. For a sequenced plan covering the time that is left, select Readiness Triage (AI) beside the heading. It narrates the recommendations Aegis has already worked out — it does not invent a gap or move a score — and what it drafts is kept with the page as saved insights and action items you can hand out.

The bands themselves are fixed, and the same thresholds label a framework row and the overall card — but they are applied to different numbers: a row is graded on that framework's conformity (the note under the badge reads Compliant controls, or names the CCB self-assessment and target level where that is the measure), the card on the weighted readiness score described under Tips and limits.

Score Readiness label
80% and above High
50–79% Medium
Below 50% Low
Nothing in scope to measure yet (a framework row only) N/A, with no percentage on the badge

A framework that has been activated but not yet populated therefore reads N/A rather than Low — empty, not failing — and its coverage cell reads 0/0 (0%). When no controls are loaded anywhere, the Coverage Rate card reads N/A too. If no framework has been configured at all, the table is replaced by a line telling you to add one from the Compliance page.

Step 6 — Brief the board, then walk in

The week before the assessment Tom prepares the leadership view; on the day, the team works from the record it has been building all quarter.

  1. Open Board Reports and select Generate Report. The dialog asks for two things: a Title, which is required, and an optional Period such as 2026-Q2. There is no framework picker — the report is drafted across your whole recorded posture, so name it for the audit it is written for.
  2. The report is queued and builds in the background; the row shows Generating… until it turns Completed. Open it and read the Report Sections: they are generated from your data and are not editable here.
  3. Work on the Executive Summary — the AI-drafted part, and the only section of the report body you can edit. It is marked Pending review until a person has read it. Select Edit, correct anything that does not hold, save, then Mark reviewed. Record what leadership decides under Board Decisions, with an owner and a due date.
  4. Send it out with Download PDF, Download Excel or Download Markdown, or use Email Report to post it to one recipient — which needs working SMTP, or it tells you email is not configured.
  5. On the day, when the auditor asks for proof that a control works, open the control in Compliance, follow the link to its evidence, and show the artefact with its date. When the auditor asks when a change was made or who approved it, the audit log answers that.

The AI assist

Two AI helpers live inside a mock audit run. Both sit in the run's detail dialog rather than on the list in the capture above, and both need the write permission and an active AI entitlement, so a Contributor opens that dialog without them. Generate AI questions drafts the questions an auditor would put to your organisation for this framework, built from your recorded control posture, open gaps and supporting documents. Each draft carries a severity, a control reference, and a note on what good evidence would look like. Nothing is saved until you review the drafts, reject the ones that miss, and attach the rest; attached questions then appear in their own section of the run. Attaching again replaces the whole attached set, and the dialog warns you before it does. Run simulation is a separate exercise: it walks you through the framework's built-in question bank one question at a time, evaluates each written answer, and records a finding. Only the person who started the run can answer its questions; for anyone else, and for a run that is already completed, the button reads View simulation results and opens the answers read-only. Evaluating an answer spends an AI credit — with none left, the answer is not recorded and you are told to top up and submit it again. Attached AI questions sit alongside that bank rather than replacing it. Both are internal preparation aids built from your own records — not a regulatory submission, and not a pass or a fail. A person reviews and decides; the AI never changes a control or closes a gap.

Tips and limits

Where this connects

Each module in this journey has its own chapter: Mock audits, Compliance frameworks, Control mapping, Evidence, Policies, Audit readiness and Board reports. Internal audits, run to a schedule you set, are covered in Audits; findings you raise formally are tracked in Non-conformities; the work the triage produces lands in Action items. For healthcare organisations rehearsing NEN 7510, that chapter covers the framework itself. For who can do each step, read What each role can do; to trace what happened and when, see the Audit log. If a screen does not behave as described here, Getting help lists the common causes.