Risk acceptance record
A register for accepted security risks: the risk, its business owner, compensating controls, residual risk, the approver, and an expiry and review date on every row.
A risk acceptance turns a known gap into a decision with a name, a date, and an end. The record is written for its second reader: the person reconstructing the decision after something has gone wrong, who needs to see that the risk was understood, that controls were placed around it, that someone with authority approved it, and that it was due to be looked at again. Without an expiry an acceptance quietly becomes permanent, so every row carries one. This is a working record, not legal advice.
Preview
The first 3 of 3 rows, rendered from the same data the download is built from.
| Risk ID | Risk statement | Affected asset or process | Risk owner | Compensating controls | Residual risk (Low/Medium/High) | Reason for acceptance | Approver | Approval date | Expiry date | Next review date | Exit condition |
|---|---|---|---|---|---|---|---|---|---|---|---|
| blank | blank | blank | blank | blank | blank | blank | blank | blank | blank | blank | blank |
| RA-001 (example) | Legacy payroll application cannot enforce MFA for its local accounts | Payroll application | Head of Finance Systems | Access restricted to the finance network segment; local accounts reviewed monthly; failed logins alert the SOC | Medium | Replacement is contracted, and retrofitting MFA would cost more than the remaining life of the system | CFO | 2026-11-01 | 2027-05-01 | 2027-02-01 | Replacement live and legacy local accounts disabled |
| RA-002 (example) | Third-party SDK in the customer mobile app carries an unpatched medium-severity finding | Customer mobile app | Mobile engineering lead | Affected feature disabled by flag; dependency version pinned | Low | Fix is scheduled in the vendor's next release | VP Engineering | 2026-11-10 | 2027-02-10 | 2027-01-10 | Patched SDK version shipped to both app stores |
Formulas: Add a conditional format on Expiry date that highlights any row whose expiry is before today, and a column computing days until the next review. An expired acceptance is an unaccepted risk, so the highlighted rows are the agenda.
How to use it
- The risk owner is the person whose process carries the consequence, not the security team. Security writes the risk statement and recommends; the owner accepts.
- The approver needs authority over the budget or process that would remove the risk. If the approver could not have funded the fix, the acceptance sits at the wrong level.
- Every row has an expiry. Extending one is a new decision with a new approval date, recorded as a new row, not an edited cell.
- Write the exit condition as an observable event, such as a replacement system going live, so closing the row needs no judgment call.
- On each review date, check what changed: a new exploit, new data in scope, or a compensating control that stopped working. Any of those reopens the residual risk rating.
Changelog
- v1.0 (November 18, 2026):
- First release. Twelve columns, two worked example rows.
Common questions
- What should a security risk acceptance record contain?
- A specific risk statement, the affected asset, a named business owner, the compensating controls in place, the residual risk after those controls, the reason for accepting, the approver, the approval date, an expiry date, a review date, and the condition that closes the record. Expiry is the field most often left out, and it is what stops an acceptance becoming permanent.
- Who should approve a security risk acceptance?
- Someone with authority over the money or process that would remove the risk, usually a business executive rather than the security team. Security leaders describe the risk and recommend an option. When a security team approves its own exceptions, the record shows a decision taken by the party least able to fund the alternative.
- How long should a risk acceptance last?
- As long as the reason for accepting it remains true, and no longer than the next review cycle. Tie the expiry to the exit condition where one exists, such as a replacement going live. An acceptance with no end date has stopped being a decision, because nobody is ever asked to make it again.
Filed under The Record.