Roles
Every FedRAMP assessment package must identify the party (individual, team or organization) responsible for pre-defined roles, such as system owner and information system security officer (ISSO).
Representing this information in OSCAL requires four important elements:
rolesto define the rolespartiesto represent individuals, teams or organizationsresponsible-partieslinkingrolestoparties- Canonical role ID values for required roles ensure consistency for tool processing
This is represented in OSCAL metadata.
- A
rolesentry must exist that includes:idwith an canonical role ID valuetitlewith a human-readable name for the role as it appears in the FedRAMP authorization package
- One or more
partiesentries must exist that includes:uuidwith a unique valuetypewith a value ofindividualfor people ororganizationfor teams and organizationsnamewith the name of the person, team or organization.- other fields as needed, such as
email-addresses,telephone numbers,addressesorlocation-uuid.
- A
responsible-partiesentry must exist that includes:role-idwith the same value as inroles/idabove.party-uuidsarray with one or more UUIDs that referencepartiesentries above.
- Optional
locationsentries that can be linked from party entries
Representation
metadata:
roles:
- id: system-owner
title: System Owner
- id: authorizing-official
title: Authorizing Official
locations:
- uuid: 11111111-2222-4000-8000-003000000001
title: CSP HQ
address:
type: work
addr-lines:
- Suite 0000
- 1234 Some Street
city: Haven
state: ME
postal-code: '00000'
parties:
- uuid: 11111111-2222-4000-8000-004000000003
type: individual
name: A. Person
email-addresses:
- a.person@example.com
location-uuids:
- 11111111-2222-4000-8000-003000000001
responsible-parties:
- role-id: authorizing-official
party-uuids:
- 11111111-2222-4000-8000-004000000003
Canonical Role ID Values
The following values are canonical for roles and must be used for id in roles and role-id in responsible-parties to ensure consistent tool processing:
Roles for All FedRAMP Artifacts
| This role ID | identifies |
|---|---|
prepared-by |
who prepared the FedRAMP artifact |
prepared-for |
for whom the artifact was prepared |
content-approver |
the individual(s) who approve the content in the FedRAMP artifact as accurate and complete. |
Roles for System Security Plan (SSP)
| This role ID | identifies |
|---|---|
cloud-service-provider |
the Cloud Service Provider's organization |
system-owner |
the CSP officer legally responsible for system |
system-poc-management |
the system's prmariy management contact |
system-poc-technical |
the system's primary technical contact |
authorizing-official |
an Agency's authorizing official (AO) |
authorizing-official-poc |
an Agency's primary point of contact on behalf of the AO. |
system-poc-other |
additional points of contact for the system |
information-system-security-officer |
the individual responsible for the the secure operation of the system |
privacy-poc |
the individual responsible for ensuring appropriate protection of privacy information within the system |
Roles for Plan of Action and Milestones (POA&M)
To be added in Phase 2
Roles for Security Assessment Plan (SAP)
To be added in Phase 3
Roles for Security Assessment Report (SAR)
To be added in Phase 3
No comments to display
According to the fedramp-automation validator, the following additional role appears to be required:
- fedramp-pmo: FedRAMP Project Management Office (PMO)
In reply to #1
Good catch. I'm more inclined to remove this from the validator, but we should discuss either way.
No comments to display