5x5 Security Risk Register & Triage Worksheet
Score operational and security risks on a 5x5 likelihood-by-impact matrix, assign owners and treatments, enforce approval fields on accepted risks, and export CSV or PDF.
Practical 5x5 Scoring Without Indefinite Exceptions
A risk register filled with one-word entries like "Ransomware" rarely helps anyone decide what to fix next quarter. Each row here pairs a concrete scenario—the asset, how a failure or compromise happens, and what it costs the business—with a named owner, Likelihood (1-5), and Impact (1-5), producing a 1-to-25 score across Low (1-4), Moderate (5-9), High (10-15), and Critical (16-25) bands.
Assign Reduce, Avoid, Transfer, or Accept to each row. Picking Accept requires both a named executive approver and a review expiration date before export works, so accepted risks cannot sit forgotten for years.
Scope and Exports
This worksheet records one 5x5 score per row using the bands above rather than dual inherent-and-residual matrices, and holds rows in tab memory only until you leave the page. Export a formula-safe CSV, download a formatted PDF, copy plain text, or print.
House 5x5 Score Bands
Scores from 16 to 25 (Critical) mark high-likelihood, high-impact exposures that warrant immediate engineering work; 10 to 15 (High) mark material gaps scheduled into near-term sprints; 5 to 9 (Moderate) cover bounded operational risks tracked in normal planning; and 1 to 4 (Low) cover minor items revisited during scheduled reviews.
Related Guides and Services
Frequently Asked Questions
Why does Risk Acceptance require an approver and an expiration date?
Accepting a risk means leadership consciously decides not to spend engineering time or budget reducing it right now. Naming an authorized approver and setting an expiration date forces a fresh look once architecture or customer commitments change.
How should we write a clear risk scenario instead of a vague label?
Skip broad labels like "Cloud" or "Phishing" and describe the actual mechanism. For example: "Long-lived AWS IAM access keys shared across CI runners could let a compromised build job delete production S3 backups or read customer exports." That gives engineers a specific flaw to fix.
Are the 1-4, 5-9, 10-15, and 16-25 bands mandatory for SOC 2 or ISO 27001?
No audit standard prescribes exact numeric cutoffs. Assessors check that you define a clear scoring scale in your risk management policy and apply that same scale consistently across reviews.