Compliance frameworks

The Compliance area puts every framework your organisation answers to on one screen, then lets you open any single control to see what still stands between it and coverage.

A framework is a published set of requirements you measure yourself against, such as DORA, GDPR or ISO 22301. Each framework breaks into controls. You link policies, procedures, risks and evidence (the proof a control works) to those controls, and Aegis reads only those links. One rule decides the headline number: a control counts as covered when at least one linked evidence item is approved and still inside its valid-until date. A control with only a policy, a procedure or a risk linked is partial, not covered. Coverage records that approved, current evidence is present; Aegis does not judge whether that evidence's content actually meets the requirement. That judgement stays with your reviewers and your auditor.

Who uses it

What's on this screen

Open Control Measures (under Compliance) in the left menu to reach /compliance. This is the controls list; typing /controls also lands here. The header reads Compliance above the line "Track evidence coverage and implementation status across compliance frameworks". Three buttons sit on the right: Gap Triage (AI), Coverage Triage (AI) and the dark Export button.

Below the header are five figures: Evidence Coverage, Total Controls, Approved Evidence, Compliant and Overdue Evidence. They count only frameworks that are both enabled and applicable. The captured screen shows 72% coverage across 847 controls, with 449 of them Compliant and none overdue. Coverage shows green from 80%, yellow from 60% and orange below. A note under the figures repeats how coverage is computed: at least one approved, unexpired evidence item is linked, and the content of that evidence is not assessed. It also points you to Review content (AI) on an evidence item when you want that content checked, as an advisory review.

Next comes the Data Loss card: Events, Blocked and Overridden counts for DLP (data loss prevention) events from Microsoft Purview over the last 30 days, with an Open Data Loss button. The card appears only when the Data Loss module is switched on, your licence includes it and your role may read it; otherwise the page goes straight to the frameworks.

Under Frameworks is an alphabetical grid of cards, four to a row. Each gives the framework name, its percentage, a progress bar and a line such as "24 compliant of 56". Three badges can appear on a card. A yellow Newer edition badge (on ISO 9001:2015 in the capture) means the publisher has superseded the edition Aegis ships; hover over it to see which edition. A blue Guidance badge (on NEN 7512 and NEN 7513 in the capture) marks implementation guidance that is not certifiable on its own; hover to see the standard you certify against. The NIS2 card shows your entity class, such as Essential, taken from your organisation profile. A framework your organisation profile marks as not applicable stays on the grid with a dashed border, a Not applicable to your organization label and — in place of a percentage. A framework that is switched off reads Disabled.

Below the captured area come Control Requirements (the filterable controls table), Saved AI insights and Action items.

Working from the overview

  1. Select Gap Triage (AI). The Control Gap Smart Triage window opens and waits for Run Gap Triage. It ranks open gaps into a 90-day sprint and a 12-month horizon.
  2. Select Coverage Triage (AI). Its window looks at controls with nothing linked at all and suggests where to start.
  3. Select Export. The Export Compliance Data window asks for a format (JSON, CSV, PDF, OSCAL SSP or OSCAL AR) and a scope (Executive Summary, All Frameworks, Single Framework or Statement of Applicability). Confirm, and the file downloads. The Statement of Applicability also has its own button on the framework page, described below.
  4. Read Evidence Coverage: the share of controls with approved, current evidence. Compliant, by contrast, counts controls whose own status is Compliant.
  5. Where the Data Loss card is shown, select Open Data Loss. The Data Loss module opens at /compliance/data-loss with the events behind the three counts.
  6. Select a card, for example DORA. The card gains a highlighted border, the heading changes to Frameworks (click to clear filter), and the controls table below shows only DORA controls. Select the card again to clear the filter.
The Compliance overview: AI and export actions, the five headline figures, the Data Loss card and the framework cards — /compliance.
The Compliance overview: AI and export actions, the five headline figures, the Data Loss card and the framework cards — /compliance.

Opening a control

Scroll to Control Requirements, narrow the table with the search box and filters, then select a row. A window opens, headed with the control's reference and title, with the framework and a status badge beneath. Its Applicability panel records the Statement of Applicability (SoA: the per-control record of whether and how a control applies to you) decision. A Manager or Admin can change it; for a Contributor or Viewer the options are read-only and there is no save button.

The first capture shows NEN 7510-2 8.2, Special access rights, opened as a Manager. Below the panels sit the control's text and, where the catalogue publishes them, collapsed Purpose, Guidance and Other information sections you can expand. The footer holds Close and, for a Manager or Admin, AI Implementation Proposal; a Contributor sees only Close.

  1. Set Implementation status. Only a Manager or Admin sees this list. Pick Not Started, In Progress, Compliant or Non-Compliant, and the status badge above updates. Compliant is greyed out while something stands in its way, with the reason beside the list: unresolved gaps, incomplete requirements, no linked evidence, only expired evidence, or evidence still awaiting its four-eyes approval. While a control is not applicable, its status is frozen.
  2. Under Statement of Applicability decision, which reads No decision recorded yet. until someone saves one, choose Comply — the guidance is followed when you apply the control as the framework describes it. A justification is optional.
  3. Choose Deviate — applied differently (explain how and why) when you meet the aim another way. NEN 7510 works on comply-or-explain, so the explanation is required: the field label turns to Justification (required) and saving waits until you have written one.
  4. Choose Not applicable (explain why) to take the control out of coverage. It also needs a justification.
  5. Write the reasoning in the justification field.
  6. Select Save. It is greyed out until something has changed. The decision, who made it and when then travel into the Statement of Applicability export.
A NEN 7510 control opened as a Manager: the implementation status list and the Statement of Applicability decision — /compliance.
A NEN 7510 control opened as a Manager: the implementation status list and the Statement of Applicability decision — /compliance.

Some controls can never be excluded. ISO management-system clauses 4 to 10 are mandatory, and so are CyFun key measures; for those the panel offers only Comply and Deviate. The second capture shows ISO 27001 clause 4.3 as a Contributor, so the Implementation status list is absent and only the In Progress badge shows the status.

  1. Read the note: “This is a mandatory management-system clause (clauses 4–10). It cannot be marked not applicable.”
  2. Under Statement of Applicability decision only the comply and deviate options appear, read-only for a Contributor. Once a decision is saved, the panel names who made it and when; the captured screen reads "Decided by Sophie Peeters on Jun 9, 2026".
  3. Justification (optional) is read-only too, so this capture has no save button.
  4. Check Organization-defined parameters: values the framework leaves to you, which flow into the exports and the OSCAL system security plan. Here the catalogue defines none.
  5. Read Expected evidence, below the control text: what the catalogue says an assessor should see for this control. It appears only where the catalogue publishes it. Further down, Owner group shows who owns the control, with a No owner assigned label when nobody does yet.
  6. Select Close. The window closes and the table row reflects any saved change.
A mandatory ISO management-system clause offers no not-applicable option — /compliance.
A mandatory ISO management-system clause offers no not-applicable option — /compliance.

A framework's own page and its Statement of Applicability

Select a framework card's name, or open /compliance/<framework>, for example /compliance/NEN7510. A breadcrumb leads back to Compliance. The page shows the framework's key, version and publication date, and an Active badge beside the export button while the framework is switched on.

  1. Read the line under the version. It gives the date the framework applies from, where that differs from publication, and the date its edition was last assessed; the captured screen reads "Edition assessed on 2026-10-14".
  2. Select Statement of Applicability at the top-right. The export window opens with that scope and this framework already chosen.
  3. Read the Applicability timeline, where the framework has one: dated obligations, oldest first, each marked In effect or Upcoming, with a Source link and the date it was last verified against that source.
  4. Scan the figures: Evidence coverage, Applicable controls, Not applicable, Not an obligation, Approved evidence, Partial and Gaps.
  5. Not applicable counts controls you have excluded through the SoA decision. Not an obligation counts controls the catalogue itself marks as awareness or good practice rather than a requirement. Neither counts towards the coverage percentage.
  6. Read the note under the figures. Coverage means at least one approved, unexpired evidence item is linked; Aegis checks presence and currency, not whether the content meets the requirement.
The NEN 7510 framework page with the Statement of Applicability button, the applicability timeline and the coverage figures — /compliance/NEN7510.
The NEN 7510 framework page with the Statement of Applicability button, the applicability timeline and the coverage figures — /compliance/NEN7510.

If any control has overdue evidence, an orange banner under the note counts them and asks you to renew or replace the expired evidence. The Controls table follows, with the columns Ref, Title, Status, Mappings and Evidence (Yes, Overdue or No). Further down is a Gaps list of controls with no policy, risk or evidence mapped at all.

In the export window, check Export Scope and Select Framework first. Per control, the SoA lists the decision, justification, implementation status, evidence and the linked policies and procedures, with who decided and when. Under Include Details, one box (Policy/Risk/Evidence Mappings) starts ticked. Untick it to leave the names of the linked policies, procedures and evidence out of the file; the evidence count stays.

  1. Note the format: the window opens on JSON, and a line under the format grid describes whichever format is selected.
  2. Choose Excel for a branded workbook of the Statement of Applicability.
  3. Choose Word for the same content as a branded document. Both formats appear only while the scope is Statement of Applicability; pick another scope and the window falls back to JSON.
  4. Select the export button in the footer, which names the format (for example Export JSON). The file downloads. Cancel closes the window without exporting.
Exporting the Statement of Applicability, with the Excel and Word formats — /compliance/NEN7510.
Exporting the Statement of Applicability, with the Excel and Word formats — /compliance/NEN7510.
When a framework is switched off

An administrator can switch a framework off in Settings → Frameworks. Its pages then show a card reading “… is switched off” instead of their content, its API calls are refused and its reminders stop. The data is kept and returns when the framework is switched on again. This applies to every framework page, including DORA, the EU AI Act, ISO 42001, CyFun, ESRS and the NEN 7510 hub. An Admin sees the link Open Settings → Frameworks on the card. A framework outside your licence shows a different card, “… Not Available”.

Moving a control forward

This needs Manager rights. Further down the same control window are Implementation progress, a Maturity panel where the framework defines a maturity scale, and the requirements, each with a status of Not Started, In Progress or Complete.

The DORA page

DORA (the EU's Digital Operational Resilience Act) has its own page at /compliance/dora. A DORA Readiness bar under the header shows how many of four areas are complete, with the note "Complete all four areas to achieve full readiness"; the captured screen reads 100%. Four figure cards follow: DORA Profile (Configured, with Edit), ICT Assets, Third-Party Providers and Resilience Tests. Below them, navigation cards open DORA ICT-Related Incidents (Article 18), ICT Assets (Article 8), Third-Party Providers (Articles 28–44) and Resilience Tests (Articles 24–27).

  1. Select AI Register Readiness. Aegis scores your Register of Information against DORA Article 28(3) and lists gaps and next steps. You decide which to act on.
  2. Select Edit on the DORA Profile card. The profile window opens; only entity type is required. Save, and the readiness bar updates. With no profile yet, the button reads Configure.
  3. Read Saved AI insights. In the capture it is empty: "No AI insights saved yet. Run an AI action and choose 'Save as record' to keep it here." Once you keep a run, each insight shows the date it was saved and a provenance badge; Show more expands the full text, Create action item turns a recommendation into tracked work, and Edit and Delete amend or remove it.
  4. Read Action items at the foot of the page. It stays empty until you use Create action item inside an AI result.
The DORA landing page: readiness bar, profile and register cards, and both AI panels still empty — /compliance/dora.
The DORA landing page: readiness bar, profile and register cards, and both AI panels still empty — /compliance/dora.
A saved insight is a snapshot, not a live reading

Saved insights record what was true when the run happened. An insight saved before you configured the profile or filled the register can still say the register is incomplete. Run AI Register Readiness again after you change the register, and delete insights that no longer apply. A Legacy record badge means the insight was saved before AI runs were recorded, so its origin cannot be verified.

The EU AI Act page

/compliance/eu-ai-act is the entry point for the EU AI Act (Regulation 2024/1689). Five figures follow the header: Total Systems, High Risk, Conformity Passed, FRIA Required (FRIA is a fundamental-rights impact assessment) and Reassessment Required. The captured screen shows 13 systems, 4 of them high risk. Four navigation cards lead to AI Systems, Technical Documentation (Annex IV), Transparency Obligations (Article 50) and Prohibited Practices Check (Article 5).

  1. Select AI Inventory Readiness. Aegis scores your registered AI systems on prohibited practices, classification, FRIA, conformity and registration, tying each gap to an article. With an empty inventory it says so and does not invent systems, so register them first through AI Systems.
  2. Read Saved AI insights. Until you keep a run, it says "No AI insights saved yet. Run an AI action and choose 'Save as record' to keep it here."
  3. Read Action items. It stays empty until you use Create action item inside an AI result, exactly as on the DORA page.
The EU AI Act landing page with registered systems and both AI panels still empty — /compliance/eu-ai-act.
The EU AI Act landing page with registered systems and both AI panels still empty — /compliance/eu-ai-act.

The AI assist

All five AI actions in this area read what is recorded, write a briefing, and leave the decision to a person. None changes a control, status or mapping by itself. The gap triage ranking comes from fixed rules, not from AI. Keep any run with Save as record. Every AI action is logged and uses your organisation's AI credits. To have an evidence document's content checked against its controls, use Review content (AI) on the evidence item; that review is advisory and does not change coverage.

Tips and limits

Where this connects

Close gaps by linking work from Policies, Procedures and Evidence, and by recording treatment in Risks. Control Mapping, CyFun Maturity and Mock Audit cover the related sub-pages. DORA Compliance, EU AI Act and Healthcare (NEN 7510) go deeper into their framework pages. Data Loss covers the module behind the overview card. Audit readiness turns this picture into a checklist, and the work you take on is tracked in Action items.