Guide
Cybersecurity Risk Register Template
A cybersecurity risk register should connect a plausible loss scenario to evidence, a treatment decision, accountable owners, and the proof needed to revisit or close it. Use the copyable outline and fictional example below as a practical starting point, then adapt the fields and rating method to your organization.
What a cybersecurity risk register is
A cybersecurity risk register is the working record of risk scenarios that require treatment, monitoring, or an explicit acceptance decision. A useful row explains what could happen, why it could happen, what the organization knows, what remains uncertain, who is accountable for the decision, and when the risk will be reviewed again.
This guide is a practical adaptation of risk-register concepts in NIST Interagency Report 8286A Revision 1 and the prioritization and response concepts in NIST IR 8286B. Those publications address integrating cybersecurity risk information with enterprise risk management. This starter template is not an official NIST form and does not replace an organization’s required risk method.
For a worked report that carries evidence from a finding into an executive summary and action plan, see the cyber risk assessment report example. The register here serves a different job: maintaining risk decisions and follow-up across reviews.
Copyable risk register outline
Use one row per risk scenario. Keep supporting evidence in an access-controlled repository and reference it from the register rather than pasting secrets, personal data, or sensitive configurations into the row.
| Field | What to record |
|---|---|
| Risk ID and title | A stable identifier and a short scenario-based name |
| Scenario and cause | A concise “because / event / consequence” statement: the condition or threat, the event that could occur, and why it is plausible |
| Business impact | The affected service, data, obligation, revenue process, customer outcome, safety concern, or strategic objective |
| Scope | Systems, accounts, data, business process, locations, and time period covered; name important exclusions |
| Existing safeguards | Controls that reduce likelihood or impact, including their current verification status |
| Evidence and date | Dated records that support the scenario, such as listings, configurations, tests, incidents, interviews, or contracts |
| Uncertainty and open questions | Missing evidence, sampling limits, disputed assumptions, and facts still to verify |
| Likelihood | Rating or estimate under the organization’s defined method, with rationale |
| Impact | Rating or estimate under the organization’s defined method, with rationale |
| Current risk | Combined rating or quantified result, with the method and version used |
| Response | Mitigate, transfer, avoid, accept, or another response allowed by policy; include rationale |
| Accountable risk owner | Business role accountable for the risk decision and residual exposure |
| Action owner and plan | Person responsible for each treatment task, dependencies, target, and status |
| Next review | Date or trigger for reassessment, such as a control test, material system change, incident, or contract milestone |
| Closure evidence | Specific proof needed before the row can be closed, merged, or retired |
| Expected residual risk | Exposure expected after planned actions, including assumptions |
| Acceptance reference | Link or identifier for the separate approved exception or acceptance record when residual risk is accepted |
A spreadsheet is enough to start if it preserves stable IDs, ownership, dates, and history. A governance, risk, and compliance platform may help at larger scale, but software does not decide whether the scenario, evidence, or response is sound.
Write the scenario before assigning a score
Avoid rows such as “MFA risk” or “backups: high.” They name a topic but not a decision. A scenario should connect three parts:
Because [condition or cause], [threat event] could occur, resulting in [business impact].
For example:
Because several engineers use one release credential and the system does not reliably attribute its use, an unauthorized or mistaken release could reach production without a dependable operator record, resulting in service disruption, investigation delay, or an unverified change to customer-facing code.
The scenario still needs evidence. Do not turn a plausible concern into an observed fact. If the team has not yet checked credential assignment or release logs, mark those facts as unverified and assign an evidence action.
Separate evidence from uncertainty
Risk registers become misleading when every sentence sounds equally certain. Use the evidence field for what was actually observed and the uncertainty field for what the review could not establish.
Evidence might include:
- an identity or permission listing captured on a stated date;
- configuration settings reviewed from an approved source;
- a restoration test result and its scope;
- an incident or change record;
- a contract clause or customer requirement; or
- an interview that still requires corroboration.
Uncertainty might include unreviewed service accounts, incomplete logs, a sample that covers only one environment, or a business-impact estimate that has not been confirmed by the process owner. The risk rating should reflect those limits rather than hide them.
Rate likelihood and impact separately
Likelihood asks how plausible or frequent the scenario is under current conditions. Impact asks what happens if the scenario occurs. Define both scales before applying them. A “high” rating is not portable between organizations unless the thresholds mean the same thing.
Do not let a combined score erase the rationale. Two risks can share a score while requiring different decisions because one threatens a critical customer service and the other affects a recoverable internal process. Keep the business impact, assumptions, and decision visible next to the rating.
If inputs are too uncertain for a defensible score, use a provisional rating and state what evidence is needed to improve it. False precision is not an improvement over honest uncertainty.
Fictional filled risk example
This example is fictional and uses simulated evidence. It demonstrates field relationships, not a recommended rating for every company.
| Field | Fictional example RR-014 |
|---|---|
| Risk ID and title | RR-014 — Shared release credential obscures production changes |
| Scenario and cause | Because a shared release credential can be used outside the normal deployment identity, an unauthorized or mistaken release could reach production without reliable attribution, causing service disruption or delaying investigation. |
| Business impact | Customer-facing SaaS availability, release integrity, contractual incident handling, and engineering response time |
| Scope | Production deployment credential and the primary application pipeline. Emergency infrastructure access and third-party CI service administration are excluded pending review. |
| Existing safeguards | Normal code changes require peer review. Deployment logs record time and artifact, but the shared credential does not identify the individual operator. |
| Evidence and date | Fictional review on October 28: credential inventory shows one shared release credential; pipeline export shows it can invoke production deployment; sample of 20 normal releases shows peer approval. |
| Uncertainty and open questions | No evidence of misuse was found in the sample. The review did not establish how the credential’s recovery material is accessed or whether all uses appear in the central alert stream. |
| Likelihood | Medium, provisional: access is limited, but individual use is not attributable and the recovery path is unverified. Apply the company’s defined scale. |
| Impact | High, provisional: a production release can disrupt customer service or introduce an unreviewed change. Legal and revenue effects require confirmation by business owners. |
| Current risk | High under the fictional company’s matrix; do not reuse this rating without applying your own criteria. |
| Response | Mitigate by replacing routine use with named, short-lived deployment identities; restrict the shared credential to a documented recovery path; alert on every use; test attribution. |
| Accountable risk owner | VP Engineering |
| Action owners and plan | Platform Lead: named deployment identities. Identity Lead: recovery access and custodians. Security Lead: alert and test procedure. |
| Next review | Review after the attribution test or by November 30, whichever comes first; reassess after any unapproved release event. |
| Closure evidence | Shared credential cannot perform routine deployment; an approved recovery test identifies the operator, creates an alert, and links to a reviewed change or incident record. |
| Expected residual risk | Emergency credential misuse remains possible, but named custodians, restricted use, alerting, and review reduce likelihood and investigation delay. Re-rate after testing. |
| Acceptance reference | None. If leadership accepts a temporary exception, record it in the separate acceptance ledger with scope, rationale, approver, expiry, safeguards, and review trigger. |
Risk owner and action owner are different jobs
The accountable risk owner is responsible for bringing the decision to the right level. They can approve a response or accept residual exposure within their delegated authority. Escalate decisions that exceed those limits. Choose an owner who understands the affected business outcome. Security can help evaluate the risk and recommend a response.
An action owner completes a defined task. RR-014 has one accountable risk owner and three action owners. Completing one action does not close the row. The risk owner reviews the evidence and records or escalates the next decision according to company policy.
Link accepted exceptions to a separate ledger
A risk register describes the scenario and treatment. An acceptance or exception ledger records a specific authorization to live with stated residual exposure for a defined scope and period. Keep them linked but separate so a temporary exception does not overwrite the underlying risk history.
An acceptance record should identify:
- the related risk ID;
- the exact scope and business rationale;
- safeguards that remain in place;
- the accountable approver;
- the start, expiry, and next review dates; and
- the conditions that cancel or reopen the decision.
The risk acceptance guide and ledger example explains that governance record. Do not treat an expired acceptance as continuing approval.
Review, re-rate, and close with evidence
Review the register when a scheduled date arrives and when material evidence changes. Common triggers include a control test, system launch, acquisition, incident, major vendor change, customer commitment, or discovery that an earlier assumption was wrong.
Before closing a row, confirm that the stated closure evidence exists and has been reviewed. Then record the final residual risk and the decision. If the scenario remains plausible but falls within approved tolerance, the result may be an accepted or monitored risk rather than a closed one.
A vCSO.ai scoped Cyber Risk Assessment can review agreed evidence, document findings, and turn priorities into an action plan with owners and dependencies. Your organization retains its risk decisions; implementation, specialist work, and ongoing register administration depend on the agreed scope.
Questions & answers
What should a cybersecurity risk register include?
What is the difference between a risk owner and an action owner?
When should a cyber risk be closed?
Ready to turn this into a working plan?
Our team helps growth-stage companies, PE/VC sponsors, and cybersecurity product teams translate security questions into board-ready decisions. First call is strategy, not vendor pitch.