[Feedback]: [system-characteristics][date-authorized] use cases

[Telos-sa]

This is a ...

request - need something additional provided

This relates to ...

• the FedRAMP OSCAL Registry
• the FedRAMP OSCAL baselines
• the Guide to OSCAL-based FedRAMP Content
• 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?

For this element, there are different statuses that a package can have throughout the lifecycle. From FedRAMP-Ready, to Provisional ATO, and even ATO if through an agency. While authorization-type prop does show who the AO is, there is no where to specific the specific Dates.

Recommend writing requirements to collect the current status of the Project (Initial Authorization, FedRAMP Ready, P-ATO, ATO) as a prop, then including the date of approval as the date authorized for that status.

Where, exactly?

[system-characteristics][date-authorized] use cases

Other information

No response