Skip to content
Framework mapping

Stay ready for Cyber Essentials reviews

Map Cyber Essentials to the controls and evidence your team already maintains, keep the record current between cycles, and answer auditors, customers, and security reviewers with traceable proof without rebuilding the record each time.
68
Requirements
17
Mapped controls
36
Evidence specs
35
Test assertions
15
Sources
6
Domains
25%
Automated
Published by Cyber Essentials: Requirements for IT Infrastructure v3.2Latest: Requirements for IT Infrastructure v3.2 (active applied baseline on 2026-03-19; v3.3 preview not yet active)Mapping updated Mar 24, 2026View official source

Evidence automation

How Cyber Essentials Evidence Gets Collected

Aurora maps framework requirements to evidence specifications with defined collection methods, cadence, and integration sources.

Collection methods
36evidence specs defined
9automated25%27manual
Collection cadence
36 scheduled
3P1Y1P6M7Daily1Weekly7Quarterly6Semi-annual11Annual
Connected sources
15
Crowdstrike FalconGoogle WorkspaceIntuneJamf ProJumpcloudKandjiMicrosoft Entra M365OktaQualysRipplingSentineloneTenable IoTrinetWizWorkday

Control depth

Control Domains Mapped for Cyber Essentials

Each mapped control carries evidence specifications, test assertions, and implementation guidance. Overlapping controls are reused across frameworks.

17of 88
Aurora controls mapped
Coverage
19%
Control domains
6 domains
Access Control
5
Endpoint Security
4
Configuration Management
2
Vulnerability Management
2
Network Security
2
Governance
2

At a glance

What Teams Need to Know About Cyber Essentials

Best for

Teams aligning to a published standard without rebuilding controls and evidence for each review cycle.

Reviewers expect

Mapped requirements, linked evidence, approval history, and structured exports for Cyber Essentials reviews.

Where teams stall

Rebuilding control mappings and chasing evidence for each Cyber Essentials review cycle instead of reusing a current record.

Governed exports
  • Control matrix
  • Evidence package
  • Reviewer portal access
  • Audit-period exports

Lifecycle signals

How Aurora Keeps Cyber Essentials Current

Automated signals track evidence freshness, detect coverage gaps, and surface upcoming deadlines so teams stay ahead of review windows.

Evidence freshness tracking

Alerts when evidence artifacts approach expiration

Automation gap detection

Identifies controls without automated evidence collection

Training assignments

Links training requirements to framework controls

Assessment readiness

Tracks question coverage and approved answers

Calendar deadlines

Review window and renewal date tracking

Regulatory frameworks
Incident response timelines

Regulatory notification and response window tracking

Regulatory frameworks
Remediation tracking

Gap-to-fix workflows with owner assignment

Policy governance

Approval workflows, version tracking, and clause mapping

From request to handoff

How Teams Stay Review-Ready Between Cycles

Aurora turns one named framework request into a repeatable operating motion your team can maintain between audits, buyer reviews, and renewals.

01
Scope the exact version
Start with the Cyber Essentials version your reviewer or buyer already asked for so the record matches the request in front of you.
02
Reuse the controls you already trust
Map overlapping requirements to the same governed control library instead of rebuilding the program around one framework.
03
Keep proof current between cycles
Attach evidence with owners, freshness expectations, and reminders so the package stays current while the business keeps moving.
04
Capture approvals and decisions
Keep policy approvals, exceptions, and review history linked to the same record so reviewers see the operating context, not just files.
05
Hand off a clean reviewer package
Share structured access or export a scoped package with mappings, evidence context, and timestamps already intact.

Supported versions

Mapped Versions of Cyber Essentials

Latest
Requirements for IT Infrastructure v3.2 (active applied baseline on 2026-03-19; v3.3 preview not yet active)
Source
68
Requirements
17
Controls
36
Evidence
35
Tests
15
Sources
6
Domains
Framework request

Don't See Your Framework?

If a framework, regulation, or customer requirement is blocking your deal, bring it. We scope feasibility, assess overlap with your existing program, and map a rollout path, usually in one call.

Step 1
Share the requirement

Name the framework, version, and review timeline so we confirm scope before anything else.

Step 2
We assess the overlap

Your existing controls, evidence, and mappings in Aurora are compared against the new requirement to quantify what carries over.

Step 3
Get a clear answer

Leave the call with a feasibility decision, rollout timeline, and next steps. Not a follow-up form.

Common questions

Cyber Essentials Questions, Answered Plainly

How does this fit alongside the frameworks we already run?
Aurora maps each framework into the same governed control and evidence system, so teams expand coverage without rebuilding the entire record.
How quickly can we support the next review cycle?
Tell us about the framework version and review window you need to support. Aurora helps your team move from mapped controls to traceable proof without rebuilding the package from scratch.
What does the reviewer actually receive?
Reviewers get structured access to the mapped record, linked evidence, approvals, and point-in-time exports instead of a loose collection of attachments.
Does Aurora replace the auditor or assessor?
No. Aurora keeps the work current, traceable, and ready to share. Auditors, assessors, and regulators remain independent.

Aurora does not guarantee certification, audit outcomes, or reviewer decisions. It organizes, tracks, and shares the evidence and mappings your team maintains.

Live walkthrough
Preparing for Cyber Essentials review?
Share the version your reviewer asked for. We will show how Aurora maps Cyber Essentials into your existing control library, keeps evidence current, and gives reviewers a clean handoff.
15-minute walkthrough. No obligation. See Aurora applied to your workflow with the exact outputs reviewers receive. (No compliance guarantees.)