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 risk core looks genuinely usable for someone who inherited this job: protection-requirement analyses with automatic inheritance into the infrastructure, threat assessment, and measures with named owners, deadlines and automatic email reminders, on a BSI IT-Grundschutz 200-Standards backbone, with incidents documented ISO- and NIS2-conform and assets assigned. We found no public information on statutory reporting clocks (24h/72h) or a risk-acceptance step with ownership, which is what separates this from a certifier-grade register. 5 1 2