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 Skeptic
Automated asset discovery from cloud platforms, MDM tools and code repositories, with owners, regions and criticality metadata, asset-to-risk linking, and a risk register that syncs asset-linked risks is genuinely more than a spreadsheet import. But I found no public information on a documented risk methodology, treatment tracking, risk acceptance with ownership, protection-needs inheritance, or incident workflows with statutory reporting clocks — the core ISMS machinery is evidenced only at its edges. 3 4