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
the Guide to OSCAL-based FedRAMP System Security Plans (SSP)
the Guide to OSCAL-based FedRAMP Security Assessment Plans (SAP)
the Guide to OSCAL-based FedRAMP Security Assessment Results (SAR)
the Guide to OSCAL-based FedRAMP Plan of Action and Milestones (POA&M)
the FedRAMP SSP OSCAL Template (JSON or XML Format)
the FedRAMP SAP OSCAL Template (JSON or XML Format)
the FedRAMP SAR OSCAL Template (JSON or XML Format)
the FedRAMP POA&M OSCAL Template (JSON or XML Format)
the FedRAMP OSCAL Validations
What happened?
The requirements for task type attribute and tasks structure in FedRAMP Automate Guidance conflict with OSCAL schema structure and will result in validation errors.
Relevant log output
[#/assessment-plan/tasks] #/assessment-plan/tasks: 5 schema violations found [file:///Users/13503/Desktop/SAP_Testing.json]
[ERROR] [#/assessment-plan/tasks/0/tasks/0] #/assessment-plan/tasks/0/tasks/0: required key [type] not found [file:///Users/13503/Desktop/SAP_Testing.json]
[ERROR] [#/assessment-plan/tasks/1/tasks] #/assessment-plan/tasks/1/tasks: 2 schema violations found [file:///Users/13503/Desktop/SAP_Testing.json]
[ERROR] [#/assessment-plan/tasks/1/tasks/0] #/assessment-plan/tasks/1/tasks/0: required key [type] not found [file:///Users/13503/Desktop/SAP_Testing.json]
[ERROR] [#/assessment-plan/tasks/1/tasks/1] #/assessment-plan/tasks/1/tasks/1: required key [type] not found [file:///Users/13503/Desktop/SAP_Testing.json]
[ERROR] [#/assessment-plan/tasks/2/tasks/0] #/assessment-plan/tasks/2/tasks/0: 2 schema violations found [file:///Users/13503/Desktop/SAP_Testing.json]
[ERROR] [#/assessment-plan/tasks/2/tasks/0] #/assessment-plan/tasks/2/tasks/0: required key [type] not found [file:///Users/13503/Desktop/SAP_Testing.json]
How do we replicate this issue?
The use of props instead of the type element will cause errors when validating against schema.
The examples for action represent an accurate schema structure:
But the examples for Role Based and Web Application testing do not have the type attribute carried to the recursive task element, causing a break:
Where, exactly?
Additional Guidance:
Here are two possible solutions, both of which remove the prop for type, and instead use the attribute, since it is not strict on content. Also, recommend validation tool support recursion checks, and/or a combination of all flat or all recursive. This way the source materials may not line up with examples, but should not impact the FedRAMP ability to validate.
EXAMPLES:
OPTION 1: ALL RECURSIVE AND A COLLECTION
This relates to ...
What happened?
The requirements for task type attribute and tasks structure in FedRAMP Automate Guidance conflict with OSCAL schema structure and will result in validation errors.
Relevant log output
How do we replicate this issue?
The use of props instead of the type element will cause errors when validating against schema.
The examples for action represent an accurate schema structure:
But the examples for Role Based and Web Application testing do not have the type attribute carried to the recursive task element, causing a break:
Where, exactly?
Additional Guidance:
Here are two possible solutions, both of which remove the prop for type, and instead use the attribute, since it is not strict on content. Also, recommend validation tool support recursion checks, and/or a combination of all flat or all recursive. This way the source materials may not line up with examples, but should not impact the FedRAMP ability to validate.
EXAMPLES:
OPTION 1: ALL RECURSIVE AND A COLLECTION
Other relevant details
No response
The text was updated successfully, but these errors were encountered: