Skip to content
FedRAMP Rules Hub
JSON — GET /api/obligations

Keyboard shortcuts

Go

  • Scope — the control cataloggm
  • Plan — your last certification classgp
  • Collect — the recipe indexgc
  • The control you are workinggw
  • Startgh

Move

  • Next rowj
  • Previous rowk
  • Previous in this run[
  • Next in this run]
  • Filter this page's list/
  • Search everything⌘K

Act

  • Copy this page's permalinky
  • Toggle dark moded
  • This sheet?

Rows are whatever the current page lists — controls on Scope, recipes on Plan and Collect.

Control index

SCN-CSO-HRMHuman and Machine-Readable Notifications

JSON — GET /api/obligationsMD — /requirement/scn-cso-hrm.md — this page as markdown, for pasting into an agent
allMUST
Providers MUST make ALL Significant Change Notifications and related audit records available in human-readable and JSON formats.

Who it binds

Providers

Controls whose FedRAMP guidance points at SCN (2)

Their guidance names the Significant Change Notification rules as a whole, not this requirement — so this is where to read from, not a mapping to this clause. Controls no KSI reaches have no page and are not listed.

CA-07CM-08

Which certifications it binds

Certification type
20x · Rev5
Path
Program · Agency

Machine-readable form

FedRAMP Significant Change Notifications Schema

https://fedramp.gov/schemas/fedramp-significant-change-notifications-schema-2026-06-24.json

Evidence this requirement demands

  • URL or explanation of how to request these materials.
  • Explanation of how the provider decides whether or not to share these materials or other related policies.
5 default artifacts owed by every FRR requirement
  • Explanation of how the rule is followed, or an explanation of the reason and resulting risk to customers for not following the rule.
  • Verification that the implementation is appropriate for the rule, or that the reason for not implementing is accepted by a senior official.
  • Validation that the implementation is in place and working as intended, or that the reason for not implementing is accepted by a senior official.
  • Independent verification.
  • Independent validation.

Group all, subset CSO of Significant Change Notification. See all obligations on /obligations or the full evidence plan on /evidence.