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 Skeptic
The BSI methodology is implemented as real objects — targets, requirements, measures, threats, risks — with automatic protection-needs inheritance and supporting structural analysis, and the NIS2 domain carries the statutory clocks (report after 24 hours, situation report after 72 hours, final report after one month). Risk management per NIS2 Article 21 is documented as integrated into both the Grundschutz and ISO 27001 domains. We found no public information on risk acceptance with named ownership or executive-level risk reporting. 6 7 8