Settings
Read-only in this demonstration build — there is no authentication, storage or integration, so nothing on this page can be changed or saved.
Organisation profile
Synthetic organisation used for every page
- Name
- Halcyon Freight Group Ltd (DEMO)
- Sector
- Logistics & Distribution
- Region
- United Kingdom
- Staff
- 1,240
- Microsoft 365 tenant
- halcyonfreight.onmicrosoft.demo — fictitious; not connected
Users & access
Authentication is not enabled
- Signed-in user
- Alex Morgan (Virtual CISO) — a demonstration identity, not an account
- Roles and permissions
- Not available — every visitor sees the same synthetic data.
- Tenant isolation
- Not applicable — a single synthetic organisation; no customer data.
- Audit log
- Not available — no user actions are recorded.
Integrations
No source is connected. Evidence references such as “Defender device inventory (DEMO)” describe synthetic exports, not ingested data.
| Source | Would provide | Status |
|---|---|---|
| Microsoft Entra ID | Users, roles, Conditional Access, sign-in and audit logs | Not connected |
| Microsoft Defender XDR | Device inventory, vulnerabilities, incidents, Secure Score | Not connected |
| Microsoft Intune | Device compliance and configuration profiles | Not connected |
| Microsoft Defender for Cloud | Azure resources, recommendations and plans | Not connected |
| Microsoft Sentinel | Connector health, analytics rules and incidents | Not connected |
| ITSM (e.g. ServiceNow) | Remediation tasks and status history | Not connected |
Assessment data
Loaded with the application; stored nowhere else
- Assessments
- 6 monthly snapshots, 31 May 2026 – 31 Oct 2026
- Evidence catalogue — registered
- v1.0 (in force from 1 May 2026) · v2.0 (in force from 1 Nov 2026) · v3.0 (in force from 1 Dec 2026)
- Evidence catalogue — previews
- v4.0, v5.0, v6.0 — proposals only, not registered or applied
- Uploads
- Simulated — files are not stored or parsed.
- Reports
- Generated in the browser and printed with the browser’s print dialogue; no report archive.
Methodology & data basis
The standards every page applies
- Cyber Risk Index
- 0–100, higher is worse. Bands: Managed < 30, Elevated 30–44, High 45–59, Severe ≥ 60. Inputs include assessor ratings.
- Evidence Coverage
- Controls whose required datasets are all complete, using the catalogue version in force on the assessment date. A statement about evidence, not implementation or effectiveness.
- Technical verification
- Outcome confirmation is an assessor-recorded determination of what the export shows, made against synthetic demonstration data — not automated validation of the export contents.
- Exports with warnings
- An “Accepted with warnings” export is eligible only where its recorded warning does not undermine the specific outcome being confirmed. Acceptance is not, on its own, proof that the remediation is effective.
- Closure and approval
- Closure dates are preserved from the register. Formal closure approval evidence is not recorded and is never inferred from action completion.
- Statement types
- Source evidence, assessor-reported, inferred, hypothetical and not assessed are labelled separately on every page.
- Governance records
- Only decisions with a recorded date count as formally recorded. Outstanding decisions with an unknown recording date are shown as requiring management attention. Open the decision register