Home
Pick the right workspace
Start by choosing a client. Home should answer the basics quickly: devices, Cyber Essentials readiness, security findings, proof confidence, and the next useful action.
No client selected yet.
Director verdict
—
Plain-English view of whether this client looks unproven, improving, or ready for review.
What this means
A short board-style summary of position, trust, and pressure.
This week
The shortest safe route to a cleaner, more shareable story.
Cyber Essentials readiness
—
How close the client is to a clean CE story.
Devices
—
Known and reporting devices.
Open issues
—
Control gaps and vulnerabilities.
Proof confidence
—
Whether the score is backed by evidence.
Today
—
The plain-English state of the active workspace.
This week
—
The shortest useful step from here.
Rollout status
—
Installer, check-in, and first proof.
What matters now
What to do next.
Launch path
How to get telemetry and source-of-truth flowing.
Follow-through queue
Ownership, due pressure, and nudges for the active workspace.
Owners
Who currently holds the open approvals and evidence follow-up.
Switch workspace
Move between platform and client views without guessing.
Mission control
Choose the right workspace
This view is designed to help you move from device truth to Cyber Essentials-ready evidence without getting lost in admin noise.
No workspace selected yet.
Readiness
—
The benchmark state appears here once the workspace loads.
Evidence
—
Coverage and proof quality in one quick read.
Devices
—
Reporting state and key device names will appear here.
Security findings
—
Open critical and high pressure in the current workspace.
Best next move
—
The calmest useful next action will appear here.
Stage 1
Workspace locked
Pick the client scope you actually want to work in.
Stage 2
Devices proving
Make sure reporting devices tell a believable operational story.
Stage 3
Checklist closing
Turn missing or weak controls into cleaner proof paths.
Stage 4
Report ready
Use Reports & Sharing once the story is fit to hand over.
Cyber Essentials mission control
Keep the benchmark, evidence stack, and handover story aligned
Select a client scope to see the current Cyber Essentials posture, evidence confidence, and assessor readiness in one place.
Selected benchmark
Cyber Essentials
Awaiting scope
Last verified: —
Readiness
—
Evidence-backed control readiness
Evidence confidence
—
Freshness, coverage, and corroboration
Trust Centre
—
Assessor-shareable governance output
Path to pass
Scope, evidence stack, controls, and handover readiness.
Onboarding Hub
Simple, fast onboarding for admin and MSP teams. Advanced tasks stay in Settings -> Onboarding / Provisioning.
Create MSP
Admin onlyIf left blank, an ID is generated automatically.
Create Client
Admin / MSPDeploy Agent Bundle
Admin / MSPChoose the client, then generate a token or download the full onboarding bundle.
Admin View Switching
Admin onlySwitch the portal into MSP/client views for testing and demos without changing backend permissions.
Tip: Select MSP/client in the sidebar switcher, then click Apply view.
Client launch
Onboarding and source selection
Launch the client quickly, then connect the minimum evidence stack for credible readiness scoring.
Treat onboarding as a guided launch plan: scope the client, prove one reporting endpoint, connect the right source-of-truth, then generate the first CE story.
First client journey
Move from empty tenant to assessor-ready operating view
Start with the smallest defensible evidence stack. We only need enough connected proof to tell an honest Cyber Essentials story, then we can expand depth later.
Stage 1
Create scope
Create the MSP/client record, switch into the right view, and lock the benchmark scope.
Stage 2
Prove a device
Deploy the installer bundle and confirm at least one endpoint is actively reporting.
Stage 3
Connect authority
Add the minimum source-of-truth integrations needed for this client’s environment shape.
Stage 4
Prepare review
Run readiness, close obvious gaps, and generate the first CE autofill draft for review.
Minimum launch outcome
- One client in scope
- One reporting endpoint
- One trusted source-of-truth path
- One CE review run completed
What this unlocks
- Readiness that means something
- Controls with evidence provenance
- Manual queue with guided attestation
- Assessor-style handover output
Create an MSP
Provision the top-level tenant.
Create a client
Attach a client under the MSP.
Generate installer bundle
Download the MSI + token bundle.
Enroll an endpoint
Install agent and see it appear.
Source-of-truth baseline
Essentials relies on integrations + manual evidence. Assurance layers telemetry on top for stronger confidence and freshness.
Launch command
See whether this client can move from setup into Cyber Essentials review
This board keeps scope, device proof, source authority, and review readiness in one lane so the first-launch journey stays clear for operators and assessors.
Preparing launch workspace…
Launch state
—
The launch board fills once scope and client state are available.
Reporting proof
—
At least one live endpoint turns setup into a provable CE story.
Authority stack
—
Required integrations or truth sources connected for this client shape.
Review pack
—
Release stage, autofill coverage, and remaining manual proof.
What is happening in this first-launch path
The launch story appears once client state is loaded.
Signals worth trusting
Scope, endpoint proof, source authority, and review evidence in one place.
Recommended next moves
Jump straight into the next stage without losing the launch story.
First client launch checklist
Where this client is in the launch journey
Scope, reporting, authority, and review readiness in one place.
Awaiting client scope
Executive summary
Evidence-backed readiness snapshot (not certification)
Overview command
See what deserves attention before you read the dashboard cards
This lane separates benchmark gaps, evidence confidence, raw exposure, reporting coverage, and review readiness so first-time operators know where to go next.
Preparing executive workspace…
Operating state
—
The overview command board fills once the dashboard state is loaded.
Evidence confidence
—
Coverage, freshness, and automation depth for the active benchmark.
Exposure pressure
—
Control gaps, raw findings, and device-level security pressure.
Coverage lane
—
Reporting devices, source authority, and the route into review.
What is happening in this client workspace
The overview story appears once benchmark and environment state are loaded.
Signals worth trusting
Confidence, source authority, exposure, and release posture in one place.
Recommended next moves
Take the shortest route to a cleaner readiness story.
Readiness indicator
—
Freshness: —
Last verified: —
Environment overview
Devices monitored—
Devices not reporting—
Evidence coverage—
Integrations connected—
Frameworks active—
Browser compliance—
AV presence—
Integration status
Evidence trace
—Active framework: —
Evidence recency: —
Top control gaps
—Devices not reporting
—Evidence & readiness detail Confidence, coverage, risks, and source breakdowns
Telemetry posture
—
—
Evidence coverage
—
Controls with evidence: —
Evidence freshness
30d —
60d —
90d —
Evidence confidence
—
—
Confidence trend
30d —
60d —
90d —
Client & plan
—
Plan: — · Tier: —
Endpoints: —
Benchmark focus
—
Active: —
—
Key gaps to close
—
Top risks
—
Risk heat map
Evidence sources in use
Next evidence actions
Recommendations
Executive snapshot history
Last 3 snapshots (local)
—
Environment overview
Scope: —
Updated: —
Telemetry posture
—
—
Benchmark readiness
—
—
Compliance coverage
—
—
Benchmarks active
—
—
Devices monitored
—
—
Integrations connected
—
—
Telemetry posture uses alert rates. Benchmark readiness is evidence-backed. Evidence coverage shows how much of the benchmark has evidence.
View evidence coverage
Trend strip
Trend data appears after a few snapshots. Use Refresh data to start.
Telemetry (7d)
—
Evidence (30d)
—
Endpoints (30d)
—