Asset & risk management depth
How this is scored
The ISMS core: asset inventory, risk methodology (identification, assessment, treatment), protection-needs inheritance, incident handling with statutory clocks.
0 — No ISMS substance; "information security" is a chapter in the marketing site.
3 — A flat risk list and an asset spreadsheet import; no treatment tracking, no inheritance, incidents live in the ticket system.
5 — Asset and risk management with configurable matrices and treatment tracking; basic incident handling; inheritance and aggregation need manual work.
8 — A real risk backbone: documented methodology (ISO 27005 or equivalent), inherited protection needs across asset relations, incident workflows with statutory reporting clocks (NIS2 24h/72h), risk acceptance with ownership.
10 — Risk management a certifier works inside: complete asset-risk-treatment chain with inheritance, continuity planning, incident reporting with authority export, and risk reporting the executive level actually reads.
The Evidence Integrator
A structured asset register with owners, tags and visualised dependencies, risks linked to assets, a distribution matrix and mitigation tasks with owners form a real chain, and asset updates can be fed from Azure. But we found no public information on a documented risk methodology, inherited protection needs across asset relations, or incident workflows carrying statutory reporting clocks; incident handling shows up as configurable workflows rather than a clocked process. 8 9 3 16