Skip to content

Commit ed91f59

Browse files
Improve wording, add missing words from @kyhu65867 review for GSA#939
Co-authored-by: Kylie Hunter <kylie.hunter@gsa.gov>
1 parent 1e461ff commit ed91f59

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/validations/constraints/fedramp-external-constraints.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -172,8 +172,8 @@
172172
<message>A FedRAMP SSP MUST identify how the system implements each control requirement implemented at the per-statement level, not in other locations allowed for non-FedRAMP use cases.</message>
173173
<remarks>
174174
<p>NIST maintains OSCAL models that allow implemented requirements for controls to have references to the implementing components in multiple locations to support multiple use cases.</p>
175-
<p>Despite the flexibility of NIST's upstream OSCAL models, FedRAMP only accepts OSCAL-based SSP with the reference in one of those locations, see <code>missing-response-components</code> for more details about this requirement.</p>
176-
<p>A constraint violation with this warning indicates a given SSP uses one of the valid locations for all NIST use cases, not the only one FedRA</p>
175+
<p>Despite the flexibility of NIST's upstream OSCAL models, FedRAMP only accepts OSCAL-based SSPs with the reference in one of those locations, see <code>missing-response-components</code> for more details about this requirement.</p>
176+
<p>A constraint violation with this warning indicates a given SSP uses one of the valid locations for all NIST use cases, but not the only FedRAMP required location.</p>
177177
</remarks>
178178
</expect>
179179
<expect id="missing-response-components" target="implemented-requirement/statement" test="count(by-component) ge 1" level="ERROR">

0 commit comments

Comments
 (0)