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 backbone is documented and real: the risk analysis is stated to fulfil BSI-Standard 200-3 and 100-3 with measure proposals via cross-reference tables, Grundschutz and BCM risk results can flow together in one tool down to IT implementation, and a protection-needs determination exists in the data protection module. We found no public information on incident workflows with statutory reporting clocks or on risk acceptance with named ownership, which keeps it below the top band. 3 2 7 8