You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 1, 2025. It is now read-only.
the FedRAMP SSP OSCAL Template (JSON or XML Format)
the FedRAMP OSCAL Validations
What is your feedback?
The frr295 constraint requires every control statement to have a by-component that links back to the this-system component. In the case that a statement is fully inherited, and there is no implementation local to this-system, I don't think this constraint should be enforced.
Im wondering if the constraint can be modified to require there be at least 1 by-component for each statement, rather than each statement requiring a this-system by-component. Please let me know your thoughts on this, or if you think this should be handled/represented a different way.
Update documentation to explain requirement to be "one component must be used and this system should be the catch-all for all control implementation that is leveraged or inherited without 'this system' layer of controls."