{
 "name": "Remediation vs Mitigation: Risk Acceptance Form fields",
 "edition": "2026-11-19",
 "license": "CC BY 4.0",
 "license_url": "https://creativecommons.org/licenses/by/4.0/",
 "cite": "Remediation vs Mitigation, Risk Acceptance Form fields, edition 19 Nov 2026, https://remediationvsmitigation.com/risk-acceptance-form/",
 "who_may_sign": [
  {
   "context": "US federal information systems (NIST RMF)",
   "who": "The authorizing official, or for common controls the authorizing official for the control provider",
   "delegable": "Acceptance cannot be delegated; carrying out the chosen response can be assigned to the AO designated representative.",
   "sources": [
    {
     "claim": "SP 800-37 Task R-2/R-3 discussion.",
     "quote": "Because the authorizing official is the only person who can accept risk",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Chapter 3 page 72"
    },
    {
     "claim": "SP 800-37.",
     "quote": "The explicit acceptance of risk is the responsibility of the authorizing official and cannot be delegated to other officials within the organization.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task R-4"
    },
    {
     "claim": "NIST glossary definition of authorizing official.",
     "quote": "A senior Federal official or executive with the authority to authorize (i.e., assume responsibility for) the operation of an information system",
     "source": "https://csrc.nist.gov/glossary/term/authorizing_official",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "NIST CSRC glossary, authorizing official"
    },
    {
     "claim": "SP 800-37 Task R-3 assigns identifying and implementing the response to the AO or a designated representative (not the same as accepting risk).",
     "quote": "Primary Responsibility:  Authorizing Official or Authorizing Official Designated Representative.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task R-3"
    }
   ]
  },
  {
   "context": "Cloud services in FedRAMP (2026 rules and legacy playbook)",
   "who": "The provider records accepted vulnerabilities and reports them; the federal agency's authorizing official decides about agency use and any agency POA&M",
   "delegable": "Not stated.",
   "sources": [
    {
     "claim": "FedRAMP 2026.",
     "quote": "The POA&M belongs to the agency when the action belongs to the agency.",
     "source": "https://www.fedramp.gov/2026/agencies/use/ongoing/poams/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Managing POA&Ms"
    },
    {
     "claim": "FedRAMP 2026.",
     "quote": "The agency authorizing official identifies an agency action needed to keep the system within the agency's risk tolerance.",
     "source": "https://www.fedramp.gov/2026/agencies/use/ongoing/poams/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Managing POA&Ms"
    }
   ]
  },
  {
   "context": "PCI DSS compensating control",
   "who": "The entity proposes; the Qualified Security Assessor judges whether the control meets the intent. PCI SSC does not approve compensating controls.",
   "delegable": "Not applicable.",
   "sources": [
    {
     "claim": "PCI SSC FAQ 1046.",
     "quote": "The PCI Security Standards Council (PCI SSC) is not able to approve specific configurations or compensating controls",
     "source": "https://www.pcisecuritystandards.org/faqs/1046",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "FAQ 1046"
    },
    {
     "claim": "PCI SSC FAQ 1486 (legal exception only).",
     "quote": "Use of the \"Compliant but with Legal exception\" option also requires additional review from the acquirer or payment brand to whom compliance is being reported.",
     "source": "https://www.pcisecuritystandards.org/faqs/1486",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "FAQ 1486"
    }
   ]
  },
  {
   "context": "Other organizations (no federal or PCI duty)",
   "who": "None found on 2026-11-19: no standard read names a title. NIST SP 800-39 says residual risk is accepted by decision makers within the organization's stated risk tolerance.",
   "delegable": "Not stated.",
   "sources": [
    {
     "claim": "SP 800-39 Task 3-3.",
     "quote": "Organizations determine acceptable degrees of residual risk based on organizational risk tolerance and the specific risk tolerances of particular decision makers.",
     "source": "https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task 3-3, Chapter 3"
    }
   ]
  }
 ],
 "maximum_durations": [
  {
   "source": "FedRAMP Consolidated Rules for 2026, VER-TFR-MAV",
   "limit": "192 days from evaluation, after which a vulnerability not mitigated or remediated must be categorized as an accepted vulnerability and reported with the AVI fields",
   "sources": [
    {
     "claim": "",
     "quote": "Providers MUST categorize any vulnerability that is not or will not be fully mitigated or remediated within 192 days of evaluation as an accepted vulnerability.",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-TFR-MAV"
    }
   ],
   "status": "current (launched 2026-06-24; Rev5 required from 2026-12-07)"
  },
  {
   "source": "FedRAMP legacy POA&M playbook",
   "limit": "Remediate Critical and High in 30 days, Moderate in 90 days, Low in 180 days from discovery; High-risk vendor dependencies mitigated to Moderate within 30 days; vendor check-in at least monthly",
   "sources": [
    {
     "claim": "",
     "quote": "FedRAMP requires Critical and High risks to be remediated within 30 days of discovery, Moderate risks within 90 days of discovery, and Low risks within 180 days of discovery.",
     "source": "https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "General POA&M Guidance"
    }
   ],
   "status": "legacy, reference only after 2026-06-24"
  },
  {
   "source": "CISA BOD 26-04 Table 1",
   "limit": "3, 14 or 60 calendar days, or 'fix on system upgrade', depending on exposure, KEV status, automation and impact",
   "sources": [
    {
     "claim": "Table 1 timelines, read from the table image.",
     "quote": "3 days & forensic triage | 3 days | 14 days | 60 days | Fix on system upgrade",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Table 1"
    }
   ],
   "status": "current for federal civilian agencies; no waivers"
  },
  {
   "source": "CISA BOD 26-04 implementation guidance",
   "limit": "No waivers or exceptions to directive actions",
   "sources": [
    {
     "claim": "",
     "quote": "CISA does not issue waivers or exceptions for actions required in cyber directives.",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "FAQ"
    }
   ],
   "status": "current"
  },
  {
   "source": "CISA BOD 26-02",
   "limit": "EOS edge devices on the CISA list: decommission within 12 months (listed devices with an EOS date by then) and all EOS edge devices within 18 months; continuous discovery and decommission by EOS date within 24 months, counted from 5 Feb 2026",
   "sources": [
    {
     "claim": "",
     "quote": "Within eighteen (18) months of issuance, all FCEB agencies shall:",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-02-mitigating-risk-end-support-edge-devices",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Required Actions"
    }
   ],
   "status": "current for federal civilian agencies; does not apply to OT devices"
  },
  {
   "source": "PCI DSS v4.0.1 (via PCI SSC FAQ 1597 and announcement)",
   "limit": "Critical vulnerabilities resolved (patches installed) within one month (30 days) of release; no maximum duration for a compensating control was found because Appendix B was not read",
   "sources": [
    {
     "claim": "",
     "quote": "Reverted to PCI DSS v3.2.1 language that installing patches/updates within 30 days applies only for \"critical vulnerabilities.\"",
     "source": "https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Requirement 6 changes"
    }
   ],
   "status": "current"
  },
  {
   "source": "NIST SP 800-37 Rev. 2",
   "limit": "No fixed maximum. The authorizing official sets the termination date, or authorization frequency under ongoing authorization.",
   "sources": [
    {
     "claim": "",
     "quote": "Organizations may eliminate the authorization termination date if the system is operating under an ongoing authorization",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task R-4"
    }
   ],
   "status": "current"
  },
  {
   "source": "NIST SP 800-53 Rev. 5 CA-5, SI-2",
   "limit": "No fixed number; the review frequency in CA-5 and the update window in SI-2 are organization-defined parameters",
   "sources": [
    {
     "claim": "",
     "quote": "Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of risk factors",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/SI-2",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "SI-2 discussion"
    }
   ],
   "status": "current"
  },
  {
   "source": "NIST SP 800-40 Rev. 4",
   "limit": "No fixed number; exceptions are reviewed regularly",
   "sources": [
    {
     "claim": "",
     "quote": "Organizations should closely track and monitor all exceptions to maintenance plans.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 3.5.5"
    }
   ],
   "status": "current"
  }
 ],
 "unread": [
  "FedRAMP POA&M template spreadsheet itself and the Vulnerability Deviation Request form (legacy; only the playbook page and the June 2022 update post were read)",
  "PCI DSS v4.0.1 Appendix C compensating controls worksheet (click-through license)",
  "ISO/IEC 27005 (iso.org returned 403)"
 ],
 "rows": [
  {
   "id": "tracking-id",
   "label": "Tracking identifier and finding reference (CVE ID, scanner finding ID)",
   "recommended_required": true,
   "what_goes_here": "One internal ID for the exception, plus the CVE ID and scanner finding IDs it covers.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "FedRAMP 2026 accepted-vulnerability report field.",
     "quote": "Provider's internally assigned tracking identifier",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-RPT-AVI: Accepted Vulnerability Info"
    },
    {
     "claim": "FedRAMP POA&M template column AD 'CVE' (added June 2022).",
     "quote": "should now be used to track the CVE's associated with the vulnerabilities listed on that POA&M line item (if applicable).",
     "source": "https://www.fedramp.gov/archive/2022-06-28-update-poam-template/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Update to the POA&M template, 27 Jun 2022"
    }
   ],
   "used_for": [
    "remediate",
    "mitigate_now_fix_later",
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "detection",
   "label": "Time and source of the detection, and time evaluation completed",
   "recommended_required": true,
   "what_goes_here": "When and by what tool or report the finding was first seen, and when it was evaluated.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "FedRAMP 2026 field.",
     "quote": "Time and source of the detection",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-RPT-AVI: Accepted Vulnerability Info"
    },
    {
     "claim": "FedRAMP 2026 field.",
     "quote": "Time of completed evaluation",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-RPT-AVI: Accepted Vulnerability Info"
    }
   ],
   "used_for": [
    "remediate",
    "mitigate_now_fix_later",
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "asset",
   "label": "Affected asset or system, environment, and exposure",
   "recommended_required": true,
   "what_goes_here": "Hostnames or system IDs, prod or dev, public or internal, asset type.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "BOD 26-04 asset tag: exposure.",
     "quote": "Exposure (public/internal)",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Required Actions, Phase III, tags"
    },
    {
     "claim": "BOD 26-04 asset tag: environment.",
     "quote": "Environment (prod/dev)",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Required Actions, Phase III, tags"
    }
   ],
   "used_for": [
    "remediate",
    "mitigate_now_fix_later",
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "reachable",
   "label": "Is it internet-reachable?",
   "recommended_required": true,
   "what_goes_here": "Yes or no, with the basis (reachability test, architecture).",
   "applies_to": "all",
   "sources": [
    {
     "claim": "FedRAMP 2026 field.",
     "quote": "Is it an internet-reachable vulnerability or not?",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-RPT-AVI: Accepted Vulnerability Info"
    }
   ],
   "used_for": [
    "mitigate_now_fix_later",
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "exploitable",
   "label": "Is it likely exploitable? Is it on the KEV list?",
   "recommended_required": true,
   "what_goes_here": "Likelihood of exploitation in this environment, KEV status, exploit automation.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "FedRAMP 2026 field.",
     "quote": "Is it a likely exploitable vulnerability or not?",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-RPT-AVI: Accepted Vulnerability Info"
    },
    {
     "claim": "BOD 26-04 decision variable.",
     "quote": "KEV Status: Is the vulnerability, as identified by a common vulnerabilities and exposures identifier (CVE ID), on CISA's Known Exploited Vulnerabilities Catalog ?",
     "source": "https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Background"
    }
   ],
   "used_for": [
    "remediate",
    "mitigate_now_fix_later",
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "impact",
   "label": "Estimated impact if exploited",
   "recommended_required": true,
   "what_goes_here": "Impact rating using the organization's scale (FedRAMP uses a Potential Agency Impact N-rating).",
   "applies_to": "all",
   "sources": [
    {
     "claim": "FedRAMP 2026 field.",
     "quote": "Currently estimated Potential Agency Impact N-rating",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-RPT-AVI: Accepted Vulnerability Info"
    }
   ],
   "used_for": [
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "reason",
   "label": "Reason the finding is accepted instead of fixed or mitigated",
   "recommended_required": true,
   "what_goes_here": "The business, technical or legal constraint, in plain words.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "FedRAMP 2026 field.",
     "quote": "Explanation of why this is an accepted vulnerability",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-RPT-AVI: Accepted Vulnerability Info"
    },
    {
     "claim": "SP 800-39 allows acceptance for compelling needs.",
     "quote": "Conversely, organizations may accept substantially greater risk (in the moderate/high range) due to compelling mission, business, or operational needs.",
     "source": "https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-39.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task 3-1, Chapter 3 page 42"
    }
   ],
   "used_for": [
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "controls",
   "label": "Mitigating factors and compensating controls in place",
   "recommended_required": true,
   "what_goes_here": "Each control, its owner, how it was verified and when. Link to the controls register entry.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "Legacy FedRAMP risk adjustment justification.",
     "quote": "To justify a RA, CSPs must describe mitigating factors or compensating controls in place that reduce likelihood and/or impact of exploitation.",
     "source": "https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "General POA&M Guidance"
    },
    {
     "claim": "SP 800-37 Task R-2 discussion: compensating controls are documented.",
     "quote": "At the completion of the control reassessments, security and privacy plans contain an accurate description of implemented controls, including compensating controls.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task R-2, Chapter 3 page 72"
    }
   ],
   "used_for": [
    "mitigate_now_fix_later",
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "plan",
   "label": "Planned corrective tasks, resources, milestones and scheduled completion dates",
   "recommended_required": true,
   "what_goes_here": "What will fix it, who owns each task, what it needs, and the dates.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "SP 800-37 Task A-6 on POA&M content.",
     "quote": "The plan of action and milestones includes tasks to be accomplished with a recommendation for completion before or after system authorization; resources required to accomplish the tasks; milestones established to meet the tasks; and the scheduled completion dates for the milestones and tasks.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task A-6"
    },
    {
     "claim": "800-53 CA-5 a.",
     "quote": "Develop a plan of action and milestones for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system; and",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/CA-5",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "CA-5 a"
    },
    {
     "claim": "NIST glossary definition (SP 800-53 Rev. 5).",
     "quote": "A document that identifies tasks that need to be accomplished. It details resources required to accomplish the elements of the plan, milestones for meeting the tasks, and the scheduled completion dates for the milestones.",
     "source": "https://csrc.nist.gov/glossary/term/plan_of_action_and_milestones",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "NIST CSRC glossary, plan of action and milestones"
    }
   ],
   "used_for": [
    "remediate",
    "mitigate_now_fix_later",
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "update",
   "label": "Update trigger and review cadence",
   "recommended_required": true,
   "what_goes_here": "What causes the record to be reopened: scan, audit, monitoring finding, change to exposure, new KEV listing.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "800-53 CA-5 b (the review frequency is an organization-defined parameter).",
     "quote": "based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/CA-5",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "CA-5 b"
    },
    {
     "claim": "SP 800-40r4 on regular review.",
     "quote": "All exceptions to maintenance plans should be reviewed regularly to determine if the maintenance plan can be implemented now.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Section 3.5.5"
    },
    {
     "claim": "Legacy FedRAMP: an approved exception stays open and is reassessed.",
     "quote": "Approved ORs are still considered open risks. They must be captured on the POA&M's \" Open \" tab and periodically reassessed by the CSP.",
     "source": "https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "General POA&M Guidance"
    }
   ],
   "used_for": [
    "mitigate_now_fix_later",
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "residual",
   "label": "Residual risk statement and reference to risk tolerance",
   "recommended_required": true,
   "what_goes_here": "What risk remains after the controls, compared to the organization's stated tolerance.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "SP 800-37 Task R-3 discussion.",
     "quote": "A key part of the risk-based decision process is the recognition that regardless of the risk response, there remains a degree of residual risk.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task R-3"
    },
    {
     "claim": "NIST glossary: risk tolerance (SP 800-53 Rev. 5).",
     "quote": "The level of risk or the degree of uncertainty that is acceptable to an organization.",
     "source": "https://csrc.nist.gov/glossary/term/risk_tolerance",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "NIST CSRC glossary, risk tolerance"
    },
    {
     "claim": "800-53 RA-7.",
     "quote": "Respond to findings from security and privacy assessments, monitoring, and audits in accordance with organizational risk tolerance.",
     "source": "https://csrc.nist.gov/projects/cprt/catalog#/cprt/framework/version/SP_800_53_5_2_0/home/RA-7",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "RA-7"
    }
   ],
   "used_for": [
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "vendor",
   "label": "Vendor dependency: product name, last vendor check-in date, evidence of vendor status",
   "recommended_required": false,
   "what_goes_here": "When the fix depends on a vendor patch that does not exist yet.",
   "applies_to": "vendor-dependent findings",
   "sources": [
    {
     "claim": "Legacy FedRAMP vendor dependency rule.",
     "quote": "VDs are tracked as open risks, and CSPs are required to check in with the vendor at least once a month to determine the status of the patch/fix.",
     "source": "https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "General POA&M Guidance"
    },
    {
     "claim": "Legacy FedRAMP evidence expectation.",
     "quote": "Do provide evidence of vendor interactions regarding the status of patches/fixes (e.g., vendor notifications, email exchanges, etc.).",
     "source": "https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "POA&M Do's and Don'ts"
    }
   ],
   "used_for": [
    "mitigate_now_fix_later"
   ]
  },
  {
   "id": "approver",
   "label": "Approver name, title and date of decision",
   "recommended_required": true,
   "what_goes_here": "The person with authority to accept the risk, signing and dating the decision.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "SP 800-37 Task R-4 discussion (authorization decision).",
     "quote": "The explicit acceptance of risk is the responsibility of the authorizing official and cannot be delegated to other officials within the organization.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task R-4"
    },
    {
     "claim": "Legacy FedRAMP: pending risk adjustments need agency AO approval.",
     "quote": "Pending RAs must be approved by the federal agency AO prior to authorization.",
     "source": "https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "General POA&M Guidance"
    }
   ],
   "used_for": [
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "expiry",
   "label": "Expiry date (termination date) of the exception",
   "recommended_required": true,
   "what_goes_here": "A date after which the exception lapses unless renewed by the approver.",
   "applies_to": "all",
   "sources": [
    {
     "claim": "SP 800-37 Task R-4 discussion.",
     "quote": "The authorization termination date is established by the authorizing official and indicates when the authorization expires.",
     "source": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-37r2.pdf",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "Task R-4"
    },
    {
     "claim": "FedRAMP 2026 upper bound before a vulnerability is reported as accepted.",
     "quote": "Providers MUST categorize any vulnerability that is not or will not be fully mitigated or remediated within 192 days of evaluation as an accepted vulnerability.",
     "source": "https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-evaluation-and-reporting/",
     "read": "2026-11-19",
     "kind": "primary",
     "location": "VER-TFR-MAV"
    }
   ],
   "used_for": [
    "accept_with_dated_exception"
   ]
  },
  {
   "id": "pci-fields",
   "label": "PCI DSS compensating control worksheet fields",
   "recommended_required": false,
   "what_goes_here": "Not recorded: Appendix C text was not read (see unread).",
   "applies_to": "PCI DSS in-scope",
   "sources": [],
   "used_for": []
  }
 ]
}