Control Implementation Statements
Implementation
Typically, Statements:the Generalcontrols in the FedRAMP baselines have lettered parts (a., b., etc.). A few only have a top-level statement with no parts. Current FedRAMP templates expect responses at the lettered part level when present and at the top-level otherwise.
OSCAL SSPs cite controls and control requirement statements in responses.
Within the OSCAL FedRAMP baselines, each control statement is assigned an identifier. Any lettered parts are also assigned identifiers.
Citing statement identifiers correctly is critical to automated processing.
See Citing Control Statements for important information.
Typical
Organization:
Most Multi-PartFedRAMP Statementscontrols have two or more lettered parts. FedRAMP expects control responses at this level.
ThereWithin mustthe becontrol-implementation one/ implemented-requirements array, each entry includes:
- a required
uuidfield - a required
control-idfield that cites the control using its id from the baseline. - a required
statementsarray. Each array entry includes:- a
statement-idfield that cites the control statementassemblyusing its id from the baseline. - a
by-componentsarray- See Responding By Component for
eachmoreletteredinformation.
part,such - See Responding By Component for
aswith - a
Multi-Part Statement Representation
<!-system-security-plan:
control-implementation:
implemented-requirements:
- system-implementationuuid: 11111111-2222-4000-8000-012000010000
control-id: ac-1
statements:
-->
<control-implementation>
<!-- cut -->
<implemented-requirement uuid="uuid-value" control-id="ac-2">
<statement statement-id="id: ac-2_smt.a"><!--1_smt.a
cutuuid: --></statement>11111111-2222-4000-8000-012000010100
<!--by-components:
repeat[content for b, c, d, e, f, g, h, i, j -->
<statement statement-id="ac-2_smt.k"><!-- cut --></statement>
</implemented-requirement>
</control-implementation>cut]
Organization: Single StatementNon-Typical
If there are no lettered parts in the control definition, such as with AC-2 (1), there must be exactly one statement assembly.
Single-Statement Representation
A single-statement representation is identical to a typical multi-part statement representation, except for the following:
- there is only one entry in the
statementsarray - the
statement-idvalue cites the baseline ID for thestatementpart itself instead of one of its child parts.
<!-
system-security-plan:
control-implementation:
implemented-requirements:
- system-implementationuuid: 11111111-2222-4000-8000-012000010000
control-id: ac-2.1
statements:
--> <control-implementation>statement-id: <!-- cut -->
<implemented-requirement control-id="ac-2.1">1_smt
<statementuuid: statement-id="ac-2.1_smt"><!--11111111-2222-4000-8000-012000010100
cutby-components:
--></statement>[content </implemented-requirement>
</control-implementation>cut]
