FedRAMP POA&M Contents

The OSCAL POA&M Model is used to represent the FedRAMP POA&M. This model includes:

  • Metadata and back-matter syntax, which is common to all OSCAL models

  • Local definitions

  • Observations

  • Risks; and

  • POA&M Items syntax. Individual POA&M item syntax is the same as the Findings syntax in the SAR.

Representing the POA&M

This is based on the Excel-based FedRAMP POA&M Template.

Content that is common across OSCAL file types is described in the FedRAMP OSCAL Documentation. This includes the following:

Individual POA&M Entries

For those familiar with using the Excel-based FedRAMP POA&M template, each row in the spreadsheet is represented by a single poam-item assembly in OSCAL.

OSCAL requires the poam-items assembly to include title, description, start and end fields. The value of the title and description fields may be anything the CSP feels is appropriate. FedRAMP suggests duplicating the title value used in the metadata section.

Screenshot of the FedRAMP POA&M template showing entry rows.

FedRAMP POA&M entries.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

<metadata>
    <title>[System Name] FedRAMP Plan of Action and Milestones (POA&amp;M)</title>
    <last-modified>2023-06-30T00:00:00Z</last-modified>
    <version>0.0.0</version>
    <oscal-version>1.0.4</oscal-version>
    <!-- role, location, party, responsible-party -->
</metadata>

<!-- import -->
<!-- local-definitions -->
<!-- observation 1 -->
<!-- observation 2 -->
<!-- observation 3 -->
<!-- risk A -->
<!-- risk A -->
<!-- risk A -->

<poam-item uuid="6f5fff73-cac6-4da0-a0d9-0f931a5efafa">
    <title>[EXAMPLE]POA&amp;M Item</title>
    <description/>
    <prop ns="http://fedramp.gov/ns/oscal" name="POAM-ID" value="V-1"/>
    <related-observation observation-uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab" />
    <associated-risk risk-uuid="9cbd98f3-abcb-4948-ad06-14e0bcba742f" />
    <remarks>
        <p>The FedRAMP Extension, "POAM-ID" captures the traditional CSP-assigned unique POA&amp;M identifier.</p>
    </remarks>
</poam-item>

<!-- poam-item (spreadsheet row 2) -->
<!-- poam-item(spreadsheet row 3) -->
<!-- back-matter -->

Individual POA&M Entries: Findings

As with the Excel-based POA&M template, there is typically a single poam-item for each unique vulnerability; however, in OSCAL, some of the details are included in observation or risk assemblies and linked to the poam-item assembly.

The observation assembly identifies who, what, where, when and how. It identifies who performed what activity, how the activity was performed, what tools were used, and what evidence was collected. If appropriate, the location can be included as well. More importantly, observation identifies the system components impacted by the risk.

The risk assembly includes risk details, such as the risk statement, likelihood, impact, mitigating factors, deviations, remediation plan, and resolution tracking. OSCAL allows more than one associated-risk to be assigned to a poam-item; however, FedRAMP strongly recommends only one associated-risk per poam-item.

The CSP-assigned unique POA&M ID must be present in the poam-item assembly using the FedRAMP extension, POAM-ID.

The related control must be present in the risk assembly using the impacted-control-id FedRAMP extension.

The collected field must be set to the Original Detection Date, which may be the tool’s timestamp.

Within the poam-item assembly, there must be at least one observation assembly, and exactly one risk assembly.

Screenshot of the FedRAMP POA&M template showing individual POA&M entry row.

Individual POA&M entry.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

    <observation uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab">
        <!-- evidence details: which tool, who operated it, where is the raw output? -->
    </observation>
    <!-- observation -->
    <!-- observation -->
    
    <risk uuid="9cbd98f3-abcb-4948-ad06-14e0bcba742f">
        <prop name="impacted-control-id" ns="http://fedramp.gov/ns/oscal" 
              value="ac-2" />
        <!-- risk details: likelihood, impact, mitigation, deviation, remediation -->
    </risk>
    <!-- risk -->
    <!-- risk -->
    
    <poam-item uuid="0be71cd3-f850-47db-836f-14511edbd90e">
        <title>[EXAMPLE]POA&amp;M Item</title>
        <description/>
        <prop name="POAM-ID" ns="http://fedramp.gov/ns/oscal" value="V-1"/>
        <related-observation observation-uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab" />
        <associated-risk risk-uuid="9cbd98f3-abcb-4948-ad06-14e0bcba742f" />
    </poam-item>
    
    <!-- poam-item -->
    <!-- related-observation -->
    <!-- associated-risk -->
    
    <!-- poam-item -->
    <!-- related-observation -->
    <!-- associated-risk -->

Individual POA&M Entries: Observations

Within the observation assembly, the method field must be set to TEST for scanning results. Set this value to TEST, EXAMINE or INTERVIEW as appropriate for risks identified by other means.

The type field must be set to finding.

The uuid flag of the origin field must identify the Weakness Detector Source of the information. For monthly scanning, this must identify the automated tool’s UUID, and the type flag must be set to tool. The tool must be defined as a component in the local-definitions assembly, using the same syntax and approach described in SAP Test Plan: Testing Performed Using Automated Tools.

The href flag in the relevant-evidence field must point to the resource containing the raw tool output attached in the back-matter using a URI fragment. Relevant evidence information is encouraged, but not required for POA&M entries.

At the end of the finding assembly, the UUID for the operator of the scanning tool may be listed as the party-uuid for the finding. There may be more than one. Each party-uuid must reference a party assembly in either the POA&M’s metadata section, or the metadata section of the imported SSP. Tool operator information is optional, but a POA&M tool should display the party information if one or more party-uuid fields are present.

Screenshot of the FedRAMP POA&M template showing entry row weakness source.

FedRAMP POA&M entry weakness source.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

<local-definitions>
    <component uuid="9d194268-a9d1-4c38-839f-9c4aa57bf71e" type="software">
        <title>XYZ Vulnerability Scanning Tool</title>
        <description/>
        <prop ns="http://fedramp.gov/ns/oscal" name="vendor" value="Vendor Name"/>
        <prop ns="http://fedramp.gov/ns/oscal" name="name" value="Tool Name"/>
        <prop name="version" value="1.2.3"/>
        <status state="operational"/>
    </component>
</local-definitions>
<observation uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab">
    <description><p></p></description>
    <method>TEST</method>
    <type>finding</type>
    <origin>
        <actor type="party" uuid-ref="f4568fda-c6d2-4640-adec-0012015af7d0" />
        <actor type="tool"  uuid-ref="9d194268-a9d1-4c38-839f-9c4aa57bf71e" />
    </origin>
    <relevant-evidence href="./raw_scans/scanner_output.csv">
        <description><p>Optional pointer to the raw scanner output that generated 
            this POA&amp;M entry.</p></description>
    </relevant-evidence>
    <collected>2023-10-10T00:00:00Z</collected>
</observation>
<!-- risk -->
<poam-item uuid="0be71cd3-f850-47db-836f-14511edbd90e">
    <!-- cut -->
    <related-observation observation-uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab" />
</poam-item>

Individual POA&M Entries: Asset Identifiers

For scanner tool findings, impacted assets are identified using the subject field, one field for each impacted asset. The type flag should be set to either inventory-item or component. The uuid-ref flag must point to an inventory item or component defined in the SSP inventory or POA&M local-definitions.

All details about the asset become available as a result of that UUID reference, such as IP address, fully qualified domain name (FQDN), and the asset’s point of contact. If an inventory-item contains an implemented-component field, those linked component details are also considered to be part of the inventory-item itself.

When providing a monthly POA&M to FedRAMP using OSCAL, the inventory may be delivered either by:

  • delivering the entire OSCAL-based SSP file, including the latest system inventory; or

  • duplicating all component and inventory-item assemblies from the system-implementation assembly of the SSP to the local-definitions assembly of the POA&M. Any role or party citations in this content must also be duplicated from the SSP metadata assembly to the POA&M metadata assembly.

Screenshot of the FedRAMP POA&M template showing entry row asset identifier.

FedRAMP POA&M entry asset identifier.

System Inventory

When providing a monthly POA&M to FedRAMP using OSCAL, the OSCAL-based inventory may be delivered either:

  • by delivering the entire OSCAL-based SSP file, including the latest system inventory; or
  • by duplicating all component and inventory-item assemblies from the system-implementation assembly of the SSP to the local-definitions assembly of the POA&M.

See POA&M - Importing the System Security Plan for more information.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

<local-definitions>
    <component uuid="75b059f2-a9ba-40b1-a1e0-881196ca1ead" type="virtual">
        <title>Component Definition</title>
        <description>
            <p>A virtual component.</p>
        </description>
        <prop name="asset-type" value="operating-system" />
        <prop ns="http://fedramp.gov/ns/oscal" name="name" value=" Linux Flavor"/>
        <prop name="version" value="1.2.0" />
        <status state="operational" />
    </component>
    <inventory-item uuid="deb26a75-6d97-4811-ae0e-ae1c710366c1">
        <description><p>An instance of the above component.</p></description>
        <prop name="ipv4-address" value="10.10.10.10"/>
        <prop name="fqdn" value="host.domain.cloud"/>
        <implemented-component component-id="75b059f2-a9ba-40b1-a1e0-881196ca1ead" />
    </inventory-item>
    <inventory-item uuid="02075556-3660-4112-8982-02fc7d6fac00" />   <!-- cut -->
    <inventory-item uuid="5efe2c07-9fdf-453a-8457-6471046082fb" />   <!-- cut -->
</local-definitions>

<observation uuid="6841d8eb-a72c-4672-acc2-2fd265d9617d">
    <!-- description, method, type -->
    <subject type="component" uuid-ref="75b059f2-a9ba-40b1-a1e0-881196ca1ead" />
    <subject type="inventory-item" uuid-ref="f61f4408-2cb8-444a-a312-bc88412e7c61" />
    <subject type="inventory-item" uuid-ref="02075556-3660-4112-8982-02fc7d6fac00" />
    <subject type="inventory-item" uuid-ref="5efe2c07-9fdf-453a-8457-6471046082fb" />
    <!-- origin, relevant-evidence -->
</observation>
<!-- risk -->
<poam-item uuid="0be71cd3-f850-47db-836f-14511edbd90e">
    <!-- title, description, POA&M ID, collected -->
    <related-observation observation-uuid="6841d8eb-a72c-4672-acc2-2fd265d9617d" />
</poam-item>

Individual POA&M Entries: Weakness Information

Weakness details are identified in the risk assembly. The Weakness Name appears in the title field, and the Weakness Description appears in the description field. The status field is initially set to open.

The Weakness Source Identifier requires a FedRAMP extension. Within the characterization’s origin, an actor must be specified for the tool itself. Assign the vulnerability-id and plugin-id FedRAMP extensions as properties to this actor.

Information provided by the tool that characterizes the risk is captured as facet fields. When the scanner tool provides risk values from other recognized systems, such as a CVE number, IAVAM severity, or CVSS metric, the OSCAL-defined name and system values must be used, in addition to the tool value being assigned to the value attribute. For example, if the scanner tool provides a CVE number, the risk-metric field’s system flag value should reflect http://cve.mitre.org as the system, not the scanner tool.

FedRAMP-required facet fields, such as likelihood and impact, have a system flag with a value of http://fedramp.gov/ns/oscal. FedRAMP-required facets must also have a prop with the name flag set to state and the value flag set to either initial or adjusted. There must always be initial facets. If adjusted, there may be adjusted facets as well.

Screenshot of the FedRAMP POA&M template showing entry row weakness information.

FedRAMP POA&M entry weakness information.

Risk Metric Fields

The facet fields are designed to allow risk values and identifiers from different frameworks, systems, and tools to co-exist in the same risk assembly. For example, a scanning tool may provide risk values assigned by the tool itself, as well as a CVE identifier, IAVM severity score, and CVSS metrics. If the system is subject to multiple frameworks using different risk score values or risk calculation methods, they may each be expressed in their own characterization assembly.

Common values for the system flag include:

If a tool provides a value with no clear source of information for defining the value, use the special “unknown” system value: http://csrc.nist.gov/ns/oscal/unknown

Ideally scanner tool vendors will define a “system” value for their own tools. Until that happens, FedRAMP recommends either using the URL for the vendor’s web site or the OSCAL-defined system value for an “unknown” system: http://csrc.nist.gov/ns/oscal/unknown

Until this matures and clear system values are widely available across the industry, FedRAMP only requires that the same system value be used consistently throughout the POA&M for a given tool and keep the facet values from a given tool within the same characterization assembly which cites the tool as an actor.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

<risk uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7">
    <title>Weakness Name</title>
    <description><p>This is the Weakness Description.</p></description> 
    <statement>
        <p>This is the tool-provided statement about the identified risk.</p>
        <p>If no risk statement from tool, set to 'No Risk Statement'.</p>
    </statement>

    <prop ns="http://fedramp.gov/ns/oscal" name="impacted-control-id"
          value="control-id" />

    <status>open</status>

    <characterization>
        <origin>
            <actor type="tool" actor-uuid="9d194268-a9d1-4c38-839f-9c4aa57bf71e">
                <prop name="vulnerability-id" 
                    ns="http://fedramp.gov/ns/oscal" value="VulID-001"/>
                <prop name="plugin-id"  
                    ns="http://fedramp.gov/ns/oscal" value="Plugin-ID"/>
            </actor>
        </origin>
        <facet name="iavam-severity" value="high" system="https://us-cert.cisa.gov" />
        <facet name="AV" value="network"  system="http://www.first.org/cvss/v3.1" />
        <facet name="vulnerability-id" value="CVE-2020-00000" 
            system="http://cve.mitre.org" />
        <facet name="impact" value="high"   
               system="http://csrc.nist.gov/ns/oscal/unknown" />
    </characterization>

    <characterization>
        <origin>
            <actor type="party" uuid-ref="49f73135-efab-4275-9a79-003656ad890" />
        </origin>
        <facet name="likelihood" value="high" system="http://fedramp.gov/ns/oscal">
            <prop name="state" value="initial" />
        </facet>
        <facet name="impact" value="high" system="http://fedramp.gov/ns/oscal">
            <prop name="state" value="initial" />
        </facet>
        <facet name="priority" value="1" system="http://fedramp.gov/ns/oscal" />
    </characterization>
</risk>

Binding Operational Directive 22-01 Vulnerabilities

FedRAMP, in accordance with Binding Operational Directive (BOD) 22-01 and in consultation with the JAB and DHS CISA, emphasized that CSPs who maintain federal information fall within the scope defined by the BOD. CSPs must track their system’s vulnerabilities against the CISA catalog of known exploited vulnerabilities (KEV). CSPs must identify in their POA&M any system vulnerabilities that are in the KEV catalog.

A FedRAMP extension property with the name flag set to kev-catalog is used to indicate that a vulnerability is in the CISA KEV catalog. The kev-catalog property’s value flag may be set to yes or no; however, the property need only be present when its value is yes.

CSP vulnerabilities that are in the CISA KEV catalog must be remediated by the due date specified in the catalog. This date must be included in the CSP’s POA&M via a FedRAMP extension property with the name flag set to kev-due-date. This property’s value must be set to a valid date data type.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

<risk uuid="4840279d-72ec-4b5a-b685-96e45a2b8285">
    <title>Weakness Name</title>
    <description><p>This is the Weakness Description.</p></description>
    
    <statement>
        <p>This is the tool-provided statement about the identified risk.</p>
        <p>If no risk statement from tool, set to 'No Risk Statement'.</p>
    </statement>
    <prop name="kev-catalog" ns="http://fedramp.gov/ns/oscal" value="yes"/>
    <prop name="kev-due-date" ns="http://fedramp.gov/ns/oscal" value="2022-09-30"/>
    <status>open</status>
    <!-- characterizations -->

</risk>

Within the risk assembly, there must be a response assembly containing the tool’s recommended mitigation. The type flag must be set to recommendation. The origin field’s actor type flag must be set to tool, and the uuid-ref must contain the UUID of the tool that generated the recommendation. Additional remediation recommendations may also be present, such as the assessor’s recommendation copied from the SAR.

There must also be a response assembly containing the CSP’s intended mitigation plan. The type flag must be set to planned. The origin field’s actor type flag must be set to party, and the uuid-ref must contain the UUID of either the CSP organization itself or the individual overseeing the activities, such as the ISSO.

Resources Required are identified within the planned response assembly using the required assembly. Use the description field for a free-form explanation of required resources. Use one or more subject fields to link to a specific party, component, inventory-item, system user, or resource.

Screenshot of the FedRAMP POA&M template showing entry row remediation plan.

FedRAMP POA&M entry remediation plan.

Accepted Values

  • The type flag on the remediation field:
    • recommendation
    • planned
  • The type flag on the recommendation-origin field:
    • party
    • tool
  • The type flag on the subject field:
    • party
    • component
    • inventory-item
    • location
    • user
Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

<risk uuid="1689ec06-100a-4fed-9df9-e69f07d3f3c9">
    <!-- title, description, statement, status, characterization -->
    <response uuid="a3106e23-8b79-4b1b-abf4-74f16c51ad0c" lifecycle="recommendation">
        <title>Tool's Recommendation</title>
        <description><p>Tool-provided recommendation.</p></description>
        <origin >
            <actor type="tool" actor-uuid="9d194268-a9d1-4c38-839f-9c4aa57bf71e"></actor>
        </origin>
    </response>
    
    <response uuid="69344d05-937e-40f4-9c3f-9aa8702ad99d" lifecycle="recommendation">
        <title>Assessor's Recommendation</title>
        <description><p>Assessor-provided recommendation.</p></description>
        <origin >
            <actor type="party" uuid-ref="49f73135-efab-4275-9a79-003656ad890a"></actor>
        </origin>
    </response>
    
    <response uuid="e9ee6fe2-856f-42c7-8c2e-ff6466d31010" lifecycle="planned">
        <title>CSP's Remediation Plan</title>
        <description>
            <p>Describe the CSP's intended approach to remediating this risk.</p>
        </description>
        <origin>
            <actor type="party" actor-uuid="49f73135-efab-4275-9a79-003656ad890a"></actor>
        </origin>
        
        <required-asset uuid="7bd1a61e-4fda-4c52-a447-14072ef6e042">
            <subject subject-uuid="6e0d71b5-3dac-4a9b-b60d-da61b95eccb9" type="party" />
            <subject subject-uuid="6e0d71b5-3dac-4a9b-b60d-da61b95eccb9" type="party" />
            <description><p>Describe required resources.</p></description>
        </required-asset>
    </response>
</risk>

Planned Remediation Schedule

The Planned Milestones are identified within the response assembly using the task assemblies. There must be at least one task assembly of type milestone. There may be additional tasks assemblies of type action or milestone. This collection of action and milestone tasks serves as a high-level remediation timeline. A POA&M tool should offer the option of viewing either just the milestones or all actions and milestones.

Each task assembly must have a title field that briefly names the milestone and a description field. OSCAL requires both the title and description fields to be present; however, FedRAMP allows description to be empty. All milestone task assemblies must contain a timing assembly with an on-date field, whereas the timing assembly for action tasks must contain either an on-date or within-date-range field. FedRAMP presumes the Scheduled Completion Date for the POA&M item is the farthest specified timing assembly date in the future because it indicates when all remediation schedule milestones and actions will be complete.

Screenshot of the FedRAMP POA&M template showing entry row planned remediation schedule.

FedRAMP POA&M entry planned remediation schedule.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

<risk uuid="1689ec06-100a-4fed-9df9-e69f07d3f3c9">
    <!-- title, description, statement, status, characterization -->
    <response uuid="e9ee6fe2-856f-42c7-8c2e-ff6466d31010" lifecycle="planned">
        <title>CSP's Remediation Plan</title>
        <description>
            <p>Describe the CSP's intended approach to remediating this risk.</p>
        </description>
        <origin>
            <actor type="party" uuid-ref="49f73135-efab-4275-9a79-003656ad890a"></actor>
        </origin>
        
        <required-asset uuid="7bd1a61e-4fda-4c52-a447-14072ef6e042">
            <subject subject-uuid="6e0d71b5-3dac-4a9b-b60d-da61b95eccb9" type="party" />
            <subject subject-uuid="6e0d71b5-3dac-4a9b-b60d-da61b95eccb9" type="party" />
            <description><p>Describe required resources.</p></description>
        </required-asset>
        <task uuid="a12dea1d-e4d1-4f09-aacf-1eaf203a3092" type="milestone">
            <title>[Example]Milestone 1</title>
            <description><p>Optional description</p></description>
            <timing>
                <on-date date="2023-07-02T00:00:00Z"/>
            </timing>
        </task>
        <task uuid="08c50f90-3b08-49fd-862d-32ec96e6bee5" type="milestone">
            <title>[Example]Milestone 2</title>
            <description><p>Optional description</p></description>
            <timing>
                <on-date date="2023-07-07T00:00:00Z"/>
            </timing>
        </task>
    </response>                        
    <!-- remediation-tracking -->
</risk>

OSCAL supports relationships between tasks, via sub-tasks and task dependencies. FedRAMP does not require the use of sub-tasks or dependencies; however, if present, such tasks are subject to the same constraints mentioned above.

Risk Tracking

Tracking is initiated by adding the risk-log assembly to the risk assembly, which must have one or more entry assemblies. Each milestone change, vendor check-in, periodic status update, and action performed in the pursuit of remediating the risk is entered here as individual entry assemblies.

Each entry assembly must have a title, description, and start field. There may also be an end, logged-by, and related-response fields. If the end field is missing, it is presumed to have the same value as the start field. The logged-by field is optional and contains the UUID of the person (party) who made the entry. The related-response field is optional and contains the UUID of the risk response that describes the recommended or actual plan for addressing the risk.

For performed actions, start should reflect when the action was performed. For status updates, this should reflect the effective date of the status information.

If it is appropriate to attach evidence related to risk tracking, add an observation assembly with the appropriate evidence attached. If used, the observation assembly must have a type tag of risk-tracking.

Screenshot of the FedRAMP POA&M template showing entry row risk tracking.

FedRAMP POA&M entry risk tracking.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

<risk uuid="e552fb72-d662-4c01-b2d7-4dcb2086bb07">
    <!-- title, description, statement, status, response -->
    <risk-log>
        <entry uuid="1b500d56-1936-41eb-8b60-a2984937ab89">
            <title>Activity 1</title>
            <description />
            <start>2023-07-02T00:00:00Z</start>
            <end>2023-08-02T00:00:00Z</end>
            <logged-by party-uuid="339f168f-636b-4a53-8256-00465203776f"/>
            <!-- cut related response -->>
        </entry>
        <entry uuid="316fb3fe-927a-49a1-9a72-a58722862623">
            <title>Activity 2</title>
            <description />
            <start>2023-07-07T00:00:00Z</start>
        </entry>
        <entry uuid="d084a039-bdd1-4ccd-a06a-53355e07fa2f">
            <title>Vendor Check-in</title>
            <description><p>Description of the result of the vendor check-in.</p>
            </description>
            <start>2023-07-07T00:00:00Z</start>
            <prop name="vendor-dependency" ns="http://fedramp.gov/ns/oscal" 
                  value="vendor-check-in" />
        </entry>
        <entry uuid="0b09e341-cf3c-4de7-b728-751c6e88b653">
            <title>Risk Closed</title>
            <description>
                <p>Describe what action(s) the CSP took to close the risk.</p>
                <p>[EXAMPLE]Applied patch. Vulnerability no longer found in subsequent  
                   scan.</p>
            </description>
            <start>2023-07-07T00:00:00Z</start>
            <status-change>closed</status-change>
        </entry>
    </risk-log>
</risk>

Deviations and Vendor Dependencies

After risks are identified a deviation may be appropriate, or a vendor dependency may exist. As deviations are identified, the original risk information is not modified. Additional content is added to identify these changes. Typically, an additional observation is added and linked to the poam-item, and additional facet fields are added to the risk assembly. There may be both Operational Requirement (OR) and Risk Assessment (RA) information in the same risk assembly, each with its own observation.

Deviations and Vendor Dependency Requirements

FedRAMP’s requirements for deviation requests and vendor dependency handling are defined in the Continuous Monitoring Strategy Guide, and remain the same when delivering content in OSCAL format.

False Positive (FP)

To initially identify a false positive, add a false-positive FedRAMP Extension property to the risk field and set its value to investigating. Once evidence is identified to support the FP, change the risk assembly’s false-positive value to pending and add an observation with the type field set to false-positive. Typically, the method is set to EXAMINE. Add an additional related-observation field linking the poam-item to the new observation.

Once the FP is approved, change the false-positive extension’s value to approved and close the risk as described in the Risk Closure section.

Screenshot of the FedRAMP POA&M template showing a false positive entry.

False Positive (FP)

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

<observation uuid="46209140-8263-4e74-b3c9-cead4ffed22c">
    <title>False Positive</title>
    <description><p>Describe the false positive here.</p></description>
    <method>EXAMINE</method>
    <type>false-positive</type>
    <relevant-evidence href="#53af7193-b25d-4ed2-a82f-5954d2d0df61">
        <description><p>A screen shot showing the setting is correct</p></description>
    </relevant-evidence>
    <relevant-evidence href="https://vendor.site/article/describing/something.htm">
        <description><p>Vendor detail describing why this happens.</p></description>
    </relevant-evidence>
    <collected>2023-10-10T00:00:00Z</collected>
</observation>

<risk uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7">
    <title>Vulnerability Title</title>
    <description><p>Vulnerability description</p></description>
    <statement><p>Risk statement.</p></statement>
    <prop name="impacted-control-id" ns="http://fedramp.gov/ns/oscal" value="ac-2" />
    <prop name="vendor-dependency" ns="http://fedramp.gov/ns/oscal" value="tracking" />
    <prop name="operational-requirement" ns="http://fedramp.gov/ns/oscal" value="approved" />
    <prop name="false-positive" ns="http://fedramp.gov/ns/oscal" value="approved" />
    <prop name="risk-adjustment" ns="http://fedramp.gov/ns/oscal" value="withdrawn" />
    <status>open</status>
</risk>

<poam-item uuid="6f5fff73-cac6-4da0-a0d9-0f931a5efafa">
    <!-- cut -->
    <related-observation observation-uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab" />
    <related-observation observation-uuid="46209140-8263-4e74-b3c9-cead4ffed22c" />
    <associated-risk risk-uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7" />
</poam-item>

Add an entry to the risk log when investigating, as well as for submission and approval events respectively.

Operationally Required (OR)

To initially identify an OR, add an operational-requirement FedRAMP Extension property to the risk field and set its value to investigating. Once evidence is identified to support the OR, change the risk assembly’s operational-requirement value to pending and add an observation with the type field set to operational-requirement. Typically, the method is set to EXAMINE; however, another method may be identified if more appropriate. Add an additional related-observation field linking the poam-item to the new observation.

Once the OR is approved, change the operational-requirement extension value to approved.

If a risk adjustment is also required for OR approval (such as FedRAMP requires for High ORs), simply also follow the instructions in the next section for risk adjustments. When there is both an OR and an RA, each will have their own observation assembly and respective related-observation entries in the poam-item assembly.

Screenshot of the FedRAMP POA&M template showing an operational requirement entry.

Operational Requirement (OR).

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

<observation uuid="46209140-8263-4e74-b3c9-cead4ffed22c">
    <title>Operational Requirement</title>
    <description><p>Provide the justification for the OR.</p></description>
    <method>EXAMINE</method>
    <type>operational-requirement</type>
    <relevant-evidence href="#53af7193-b25d-4ed2-a82f-5954d2d0df61">
        <description><p>A screen shot showing impact when patch is applied.</p>
        </description>
    </relevant-evidence>
    <relevant-evidence href="https://vendor.site/article/describing/something.html">
        <description><p>Vendor detail describing why this happens.</p></description>
    </relevant-evidence>
    <collected>2023-10-10T00:00:00Z</collected>
</observation>

<risk uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7">
    <title>Vulnerability Title</title>
    <description><p>Vulnerability description</p></description>
    <statement><p>Risk statement.</p></statement>
    <prop name="impacted-control-id" ns="http://fedramp.gov/ns/oscal" value="ac-2" />
    <prop name="operational-requirement" ns="http://fedramp.gov/ns/oscal" value="approved" />
    <status>open</status>
</risk>

<poam-item uuid="6f5fff73-cac6-4da0-a0d9-0f931a5efafa">
    <!-- cut -->
    <related-observation observation-uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab" />
    <related-observation observation-uuid="46209140-8263-4e74-b3c9-cead4ffed22c" />
    <associated-risk risk-uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7" />
</poam-item>

Add an entry to the risk log when investigating, as well as for submission and approval events respectively.

Risk Adjustment (RA)

To initially identify an RA, add a risk-adjustment FedRAMP Extension property to the risk field and set its value to investigating. Once evidence is identified or mitigating factors are implemented, change the risk assembly’s risk-adjustment value to pending and add an observation with the type field set to risk-adjustment. Typically, the method is set to EXAMINE; however, another method may be identified if more appropriate. Add an additional related-observation field linking the poam-item to the new observation.

As mitigating factors are identified or implemented, add mitigating-factor assemblies to the risk assembly. There must be at least one mitigating factor for an RA. Based on those factors, add additional facet assemblies with adjusted risk values.

Once the RA is approved, change the risk-adjustment extension value to approved.

If the RA is performed in concert with an OR (such as FedRAMP requires for High ORs), simply also follow the instructions in the previous section for operationally required risks. When there is both an OR and an RA, each will have their own observation assembly and respective related-observation entries in the poam-item assembly.

Screenshot of the FedRAMP POA&M template showing a risk adjustment entry.

Risk Adjustment (RA).

Calculated Risk

Both initial and residual risk values are calculated based on likelihood and impact values.

Every POA&M entry must have initial likelihood and impact values:

1
2
3
4
5
6

<facet name="likelihood" value="high" system="http://fedramp.gov/ns/oscal">
  <prop name="state" value="initial" />
</facet>
<facet name="impact" value="high" system="http://fedramp.gov/ns/oscal">
  <prop name="state" value="initial" />
</facet>

When justifying a risk adjustment, either the likelihood or impact may be lowered. It is possible to justify lowering both. Even if just one value is lowered, both residual risk values must be present:

1
2
3

<facet name="likelihood" value="low" system="http://fedramp.gov/ns/oscal">
  <prop name="state" value="adjusted" />
</facet>

Add an entry to the risk log when investigating, for the completion of each mitigating factor’s implementation (if appropriate), as well as for submission and approval events respectively.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

<observation uuid="46209140-8263-4e74-b3c9-cead4ffed22c">
    <type>risk-adjustment</type>
    <relevant-evidence>
        <description>
            <p>Describe the risk adjustment evidence here.</p>
        </description>
        <link href="#53af7193-b25d-4ed2-a82f-5954d2d0df61" rel="evidence"/>
        <remarks><!-- cut --></remarks>
    </relevant-evidence>
    <collected>2023-10-10T00:00:00Z</collected>
</observation>
<risk uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7">
    <prop name="risk-adjustment" ns="http://fedramp.gov/ns/oscal" value="approved" />
    <characterization>
        <facet name="likelihood" value="high" system="http://fedramp.gov/ns/oscal">
            <prop name="state" value="initial" />
        </facet>
        <facet name="impact" value="high" system="http://fedramp.gov/ns/oscal">
            <prop name="state" value="initial" />
        </facet>
        <facet name="likelihood" value="moderate" system="http://fedramp.gov/ns/oscal">
            <prop name="state" value="adjusted">
                <remarks>
                    <p>Explain why likelihood was adjusted.</p>
                </remarks>
            </prop>
        </facet>        
        <facet name="impact" value="low" system="http://fedramp.gov/ns/oscal">
            <prop name="state" value="adjusted">
                <remarks>
                    <p>Explain why impact was adjusted.</p>
                </remarks>
            </prop>
        </facet>
    </characterization>
    <mitigating-factor uuid="260d3c0a-fc2e-4627-9fb9-a003acdc4b14">
        <description><p>Describe mitigating factor</p></description>
    </mitigating-factor>
</risk>
<poam-item uuid="6f5fff73-cac6-4da0-a0d9-0f931a5efafa">
    <related-observation observation-uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab" />
    <related-observation observation-uuid="46209140-8263-4e74-b3c9-cead4ffed22c" />
    <associated-risk risk-uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7" />
</poam-item>

Vendor Dependency

To initially identify a vendor dependency, add a vendor-dependency FedRAMP Extension property to the risk field and set its value to investigating. Once evidence is identified to support the dependency, change the risk assembly’s vendor-dependency value to tracking and add an observation with the type field set to vendor-dependency. Typically, the method is set to EXAMINE; however, another method may be identified if more appropriate. Add an additional related-observation field linking the poam-item to the new observation.

Within the observation assembly, explain the dependency in the description field. The observation assembly must include a subject-reference identifying the component or inventory-item. The Vendor Dependency Product Name is provided from the component or inventory-item details.

Add a separate relevant-evidence assembly for each piece of evidence supporting the dependency. Attached evidence, such as screen shots, must be defined as a resource in the back-matter, and cited using a URI fragment (hashtag, followed by the UUID of the resource.)

Once the vendor publishes a resolution, change the vendor-dependency extension value to resolved.

Screenshot of the FedRAMP POA&M template showing a vendor dependency.

Vendor Dependency (VD).

If the Vendor Dependent Product Name is not already defined as an individual component, add a component to the local-definitions assembly describing the component.
Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

<observation uuid="46209140-8263-4e74-b3c9-cead4ffed22c">
    <title>Vendor Dependency</title>
    <description><p>Describe the vendor dependency here.</p></description>
    <method>INTERVIEW</method>
    <type>vendor-dependency</type>
    <subject subject-uuid="a49ed61e-fca1-4ffa-b5e7-c23a2375a7a0" type="component" />
    <relevant-evidence href="#53af7193-b25d-4ed2-a82f-5954d2d0df61">
        <description><p>A screen shot showing the setting is correct</p></description>
    </relevant-evidence>
    <relevant-evidence href="https://vendor.site/article/describing/something.htm">
        <description><p>Vendor detail describing why this happens.</p></description>
    </relevant-evidence>
    <collected>2023-10-10T00:00:00Z</collected>
</observation>

<risk uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7">
    <title>Vulnerability Title</title>
    <description><p>Vulnerability description</p></description>
    <statement><p>Risk statement.</p></statement>
    <prop name="impacted-control-id" ns="http://fedramp.gov/ns/oscal" value="ac-2" />
    <prop name="vendor-dependency" ns="http://fedramp.gov/ns/oscal" value="tracking" />
    <status>open</status>
</risk>

<poam-item uuid="6f5fff73-cac6-4da0-a0d9-0f931a5efafa">
    <!-- cut -->
    <related-observation observation-uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab" />
    <related-observation observation-uuid="46209140-8263-4e74-b3c9-cead4ffed22c" />
    <associated-risk risk-uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7" />
</poam-item>

Add an entry to the risk log when investigating, as well as for each vendor check-in. As the CSP performs the required regular vendor check-ins, each must be added to the risk-log assembly as an additional entry. The title should be set to Vendor Check-in, the start field must indicate when the check-in occurred, and the result of the check-in must be described in the description field.

When the vendor publishes the resolution, add another risk log entry reflecting the date the resolution was published.

Evidence and Artifacts

All evidence collected must be attached (by relative URI path or embedded Base64) as a resource in the back-matter. See the Citations and Attachments in OSCAL Files section for more information.

Evidence must have the FedRAMP extension type with the value set to evidence.

Additional type fields may also be added with values such as plan, policy, or image. This adds clarity and can ensure specific tables are generated properly.

Artifacts may be cited from an observation as an observation-source.

Evidence may be cited from an observation as relative-evidence.

A POA&M tool could use either an rlink or base64 field here, and may use both. If both are present, FedRAMP tools will give preference to the base64 content. If an rlink is used, its href should have a relative path to ensure the path remains valid when the OSCAL content is delivered to FedRAMP.

Tools may include multiple rlink fields within the same resource assembly. This may be useful if the CSP wanted to maintain an absolute link to the file’s authoritative source location as well as a relative link suitable for delivery to FedRAMP.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19

<!-- poam-items -->
<back-matter>
    <resource uuid="f32b7ab1-baf1-451a-b3a1-1dfdadbe8dc7">
        <title>[EXAMPLE]AC Policy</title>
        <prop name="type" ns="http://fedramp.gov/ns/oscal" value="evidence" />
        <prop name="type" ns="http://fedramp.gov/ns/oscal" value="policy" />
        <prop name="version">2.1</prop>
        <prop name="publication">2018-11-11T00:00:00Z</prop>
        <rlink media-type="application/pdf" href="./artifacts/AC_Policy.pdf"></rlink>
        <base64 media-type="application/pdf" filename="AC_Policy.pdf">00000000</base64>
    </resource>
  
    <resource uuid="53af7193-b25d-4ed2-a82f-5954d2d0df61">
        <title>[EXAMPLE]Screen Shot</title>
        <prop name="type" ns="http://fedramp.gov/ns/oscal" value="evidence" />
        <rlink media-type="image/jpeg" href="./evidence/screen-shot.jpg"></rlink>
        <base64 media-type="image/jpeg" filename="screen-shot.jpg">00000000</base64>
    </resource>
</back-matter>

Risk Closure

When a risk is closed through remediation or false-positive approval, they must be closed. The risk should remain in the POA&M with the following changes.

First, in the risk assembly, change the status field to closed. Then make a final entry in the risk-log assembly. In the entry assembly, summarize the reason for closure in the description field, and set the start field to indicate the date of closure and the status-change field to closed. Individual actions performed for closure should each have their own entries in the risk log.

If it is appropriate to attach evidence of closure, add an observation assembly with the type field set to closure, and cite the appropriate evidence.

Screenshot of the FedRAMP POA&M template showing closure of a risk entry.

Risk Closure.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

<observation uuid="46209140-8263-4e74-b3c9-cead4ffed22c">
    <title>Risk Closure</title>
    <description><p>Describe the closure evidence here.</p></description>
    <method>EXAMINE</method>
    <type>closure</type>
    <subject subject-uuid="a49ed61e-fca1-4ffa-b5e7-c23a2375a7a0" type="component" />
    <relevant-evidence href="#53af7193-b25d-4ed2-a82f-5954d2d0df61">
        <description><p>A screen shot showing the setting is correct</p></description>
    </relevant-evidence>
    <relevant-evidence href="https://vendor.site/article/describing/something.htm">
        <description><p>Vendor detail describing why this happens.</p></description>
    </relevant-evidence>
    <collected>2023-10-10T00:00:00Z</collected>
</observation>

<risk uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7">
    <!-- title, description, statement, status, mitigation, response -->
    <risk-log>
        <entry uuid="1b500d56-1936-41eb-8b60-a2984937ab89">
        </entry>
        <entry uuid="316fb3fe-927a-49a1-9a72-a58722862623">
        </entry>
        <entry uuid="d084a039-bdd1-4ccd-a06a-53355e07fa2f">
        </entry>
        <entry uuid="0b09e341-cf3c-4de7-b728-751c6e88b653">
            <title>Risk Closed</title>
            <description>
                <p>Describe what action(s) the CSP took to close the risk.</p>
                <p>[EXAMPLE]Applied patch. Vulnerability no longer found in subsequent scan.</p>
            </description>
            <start>2023-07-07T00:00:00Z</start>
            <status-change>closed</status-change>
        </entry>
    </risk-log>
</risk>
<poam-item uuid="6f5fff73-cac6-4da0-a0d9-0f931a5efafa">
    <!-- cut -->
    <related-observation observation-uuid="0aa54106-8a63-4953-ac0d-30ff91f8d4ab" />
    <related-observation observation-uuid="46209140-8263-4e74-b3c9-cead4ffed22c" />
    <associated-risk risk-uuid="ae628cc5-b64c-4030-af30-57e6b24a6ae7" />
</poam-item>

CVSS Scoring

Common Vulnerability Scoring System (CVSS) metrics may be added to any risk-assembly using risk-metric fields.

Tools should accept either the upper-case abbreviation or the lower-case name on a field-by-field basis. For example, it should be acceptable to use AV for access vector, and privileges-required for privileges required, provided both have a system value of http://www.first.org/cvss/v3.1.

All CVSS metrics must be in the same CVSS version, as identified by the system flag, for successful computation. Tool developers should ensure the tool performs CVSS calculations as defined by the Forum of Incident Response and Security Teams (FIRST) at https://www.first.org/cvss/.

Representation
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

<risk id="risk-3-1">
    <!-- title, description, statement, status -->
    <characterization>
        <origin>
            <actor type="party" uuid-ref="9d194268-a9d1-4c38-839f-9c4aa57bf71e" />
        </origin>
        
        <!-- CVSS Metrics using V3.1 using abbreviations -->
        <facet name="AV" system="http://www.first.org/cvss/v3.1" value="network"/>
        <facet name="AC" system="http://www.first.org/cvss/v3.1" value="high"/>
        <facet name="PR" system="http://www.first.org/cvss/v3.1" value="low"/>
        
        <!-- CVSS Metrics using V3.1 using names -->
        <facet name="access-vector" system="http://www.first.org/cvss/v3.1" 
               value="network"/>
        
        <facet name="access-complexity" system="http://www.first.org/cvss/v3.1" 
               value="high"/>
        
        <facet name="privileges-required" system="http://www.first.org/cvss/v3.1" 
               value="low"/>
    </characterization>
</risk>