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
Enterprise Risk shows a real risk engine — risk matrix scaling up to Monte Carlo simulation, treatment choices covering avoidance through acceptance, interdependency analysis, and automated action tracking with reminders — and Technology Risk Management ties applications to business processes with business-criticality ratings. What I found no public information on: incident workflows with statutory reporting clocks such as NIS2's 24/72-hour deadlines, protection-needs inheritance across asset relations, or a named risk methodology. The risk half looks genuinely operable for a one-person security office; the incident half is a question mark I'd have to raise in the demo. 2 3 5