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
I got handed this job by an email, and the first thing I hunt for is a risk register — I found no public information on a risk methodology, treatment tracking, incident reporting deadlines, or an asset inventory beyond automatic asset discovery in Google Cloud. Incident handling shows up as alert routing from tools like Zenduty, Incident.io and Jira Active Sync, which is the ticket system doing the job, not a workflow with clocks on it. 4 6