2026/support/

[giscus[bot]]

2026/support/

This site contains FedRAMP's Consolidated Rules for 2026.

https://www.fedramp.gov/2026/support/

[ExtremoPenguin]

Some feedback on the comments here on the rules site. Allowing comments on the reference section reduces the visibility of existing questions and answers. As an example https://www.fedramp.gov/2026/reference/rev5/c/security-decision-record/ has a question/answer that is applicable beyond Rev 5 - Class C. Someone who is looking at the non-reference version of the SDR page https://www.fedramp.gov/2026/providers/rev5/rules/security-decision-record/ would not see that comment and even if you were looking at the reference pages, you would need to specifically be looking at the class C version.

[pete-gov]

All comments can be reviewed on GitHub: https://github.com/FedRAMP/2026/discussions

But yes, overall, the comment system should lead to FAQs that are posted on help.fedramp.gov and cleaned up on occasion - we're working on it!

[cbaerschellman]

Hi Pete - my experience has been that LLMs are unable to parse through the comments within the rules as they are not standalone indexed forum posts. Do you / the team (or other stakeholders) have suggestions for the best way to stay updated on the latest discussions?

[pete-gov]

Following this forum should work - I have it set up to send me an email and post in our google chat using the GitHub app any time anyone makes a comment on any discussion thread in the 2026 repo, as well as the community repo. This makes it quite easy to follow along and is why we can pop in and respond so quickly (I'm responding after seeing the post about this in chat). Our activity here is relatively low so it's not a huge burden.

Any capable agent service (Codex, Claude Code, etc.) should be able to quickly and easily write the necessary code to monitor discussion posts here using GitHub's API as well, and can follow the links to add context.

[cbaerschellman]

Thanks, Pete! I will give that a try. Appreciate it.