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 GRC Consultant
The risk methodology is real — the documented ISO 27005 lifecycle with pre-built scenarios, automatic owner assignment, quarterly reviews and a full audit trail, plus asset discovery with owners, classification and in/out-of-scope tracking, sits well above a flat spreadsheet. But I found no public information on incident handling with statutory reporting clocks, on protection needs inheriting across asset relations, or on risk-acceptance decisions with ownership, and for my book of clients that is the half of the ISMS that decides whether the tool earns its keep. 2 3 5