Title Pages
All FedRAMP artifacts include a title page. The content found on the title page is represented using core OSCAL content in metadata.
titlethe artifact title as FedRAMP requires it to appearpublishedthe formal publication date of the artifact (using OSCALdate-time-with-timezoneformat)versionthe formal version number of the artifact- a
propentry with:nameset tomarkingvalueset toControlled Unclassified Information
- an additional
propentry with:nameset tofedramp-versionnsset tohttp://fedramp.gov/ns/oscalvalueset to the the tag representing the version of FedRAMP being used
The CSP name is represented using thecloud-service-provider role in SSP Roles.
The CSO name is addressed using the SSP System Information, CSO Name
For assessment artifacts, the assessor name is represented using the assessor role in the SAP Roles.
Additional document markings may be added using additional prop entries with name set to marking and value set to the required marking.
All documents in a digital authorization package for FedRAMP should specify the version that identifies which FedRAMP policies, guidance, and technical specifications its authors used during the creation and maintenance of the package.
Representation
system-security-plan:
metadata:
title: \[EXAMPLE\] FedRAMP \[Baseline Name\] System Security Plan (SSP)
published: '2024-12-31T23:59:59Z'
last-modified: '2025-01-08T04:18:29Z'
version: fedramp-3.0.0rc1-oscal-1.1.2
oscal-version: 1.1.3
props:
- name: marking
value: cui
class: fedramp.gov
No comments to display
@Brian Ruf I added an additional prop reference based upon the guidance formally found on the FedRAMP documentation website (since decomissioned). I preserved it mostly as is, but change the verb from "must" to "should" since the implied reference no longer exists. However, it seems like a useful addition. If not, my edit should be reverted.
In reply to #1
I like the catch and addition of `marking`. Thank you!
I removed the `fedramp-version` prop as that was tied to the validation file version, which is no longer relevant as PMO is no longer maintaining or publishing validation files. If we end up maintaining validation files and want to address that with a prop, it will need to be a different prop name.
No comments to display