-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add leveraged-authorization-has-valid-impact-level
Constraint
#913
Add leveraged-authorization-has-valid-impact-level
Constraint
#913
Conversation
leveraged-authorization-matches-impact-level
constraintleveraged-authorization-has-valid-impact-level
constraint
dd9dc71
to
cf28b02
Compare
45f01c4
to
e98cbd0
Compare
leveraged-authorization-has-valid-impact-level
constraintleveraged-authorization-has-valid-impact-level
Constraint
e98cbd0
to
a485fe4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good nice work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very solid but would like the documentation change to match.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good work, I particularly enjoy how you document the scenarios in your passing and failing test cases over the last few weeks. Keep it up!
a403c4b
423dc35
to
2d17552
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
c89f710
31f0ee4
to
bf5b3bf
Compare
bf5b3bf
to
e694da4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review acceptance criteria and related documentation updates to the website in GSA/automate.fedramp.gov#124, looks good to go. 🚢
Committer Notes
Purpose
This PR adds a constraint to ensure that a digital authorization package maintains appropriate FIPS-199 impact levels for leveraged authorizations within an SSP. This update helps avoid pass-back errors by aligning with the system's security sensitivity level (e.g., low, moderate, or high).
Changes
expect
constraint to check that all leveraged authorizations define the appropriate FIPS-199 impact level (low, moderate, or high).ssp-all-VALID.xml
to have proper data to trigger the constraint and pass.All Submissions:
- [ ] If applicable, have all FedRAMP Documents Related to OSCAL Adoption affected by the changes in this issue have been updated.?Documentation already existsBy submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.