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 Drafted IT Officer
The chain from catalogued assets with CIA classifications through structured assessments to treatment plans natively linked to Annex A controls is on the product pages, and incidents get automated workflows with escalation — more than the spreadsheet I would have built. But I found no public information on inherited protection needs across asset relations, a documented risk methodology, or statutory reporting clocks like the NIS2 24/72-hour deadlines, so it stays below the certifier-grade band. 5 6 8