# Who can accept risk in cybersecurity

Canonical: https://remediationvsmitigation.com/risk-acceptance-form/who-may-sign/

In US federal systems only the authorizing official can accept risk, and NIST SP 800-37 says the decision cannot be delegated. PCI SSC approves nothing; an assessor judges. CISA grants no waivers. Any other organization names its signer in its own written policy, and a sample rule is below (read 19 Nov 2026).

## Four contexts, four answers

Who accepts risk, by context; quotes are in the sections below; read 19 Nov 2026.

| Context | Who accepts | May it be delegated? | Source |
|---|---|---|---|
| US federal information systems (NIST RMF) | The authorizing official; for common controls, the authorizing official for the control provider | No. Carrying out the chosen response can go to a designated representative; the acceptance cannot | [SP 800-37 Rev. 2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf), Tasks R-3 and R-4 |
| Cloud services under FedRAMP | The provider records and reports an accepted vulnerability; the agency authorizing official decides what the agency does about it | Not stated | [FedRAMP 2026 agency POA&M page](https://www.fedramp.gov/2026/agencies/use/ongoing/poams/) |
| PCI DSS compensating control | The entity proposes; the Qualified Security Assessor judges whether it meets the intent | Not applicable | [PCI SSC FAQ 1046](https://www.pcisecuritystandards.org/faqs/1046) |
| Any other organization | The person its own policy names, working inside the written risk tolerance | Set by that policy | [SP 800-39](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf), Task 3-3 |

## The authorizing official cannot hand the decision down

NIST SP 800-37 Rev. 2 puts acceptance with one role in two places. Task R-4 says "The explicit acceptance of risk is the responsibility of the authorizing official and cannot be delegated to other officials within the organization." The discussion of Task R-3 adds "Because the authorizing official is the only person who can accept risk", the official reviews the assessment reports and plans of action to decide whether identified risks need mitigation before authorization.

The same publication names the one thing a designated representative may not do. The representative coordinates day-to-day risk management, and "the only activity that cannot be delegated by the authorizing official to the designated representative is the authorization decision and signing of the associated authorization decision document (i.e., the acceptance of risk)". Task R-3 names the authorizing official or the designated representative as primarily responsible for identifying and carrying out the risk response, which is why a team can assign the fix or the mitigation to an engineer but not the signature. NIST defines the role as "a senior Federal official or executive with the authority to authorize (i.e., assume responsibility for) the operation of an information system" ([glossary](https://csrc.nist.gov/glossary/term/authorizing_official)).

## FedRAMP splits the record from the decision

Under the 2026 rules a provider reports each accepted vulnerability with eight items, listed in [VER-RPT-AVI](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/): tracking identifier, time and source of detection, time of completed evaluation, internet-reachable or not, likely exploitable or not, the Potential Agency Impact N-rating, why it is accepted, and any supplementary information. Seven of the eight sit in fields 1, 2 (detection and evaluation times), 4, 5, 6 and 7 of the [Risk Acceptance Form](https://remediationvsmitigation.com/risk-acceptance-form/); the eighth is free text the provider chooses. FedRAMP's agency guidance gives the agency its own record: "The POA&M belongs to the agency when the action belongs to the agency," and "The agency authorizing official identifies an agency action needed to keep the system within the agency's risk tolerance." The provider does not sign for the agency, and the agency's official does not sign the provider's internal exception.

## PCI DSS and CISA directives have no signer to name

PCI SSC states it cannot approve specific compensating controls, and that Qualified Security Assessors decide whether a compensating control meets the intent of a requirement ([FAQ 1046](https://www.pcisecuritystandards.org/faqs/1046)). A separate route exists for legal limits: the "Compliant but with Legal exception" option "also requires additional review from the acquirer or payment brand to whom compliance is being reported" ([FAQ 1486](https://www.pcisecuritystandards.org/faqs/1486)).

For KEV actions under a CISA directive there is no one to sign, because CISA does not issue waivers or exceptions for actions required in cyber directives ([BOD 26-04 guidance](https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk)). See the KEV row of the [Decision Table](https://remediationvsmitigation.com/decision-table/).

## Who signs outside the federal case

NIST SP 800-39 gives the test but no title. Task 3-3 reads "Organizations determine acceptable degrees of residual risk based on organizational risk tolerance and the specific risk tolerances of particular decision makers." This is the SP 800-39 text; the Task R-3 discussion in SP 800-37 carries the shorter form, "based on organizational risk tolerance", without the clause about decision makers. SP 800-39 adds that "There is no correct level of organizational risk tolerance", and that the residual risk accepted by authorizing officials is "within the organizational risk tolerance, and not the individual risk tolerances of those authorizing officials." So the organization writes its tolerance down, names who may sign at each level, and the signer applies that limit and not a personal one.

NIST and FedRAMP do not say whether the person who asks for an exception may also sign it, so the policy must. A requester who signs their own exception has no second check. The sample below is one reasonable arrangement, not a requirement of any standard; change the roles and levels to fit the organization.

## Sample signing rule for risk acceptance

1. A finding may be accepted only by a signed [Risk Acceptance Form](https://remediationvsmitigation.com/risk-acceptance-form/) with an expiry date, recorded in the [exception register](https://remediationvsmitigation.com/exception-register/).
2. Who signs, by residual risk after any mitigation (use the organization's own rating scale):
   - Low: the head of the team that owns the system.
   - Moderate: the business owner of the system and the head of security.
   - High: the executive named in the risk policy (for example the CIO or CEO), after the head of security has recorded a written opinion.
3. The person who requests the exception may not sign it. The requester's manager may sign only at the Low level.
4. A signer may not accept a risk above the written organizational risk tolerance, whatever their personal view.
5. The fix or the mitigation may be assigned to an engineer; the signature may not be assigned downward.
6. The signer's name, role and date go in field 13 of the form, and the role goes in the register's approver column.
7. A KEV due date under a CISA directive cannot be accepted by anyone; the rule does not apply to it.

The risk owner named in NIST IR 8286 is a different role from the signer; [who is the risk owner](https://remediationvsmitigation.com/guides/risk-owner/) sets them side by side, and [risk acceptance versus risk tolerance](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/) covers the written limit the signer works within.

## Sources

- NIST SP 800-37 Rev. 2, Tasks R-2, R-3, R-4 and the designated representative role: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf (read 19 Nov 2026)
- NIST CSRC glossary, authorizing official: https://csrc.nist.gov/glossary/term/authorizing_official (read 19 Nov 2026)
- NIST SP 800-39, Task 3-3 and the risk tolerance discussion: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf (read 19 Nov 2026)
- FedRAMP 2026, Managing POA&Ms (agencies): https://www.fedramp.gov/2026/agencies/use/ongoing/poams/ (read 19 Nov 2026)
- FedRAMP 2026, VER-RPT-AVI: https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/ (read 19 Nov 2026)
- PCI SSC FAQ 1046: https://www.pcisecuritystandards.org/faqs/1046 (read 19 Nov 2026)
- PCI SSC FAQ 1486: https://www.pcisecuritystandards.org/faqs/1486 (read 19 Nov 2026)
- CISA BOD 26-04 implementation guidance, FAQ: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk (read 19 Nov 2026)

Last reviewed 19 Nov 2026

## Related

- [Risk Acceptance Form: Free Template With 15 Fields](https://remediationvsmitigation.com/risk-acceptance-form/index.md)
- [Exception Register: 15 Columns, States and Blank CSV](https://remediationvsmitigation.com/exception-register/index.md)
- [Maximum Duration of a Risk Acceptance: 9 Sources](https://remediationvsmitigation.com/risk-acceptance-form/maximum-durations/index.md)
- [Who Is the Risk Owner for a Security Finding?](https://remediationvsmitigation.com/guides/risk-owner/index.md)
- [Risk Acceptance vs Risk Tolerance: Who Sets the Limit](https://remediationvsmitigation.com/guides/risk-acceptance-vs-risk-tolerance/index.md)
