AFC-CSO-NOCNotification of Changes
allMUST
Providers MUST immediately notify FedRAMP of any changes to the email address for their FedRAMP Security Inbox.
Who it binds
Controls whose FedRAMP guidance points at AFC (1)
Their guidance names the Addressing FedRAMP Communication 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.
Notifications (1)
- FedRAMPvia form: https://help.fedramp.gov/hc/en-us/requests/new?ticket_form_id=51829466938011
Which certifications it binds
- Certification type
- 20x · Rev5
- Path
- Program · Agency
Evidence this requirement demands
- Process, manual or automated, to notify FedRAMP of changes in the FedRAMP Security Inbox
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 Addressing FedRAMP Communication. See all obligations on /obligations or the full evidence plan on /evidence.