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 is your feedback?
In reviewing the prop list for interconnection, there are a few that seem to already be answered by other elements.
Requesting additional detail and guidance to confirm:
Data type: Information data types already captures this data. Should this, and the one below, be combined into a UUID reference back to the information types?
Data Categorization: Information data types already captures this data. Should this, and the one below, be combined into a UUID reference back to the information types?
port: Isn't port supposed to be referenced by linking to the service that is providing the port and protocol? This seems to be a work around, instead of leveraging the schema and referencing the service that has the protocol element. Describe the class requirement for this prop? What is remote? Is there supposed to be a start end end port?
This is a ...
question - need to understand something
This relates to ...
What is your feedback?
In reviewing the prop list for interconnection, there are a few that seem to already be answered by other elements.
Requesting additional detail and guidance to confirm:
Where, exactly?
component[@type=interconnection][props]
Other information
No response
The text was updated successfully, but these errors were encountered: