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
Assets are catalogued with CIA classifications, treatment plans link to controls and obligations, incidents are logged with automated escalation, and the risk lifecycle is configurable — the working core is all evidenced. We found no public information on inherited protection needs across asset relations, statutory reporting clocks like NIS2 24h/72h inside incident workflows, a named methodology such as ISO 27005, or risk acceptance with named ownership. That lands this between solid asset-and-risk operability and the certifier-grade backbone the top of the scale describes. 5 6 8