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 Drafted IT Officer
Assets are recorded and classified by their protection needs, risks run through configurable assessment methods with target-versus-current scoring and re-assessment after a measure is implemented, and incidents plus emergency scenarios and drills each get their own module. The business impact analysis with process dependencies, recovery times and configurable damage scenarios that also ship with a standard configuration is exactly the sane-defaults depth I want for a day job. We found no public information on protection-need inheritance across linked assets or the 24-hour and 72-hour NIS2 reporting deadlines inside the incident workflows. 7 9 2