Asset & risk management depth
How this is scored
The ISMS core: asset inventory, risk methodology (identification, assessment, treatment), inheritance of protection needs (Schutzbedarf) across assets, and security incident handling with its reporting deadlines.
0 — Not an ISMS tool; the product has no asset or risk management.
3 — A risk register with likelihood and impact, and an asset list that can be imported.
5 — Asset inventory and risk management with a configurable risk matrix, risk treatment with owners and measures, and a register for security incidents.
8 — A documented risk methodology (ISO 27005, BSI 200-3 or equivalent), protection needs inherited across asset relations, incident workflows with the NIS2 reporting deadlines (24h/72h), and risk acceptance with named owners.
10 — Risk management a certifier works inside: the complete asset-risk-treatment chain with inheritance, business continuity planning (BIA, ISO 22301 or BSI 200-4), incident reporting with export for the authority, and risk reporting for the executive level.
The Skeptic
The cyber risk pages document risk prioritisation by likelihood, impact and velocity, a centralised risk library, and mapping of risks to strategic objectives and critical processes, and asset types and asset records are real objects in the developer data model. But we found no public information on a documented risk methodology, protection-need inheritance across asset relations, or incident workflows with reporting deadlines — the NIS2 presence we can verify is a landing page with a downloadable checklist, not an incident register. A credible risk register with an asset model, but the ISMS core beneath it is marketing territory. 3 4 5 9 8