Risk acceptance form
A risk acceptance form is a signed record that a named approver accepts a stated residual risk until a stated expiry date. This one has 15 fields: 13 for every finding, plus a vendor field and a PCI field when they apply. Each field traces to NIST, FedRAMP, CISA or PCI SSC text read on 19 Nov 2026.
On this page
The form in full
Copy the text below or download it as Word or PDF. Fill it in, have the approver sign and date it, and write an expiry date before anyone files it. A filled-in copy is on the worked example.
- Risk Acceptance Form (.docx)
- Risk Acceptance Form (PDF)
- Blank exception register (CSV)
- Form fields (CSV)
- Form fields (JSON)
Risk Acceptance Form
Form version 1.0, first published 19 Nov 2026. License: CC BY 4.0. Cite as: Remediation vs Mitigation, Risk Acceptance Form, 19 Nov 2026, remediationvsmitigation.com/risk-acceptance-form/.
Write no exploit steps, payloads or probing instructions in this record.
A. The finding
Field 1. Exception ID (your own number): ________
CVE ID(s) and scanner finding ID(s) covered: ________
Field 2. First detected (date, time, tool or report): ________
Evaluation completed (date, time): ________
B. Where it sits and how likely it is to be used
Field 3. Asset(s) or system ID(s): ________ Environment: [ ] prod [ ] dev Exposure: [ ] public [ ] internal Asset type: [ ] server [ ] application [ ] network device
Field 4. Internet-reachable? [ ] yes [ ] no Basis (test or architecture drawing): ________
Field 5. Likely exploitable? [ ] yes [ ] no Reason: ________ On the CISA KEV catalog? [ ] yes [ ] no Catalog version checked: ________
Field 6. Estimated impact if exploited, on your own scale: ________
C. The decision
Field 7. Why this is accepted instead of fixed or mitigated: ________
Field 8. Mitigating factors and compensating controls in place (control, owner, how verified, date verified, entry link): ________
Field 9. Plan: corrective tasks, owner of each task, resources, milestones, scheduled completion dates: ________
Field 10. Reopen this record when: ________
Review every ____ days. Next review: ________
Field 11. Residual risk after the controls (one sentence) and the risk tolerance it is compared with: ________
Field 12. Only if the fix depends on a vendor: product, vendor status evidence, last vendor check-in date, next check-in date: ________
D. Decision and expiry
Field 13. Approver name, title, signature, date: ________
Statement: "I accept the residual risk in Field 11 until the date in Field 14."
Field 14. Expiry date. The exception lapses on this date unless the approver renews it in writing: ________
E. Only if PCI DSS applies
Field 15. Compensating control worksheet: attach the worksheet your QSA uses, and name the PCI DSS requirement it stands in for: ________
What goes in each field and why it is there
A field is on the form only where a source read on 19 Nov 2026 asks for it. Fields a team might add for its own reasons are left off. Fields 12 and 15 are conditional; the other 13 are asked of every finding.
| No. | Field | What goes in it | The wording that asks for it |
|---|---|---|---|
| 1 | Exception ID, CVE IDs, finding IDs | One internal number for the exception, then every CVE and scanner finding it covers. The CVE list is what lets a later KEV listing find this record. | FedRAMP VER-RPT-AVI: "Provider's internally assigned tracking identifier". FedRAMP's 27 Jun 2022 POA&M template update added column AD, "CVE", for the CVEs on each line item. |
| 2 | Detection and evaluation | Date, time and tool or report of the first detection, then date and time the evaluation finished. Two timestamps, because a clock such as FedRAMP's 192 days runs from evaluation. | VER-RPT-AVI: "Time and source of the detection" and "Time of completed evaluation". |
| 3 | Asset, environment, exposure | Hostnames or system IDs, prod or dev, public or internal, and the asset type (server, application or network device). | CISA BOD 26-04 asset tags: "Environment (prod/dev)", "Exposure (public/internal)", "Asset type (server, application, or network device)". |
| 4 | Internet-reachable | Yes or no, and the basis: a test or an architecture drawing. Reachable means a payload from the internet can arrive at the vulnerable part, including through a load balancer, so internal-only is not enough of an answer. | VER-RPT-AVI: "Is it an internet-reachable vulnerability or not?" VER-EVA-EIR notes that FedRAMP "focuses on internet-reachable (rather than internet-accessible)" and uses SQL injection behind a load balancer as its example. |
| 5 | Likely exploitable; KEV status | Yes or no with the reason, KEV yes or no, and the catalog version you checked. If you cannot show that exploitation cannot be automated, write that automation is assumed. | VER-RPT-AVI: "Is it a likely exploitable vulnerability or not?" VER-EVA-AIA: "Providers MUST assume the exploitation of vulnerabilities can be automated UNLESS they have evidence proving otherwise." BOD 26-04 lists "KEV Status" as a variable. |
| 6 | Estimated impact if exploited | A rating on your own scale, with the reason in a clause. FedRAMP's scale has six levels, N0 ("extremely unlikely to have any adverse effects") to N5 ("a debilitating customer effect on more than one agency"). | VER-RPT-AVI: "Currently estimated Potential Agency Impact N-rating"; the levels are defined in VER-EVA-EPA. |
| 7 | Why accepted | The constraint in plain words: no vendor fix yet, a patch that breaks a system, a retirement date. Add anything that helps the approver judge the risk. | VER-RPT-AVI: "Explanation of why this is an accepted vulnerability", and supplementary information that helps assess or mitigate the risk. NIST SP 800-39: "Risk acceptance is the appropriate risk response when the identified risk is within the organizational risk tolerance." |
| 8 | Mitigating factors and compensating controls | For each control: what it is, who owns it, how it was checked, the date checked, and a link to its control entry. Link rather than describe, so a change to the control updates one record. | NIST SP 800-37 Rev. 2, Task R-2: plans contain "an accurate description of implemented controls, including compensating controls". FedRAMP legacy POA&M playbook: "CSPs must describe mitigating factors or compensating controls in place that reduce likelihood and/or impact of exploitation." |
| 9 | Plan | The tasks that end the exception, an owner for each, the resources needed, milestones and dates. At least one task must be the fix or the decision to replace. | SP 800-37 Rev. 2, Task A-6: the plan includes "the scheduled completion dates for the milestones and tasks". SP 800-53 Rev. 5, CA-5 a: "document the planned remediation actions of the organization". |
| 10 | Reopen triggers and review cadence | The events that reopen the record (scan result, audit, monitoring finding, change in exposure, new KEV listing, vendor fix released), a number of days between reviews, and the next review date. | CA-5 b: update the plan "based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities". SP 800-40 Rev. 4, Section 3.5.5: "All exceptions to maintenance plans should be reviewed regularly". |
| 11 | Residual risk against tolerance | One sentence on what risk remains once the controls hold, and the stated tolerance it is compared with. See residual risk after mitigation. | SP 800-37 Rev. 2, Task R-3: "regardless of the risk response, there remains a degree of residual risk". SP 800-53 Rev. 5, RA-7: respond to findings "in accordance with organizational risk tolerance". |
| 12 | Vendor dependency | Only when the fix waits on a vendor: product, evidence of the vendor's status (advisory, vendor email), last check-in date and next check-in date. | FedRAMP legacy POA&M playbook: "CSPs are required to check in with the vendor at least once a month"; "Do provide evidence of vendor interactions regarding the status of patches/fixes (e.g., vendor notifications, email exchanges, etc.)." |
| 13 | Approver | Name, title, signature, date and the acceptance statement. The person who asked for the exception does not sign it; see who is the risk owner. | SP 800-37 Rev. 2, Task R-4: "The explicit acceptance of risk is the responsibility of the authorizing official and cannot be delegated to other officials within the organization." |
| 14 | Expiry date | The date the exception lapses unless the approver renews it in writing. See risk exception expiry. | SP 800-37 Rev. 2: "The authorization termination date is established by the authorizing official and indicates when the authorization expires." |
| 15 | PCI compensating control worksheet | Only when PCI DSS applies: attach the worksheet your Qualified Security Assessor uses and name the requirement it stands in for. | PCI SSC FAQ 1046: assessors "are responsible to determine whether a compensating control is sufficient to meet the intent of a requirement". FAQ 1597 defines "addressed" as deciding whether to resolve a vulnerability or mitigate the risk "in another way (e.g., with a compensating control or by disabling a vulnerable service)". |
Three fields where the sources differ
Expiry (field 14). NIST leaves the date to the authorizing official and allows no date at all: "Organizations may eliminate the authorization termination date if the system is operating under an ongoing authorization" (SP 800-37 Rev. 2, Task R-4). FedRAMP's 2026 rule sets no expiry; it sets a reporting trigger, 192 days from evaluation, after which an unfixed finding must be categorized as accepted (VER-TFR-MAV). The form asks for a date because an exception with no end is the case no source allows by default; what each source allows is on maximum durations.
Review cadence (field 10). CA-5 b leaves the update frequency to the organization, and SP 800-40 Rev. 4 says only "reviewed regularly". The form asks for a number of days and a date, which is stricter than either.
Vendor check-in (field 12). The monthly interval comes from the FedRAMP legacy POA&M playbook. FedRAMP's two 2026 rule pages on vulnerabilities (evaluation and reporting, detection and response) set no vendor check-in interval. Keep the monthly check-in as a convention, not as a current FedRAMP requirement.
What stays out of the record
FedRAMP's disclosure rule draws the line a record should follow: providers "MUST NOT irresponsibly disclose specific sensitive information about vulnerabilities that would likely lead to exploitation, but MUST disclose sufficient information for informed risk-based decision-making" (VER-RPT-NID). Fields 4, 5 and 7 should say whether the flaw is reachable and likely to be used, and why, without payloads, request samples or step lists.
What signing does not change
Signing the form does not move a federal civilian agency's due date. CISA's BOD 26-04 implementation guidance answers the waiver question directly: "CISA does not issue waivers or exceptions for actions required in cyber directives." The Decision Table row for a missed KEV due date shows what to do instead.
For PCI DSS, the form is not the compensating control worksheet. PCI SSC says it "is not able to approve specific configurations or compensating controls" (FAQ 1046); a Qualified Security Assessor judges them. See the PCI row of the Decision Table. Related guide: inherent versus residual risk for fields 4 to 6 against 11.
Sources
- FedRAMP Consolidated Rules for 2026, Vulnerability Evaluation and Reporting (VER-RPT-AVI, VER-RPT-NID, VER-EVA-EIR, VER-EVA-AIA, VER-EVA-EPA, VER-TFR-MAV), read 19 Nov 2026
- FedRAMP Consolidated Rules for 2026, Vulnerability Detection and Response, read 19 Nov 2026
- FedRAMP, Update to the POA&M template, 27 Jun 2022, read 19 Nov 2026
- FedRAMP legacy documentation, Plans of Action and Milestones, read 19 Nov 2026
- NIST SP 800-37 Rev. 2, Tasks A-6, R-2, R-3, R-4, read 19 Nov 2026
- NIST SP 800-39, Task 3-1, risk acceptance, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Section 3.5.5, read 19 Nov 2026
- NIST SP 800-53 Rev. 5, CA-5 and RA-7 (OSCAL catalog), read 19 Nov 2026
- CISA, BOD 26-04, asset tags and variables, read 19 Nov 2026
- CISA, BOD 26-04 implementation guidance, waiver question, read 19 Nov 2026
- PCI SSC, FAQ 1046, approval of compensating controls, read 19 Nov 2026
- PCI SSC, FAQ 1597, resolving or addressing vulnerabilities, read 19 Nov 2026
Last reviewed