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
Central assets with visual Schutzbedarf determination and matrices that fit my methodology, plus revision-safe incident workflows with task assignment — that's the Grundschutz-flavoured backbone I can actually follow, from a licensed BSI IT-Grundschutz tool vendor. But the evidence is silent on NIS2 24h/72h statutory clocks, risk acceptance with named ownership, and protection-need inheritance across asset relations (only tenant inheritance is evidenced), so it sits between rubric level 5 and 8. 1 2