Skip to content

Commit d145dfe

Browse files
David Waltermireaj-stein-nist
David Waltermire
authored and
aj-stein-nist
committed
Support for control mapping (#1150)
* Added mapping model supporting mapping controls and control statements between two catalogs. * Adjusted relationships based on PR #1150 discussions. Added type enumerations. * Included a simple example
1 parent ef28023 commit d145dfe

File tree

6 files changed

+244
-57
lines changed

6 files changed

+244
-57
lines changed

‎src/metaschema/examples/cis-sp-800-53-mapping.xml‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<!-- This is a mapping example used for development. This file should be moved to the oscal-content repo when this feature is ready. -->
3+
<mapping-collection xmlns="http://csrc.nist.gov/ns/oscal/1.0"
4+
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
5+
xsi:schemaLocation="http://csrc.nist.gov/ns/oscal/1.0 oscal-complete.xsd" uuid="3559d200-4849-41ac-a420-28b2ffa22c52">
6+
<metadata>
7+
<title>Example mapping between CIS controls and SP 800-53 rev5</title>
8+
<last-modified>2022-04-13T08:37:21.323321800-04:00</last-modified>
9+
<version>0.0.1</version>
10+
<oscal-version>1.1.0</oscal-version>
11+
</metadata>
12+
<mapping uuid="9eb2019c-f3be-4f96-947e-58876a46b2a9">
13+
<source-resource type="catalog" href="#a84961de-55ae-4bf3-a2d3-86cc32b651af"></source-resource>
14+
<target-resource type="catalog" href="#711085f6-c390-4b25-b5f1-30066a56073d"></target-resource>
15+
<map uuid="6a9a1161-770e-4556-9740-41e1809e14ea">
16+
<!-- Note: Once issue #1332 is resolved, one of the new relationships can be used, in place of subset-of, to represent that cis-1.1 is a stricter version of the same requirements defined by the combination of {cm-8 and cm-8.1}. -->
17+
<relationship>subset-of</relationship>
18+
<source type="control" id-ref="#cis-1.1"/>
19+
<target type="control" id-ref="#cm-8">
20+
<!-- TODO: consider a way to reference parameters allowing the review period of at least bi-annually to be described. This would allow for equivalent-to to be used. -->
21+
<!-- <using-param id="cm-08_odp.02">at least bi-annually</using-param>-->
22+
</target>
23+
<target type="control" id-ref="#cm-8.1"/>
24+
<remarks>
25+
<p>The combination of SP 800-53 CM-8 and CM-8(1) describe similar implementation requirements to CIS 1.1.</p>
26+
</remarks>
27+
</map>
28+
</mapping>
29+
<back-matter>
30+
<resource uuid="a84961de-55ae-4bf3-a2d3-86cc32b651af">
31+
<rlink href="cis-catalog.xml" media-type="application/oscal+xml"/>
32+
</resource>
33+
<resource uuid="711085f6-c390-4b25-b5f1-30066a56073d">
34+
<rlink href="https://github.com/usnistgov/oscal-content/raw/main/nist.gov/SP800-53/rev5/xml/NIST_SP-800-53_rev5_catalog.xml" media-type="application/oscal+xml"/>
35+
</resource>
36+
</back-matter>
37+
</mapping-collection>

‎src/metaschema/examples/computer-build_metaschema.xml‎

Lines changed: 0 additions & 57 deletions
This file was deleted.

‎src/metaschema/oscal_catalog_metaschema.xml‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@
1919
</remarks>
2020
<import href="oscal_control-common_metaschema.xml"/>
2121
<import href="oscal_metadata_metaschema.xml"/>
22+
<import href="oscal_mapping-common_metaschema.xml"/>
2223
<define-assembly name="catalog">
2324
<formal-name>Catalog</formal-name>
2425
<description>A collection of controls.</description>
@@ -173,6 +174,22 @@
173174
<assembly ref="part" max-occurs="unbounded">
174175
<group-as name="parts" in-json="ARRAY"/>
175176
</assembly>
177+
<define-assembly name="mapping">
178+
<formal-name>Mapping</formal-name>
179+
<description>A mapping between the containing control and another resource.</description>
180+
<define-flag name="uuid" as-type="uuid" required="yes">
181+
<formal-name>Mapping Identifier</formal-name>
182+
<description>The unique identifier for the mapping.</description>
183+
</define-flag>
184+
<model>
185+
<assembly ref="mapping-resource-reference" min-occurs="1">
186+
<use-name>target-resource</use-name>
187+
</assembly>
188+
<assembly ref="map" min-occurs="1" max-occurs="unbounded">
189+
<group-as name="maps" in-json="ARRAY"/>
190+
</assembly>
191+
</model>
192+
</define-assembly>
176193
<assembly ref="control" max-occurs="unbounded">
177194
<group-as name="controls" in-json="ARRAY"/>
178195
</assembly>

‎src/metaschema/oscal_complete_metaschema.xml‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@
1515
<p>This format represents a combination of all of the OSCAL models.</p>
1616
</remarks>
1717
<import href="oscal_catalog_metaschema.xml"/>
18+
<import href="oscal_mapping_metaschema.xml"/>
1819
<import href="oscal_profile_metaschema.xml"/>
1920
<import href="oscal_component_metaschema.xml"/>
2021
<import href="oscal_ssp_metaschema.xml"/>

‎src/metaschema/oscal_mapping-common_metaschema.xml‎

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
<?xml version="1.0" encoding="UTF-8"?>
2+
<?xml-model href="../../build/metaschema/toolchains/xslt-M4/validate/metaschema-check.sch" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>
3+
<METASCHEMA xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
4+
xmlns="http://csrc.nist.gov/ns/oscal/metaschema/1.0" xsi:schemaLocation="http://csrc.nist.gov/ns/oscal/metaschema/1.0 ../../build/metaschema/toolchains/xslt-M4/validate/metaschema.xsd" abstract="yes">
5+
<schema-name>OSCAL Mapping Model -- Common Models</schema-name>
6+
<schema-version>1.0.0</schema-version>
7+
<short-name>oscal-mapping-common</short-name>
8+
<namespace>http://csrc.nist.gov/ns/oscal/1.0</namespace>
9+
<json-base-uri>http://csrc.nist.gov/ns/oscal</json-base-uri>
10+
11+
<import href="oscal_metadata_metaschema.xml"/>
12+
13+
<define-assembly name="map">
14+
<formal-name>Mapping Entry</formal-name>
15+
<description>A relationship-based mapping between a source and target set consisting of members (i.e., controls, control statements) from the respective source and target.</description>
16+
<define-flag name="uuid" as-type="uuid" required="yes">
17+
<formal-name>Mapping Entry Identifier</formal-name>
18+
<description>The unique identifier for the mapping entry.</description>
19+
</define-flag>
20+
<model>
21+
<assembly ref="property" max-occurs="unbounded">
22+
<group-as name="props" in-json="ARRAY"/>
23+
</assembly>
24+
<assembly ref="link" max-occurs="unbounded">
25+
<group-as name="links" in-json="ARRAY"/>
26+
</assembly>
27+
<define-field name="relationship" as-type="token" min-occurs="1">
28+
<formal-name>Mapping Entry Relationship</formal-name>
29+
<description>The relationship type for the mapping entry, which describes the relationship between the effective requirements of the specified source and target sets.</description>
30+
<define-flag name="ns" as-type="uri">
31+
<formal-name>Relationship Value Namespace</formal-name>
32+
<description>A namespace qualifying the relationship's value. This allows different organizations to associate distinct semantics for relationships with the same name.</description>
33+
<remarks>
34+
<p>An organization MUST use a URI that they have control over. e.g., a domain registered to the organization in a URI, a registered uniform resource names (URN) namespace.</p>
35+
<p>When a <code>ns</code> is not provided, its value should be assumed to be <code>http://csrc.nist.gov/ns/oscal</code> and the name should be a name defined by the associated OSCAL model.</p>
36+
</remarks>
37+
</define-flag>
38+
<constraint>
39+
<allowed-values target=".[has-oscal-namespace('http://csrc.nist.gov/ns/oscal')]">
40+
<enum value="equivalent-to">The effective requirements of the source is equivalent in semantic meaning to the effective requirements of the target. The words may differ, but both mapped sets convey similar information with the same effective meaning. This relationship may be reversed, since `A equivalent-to B` also means that `B equivalent-to A`.</enum>
41+
<enum value="equal-to">The actual requirements of the source are the same as the actual requirements target. Differences in capitalization, spelling, and grammar can be ignored, if these differences do not change the meaning. This relationship may be reversed, since `A equal-to B` also means that `B equal-to A`.</enum>
42+
<enum value="subset-of">The effective requirements of the source is a semantic subset of the effective requirements of the target. This relationship may be reversed as a `superset-of`, since `A subset-of B` also means that `B superset-of A`.</enum>
43+
<enum value="superset-of">The effective requirements of the source is a semantic superset of the effective requirements of the target. This relationship may be reversed as a `subset-of`, since `A superset-of B` also means that `B subset-of A`.</enum>
44+
<enum value="intersects-with">The effective requirements of the source and target have some semantic equivalence, but not all effective requirements from each are contained within the other. This relationship may be reversed, since `A intersects-with B` also means that `B intersects-with A`. A lower granularity mapping, such as a statement level mapping using 'equivalent-to', 'subset-of', and/or 'superset-of', may provide a more functional mapping that allows for more inference than using this relationship type.</enum>
45+
</allowed-values>
46+
</constraint>
47+
<remarks>
48+
<p>When establishing relationships, mapping SHOULD be done at the control statement level where possible. This approach allows for more use of 'equivalent-to', which represents a stronger relationship than the other relationship types.</p>
49+
</remarks>
50+
</define-field>
51+
<assembly ref="mapping-item" min-occurs="1" max-occurs="unbounded">
52+
<use-name>source</use-name>
53+
<group-as name="sources" in-json="ARRAY"/>
54+
</assembly>
55+
<assembly ref="mapping-item" min-occurs="1" max-occurs="unbounded">
56+
<use-name>target</use-name>
57+
<group-as name="targets" in-json="ARRAY"/>
58+
</assembly>
59+
<field ref="remarks" in-xml="WITH_WRAPPER" min-occurs="0" max-occurs="1"/>
60+
</model>
61+
</define-assembly>
62+
<define-assembly name="mapping-item">
63+
<formal-name>Mapping Entry Item (source or target)</formal-name>
64+
<description>Identifies a specific edge within a source or target that is the subject of a mapping.</description>
65+
<define-flag name="type" as-type="token" required="yes">
66+
<formal-name>Subject Type</formal-name>
67+
<description>The semantic type of the subject.</description>
68+
<constraint>
69+
<allowed-values>
70+
<enum value="control">A control as <a href="https://pages.nist.gov/OSCAL/concepts/terminology/#control">defined</a> by OSCAL.</enum>
71+
<enum value="statement">A textual element of a control that defines part of the control's requirements.</enum>
72+
</allowed-values>
73+
</constraint>
74+
</define-flag>
75+
<define-flag name="id-ref" as-type="string" required="yes">
76+
<formal-name>Subject Type</formal-name>
77+
<description>The semantic type of the subject.</description>
78+
</define-flag>
79+
<model>
80+
<assembly ref="property" max-occurs="unbounded">
81+
<group-as name="props" in-json="ARRAY"/>
82+
</assembly>
83+
<assembly ref="link" max-occurs="unbounded">
84+
<group-as name="links" in-json="ARRAY"/>
85+
</assembly>
86+
<field ref="remarks" in-xml="WITH_WRAPPER" min-occurs="0" max-occurs="1"/>
87+
</model>
88+
</define-assembly>
89+
90+
<define-assembly name="mapping-resource-reference">
91+
<formal-name>Mapped Resource Reference</formal-name>
92+
<description>A reference to a back-matter resource that is either the source or target of a mapping.</description>
93+
<define-flag name="type" as-type="token" required="yes">
94+
<formal-name>Resource Type</formal-name>
95+
<description>The semantic type of the resource.</description>
96+
<constraint>
97+
<allowed-values>
98+
<enum value="catalog">The mapped resource is a control catalog.</enum>
99+
</allowed-values>
100+
</constraint>
101+
</define-flag>
102+
<define-flag name="href" as-type="uri-reference" required="yes">
103+
<formal-name>Catalog or Profile Reference</formal-name>
104+
<description>A resolvable URL reference to the base catalog or profile that this profile is tailoring.</description>
105+
<remarks>
106+
<p>The value of the <code>href</code> can be an internet resource, or a local reference using a fragment e.g. #fragment that points to a <code>back-matter</code>
107+
<code>resource</code> in the same document.</p>
108+
<!-- TODO: Add a link to "within the scope of the containing OSCAL document" to point to documentation of identification scopes" -->
109+
<p>If a local reference using a fragment is used, this will be indicated by a fragment "#" followed by an identifier which references an identified <code>resource</code> in the document's <code>back-matter</code> or another object that is within the scope of the containing OSCAL document.</p>
110+
<p>If an internet resource is used, the <code>href</code> value will be an absolute or relative URL pointing to the location of the referenced resource. A relative URL will be resolved relative to the location of the document containing the link.</p>
111+
</remarks>
112+
</define-flag>
113+
<model>
114+
<assembly ref="property" max-occurs="unbounded">
115+
<group-as name="props" in-json="ARRAY"/>
116+
</assembly>
117+
<assembly ref="link" max-occurs="unbounded">
118+
<group-as name="links" in-json="ARRAY"/>
119+
</assembly>
120+
<field ref="remarks" in-xml="WITH_WRAPPER" min-occurs="0" max-occurs="1"/>
121+
</model>
122+
</define-assembly>
123+
</METASCHEMA>

0 commit comments

Comments
 (0)