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 Lead Auditor
The risk module identifies, classifies and treats risks with mandatory owners and review dates, untreated items are recorded as documented decisions with owners and expiry, and incidents run a full lifecycle from detection through lessons learned. We found no public information on an asset inventory with inherited protection needs, a documented risk methodology, or incident workflows carrying the statutory NIS2 24h/72h reporting clocks — which is what separates working risk tooling from the backbone a certifier works inside. 5 6