The requirement for having every resource be referenced should be removed

[telosBA]

• This is a ...

  • [x] concern - I think something needs to be different.
  • [ ] question - I didn't understand something.
  • [ ] kudos - I found something helpful and want to encourage it in future FedRAMP publications.
  • [ ] request - I would like to see something additional provided.

• This relates to ...

  • [ ] the FedRAMP OSCAL Registry (Excel File)
  • [ ] the Guide to OSCAL-based FedRAMP Content (PDF)
  • [ ] the Guide to OSCAL-based FedRAMP System Security Plans (SSP) (PDF)
  • [ ] the Guide to OSCAL-based FedRAMP Security Assessment Plans (SAP) (PDF)
  • [ ] the Guide to OSCAL-based FedRAMP Security Assessment Reports (SAR) (PDF)
  • [ ] the Guide to OSCAL-based FedRAMP Plan of Action and Milestones (POA&M) (PDF)
  • [ ] the FedRAMP SSP OSCAL Template (JSON or XML Format)
  • [ ] the FedRAMP SAP OSCAL Template (JSON or XML Format)
  • [ ] the FedRAMP SAR OSCAL Template (JSON or XML Format)
  • [ ] the FedRAMP POA&M OSCAL Template (JSON or XML Format)
  • [ ] General/Overall
  • [x] Other

NOTE: For feedback related to the OSCAL syntax itself, please create or add to an issue in the NIST OSCAL Repository.

• Where, exactly?

  • For the registry, please indicate the tab and cell, or other clear identifier
  • For the guide, please indicate the section number and printed page number (lower right corner)
  • For the OSCAL XML or JSON files, please indicate XML or JSON; and indicate the line number, field id, or other clear location identifier UI Validator

• What is your feedback? There exists a schematron check within the “SSP Template 15” section of the UI validator that checks that each resource is referenced somewhere within the SSP. This cannot be accomplished, for many reasons. One of which is that the backmatter is the only backmatter, shared across every other OSCAL file. If a resource that only exists in POAM is included in backmatter, this will always throw an error. For this reason, this test should be removed.

• Is this report specifically related to the Word or Excel files from fedramp.gov? If so, please do not open an issue here. Follow the guidance in this repository's README and contact info@fedramp..gov.

• What version of OSCAL are you using? (Check our info on supported OSCAL versions)

• What action would you like to see from the FedRAMP PMO? Remove requirement for resources being referenced.

• Other information (e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, eg. slack, gitter, etc)

[GaryGapinski]

I concur: back matter resources may be gratuitous — intra-document references need not exist.