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
There is a real asset bank feeding an asset inventory, a dynamic risk register with treatment, and a risk map you can genuinely shape — grid size, five default levels in plain words from Insignificant to Severe, additive or multiplicative scoring, review reminders at 1, 3, 6 and 12 months, all with sane defaults out of the box. Incidents sync from Jira and threats feed in as track items, so the register side feels live rather than a spreadsheet. We found no public information on protection needs inherited across asset relations, a named methodology such as ISO 27005, or NIS2-style 24h/72h reporting deadlines inside the incident workflow, which is where a regulated outfit would need it. 16 2 7 15