Risk Register
Maintain visible operational risks, mitigation status, and ownership.
Purpose
Risk work should be specific enough to influence decisions. A risk statement should describe the event, the cause or condition, the impact, the owner, and the next treatment decision.
Operating record
| Cadence | Set a normal review interval and event-driven trigger. |
|---|---|
| Owner | Identify the role accountable for keeping risk register current. |
| Source data | List the systems, logs, reports, tickets, or records used during review. |
| Findings | Record exceptions, decisions, blockers, risk changes, and follow-up actions. |
| Evidence | Keep the smallest durable proof that the review occurred and produced a result. |
When to use
- When the work repeats often enough that memory is no longer reliable.
- When more than one person may request, perform, review, or inherit the work.
- When risk, approval, evidence, or handoff needs to be visible later.
Common failure modes
- Risk language is too vague to act on.
- Accepted risks are never reviewed.
- Mitigation tasks are not owned.
Review guidance
Review this page after a material incident, after a role or system change, and on a normal cadence appropriate to its risk. During review, check whether the owner is still correct, whether inputs are still complete, whether the output is still useful, and whether related pages need updates.
External guidance
These resources are references for terminology, control thinking, or review design. DailyWF adapts the ideas into lightweight operating pages rather than reproducing full standards.
- NIST Cybersecurity Framework 2.0General cybersecurity risk management structure: govern, identify, protect, detect, respond, recover.
- NIST SP 800-53 Rev. 5 control catalogSecurity and privacy control language useful when translating operating work into controls.