Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the
fedramp-consolidated-rules.jsonfile to clarify requirements for public JSON data interoperability, improve rule precision, and update supporting information for FedRAMP compliance. The most important changes include new guidance for web compatibility of JSON data, clarifications in rule statements and notes, and updates to forms and terminology.Public JSON Data Interoperability and Web Compatibility:
FRC-CSO-JSNrule to require that public JSON data be compatible with modern web frameworks, including proper CORS configuration and HTTP headers, and added detailed notes on expected web accessibility and schema validation.Clarifications and Precision in Rules:
FedRAMP Ready Conversionrule statement for grammatical accuracy and documented the change. [1] [2]Terminology and Impact Assessment Updates:
Estimate Potential Agency Impactrule to specify that the "likely" impact should be estimated, added a new PAIN0 category for cases with no likely adverse effects, and included "Likely" in the terms. [1] [2]Form and Reference Updates:
Versioning and Metadata: