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
This is a genuine risk backbone: the Grundschutz domain captures target objects, threats, risks and measures, computes automatic protection-needs inheritance, and offers the Basis-, Standard- and Kernabsicherung paths a drafted officer like me can actually follow. The NIS2 domain names the statutory clocks — report after 24 hours, situation report after 72 — and adds supply-chain documentation and TOM capture. I found no public information on risk acceptance with named owners, which is the one piece of the chain the pages leave dark. 6 7 8