oscal-content
oscal-content copied to clipboard
NIST SP 800-53 content and other OSCAL content examples
# User Story: Picking up on #86, we have code in a working branch here: https://github.com/wendellpiez/oscal-content/tree/issue86-opd-analysis But there are (policy-level) data governance questions to be addressed first. The idea/concept of...
# User Story: In coordination with the NIST SP 800-53 Rev 5 update 2 release, we can stabilize all the corrections and enhancements it includes along with those accruing in...
# User Story: As an OSCAL tools developer, in order to better understand the examples and adjacent documentation, I want the `./src/examples/ssp` I want scripts, validation utilities, document, and design...
> Also, in terms of acceptance criteria, we still ask for examples. It seems in #1263 NIST has begun removing `example`s from the Metaschema and I am not sure of:...
# User Story: As an OSCAL content consumer, I need an accurate representation in the OSCAL SP800-53/rev4 catalog of the controls described in the document SP 800-53rev4 Appendix J. ##...
As a developer of tooling built around OSCAL catalogs/profiles, would it be possible to either have separate branches, tags, or actual releases for the different OSCAL milestones? At least the...
# User Story: Responding to usnistgov/OSCAL#534 we implemented a simple profile link checker that reports when profiles call controls that can't be found in an imported catalog. It doesn't work...
# User Story: As an OSCAL user, I would like access to the best available OSCAL rendering tools, including XSLTs that produce HTML and (Accessible) PDF, with production values comparable...
In regards to the NIST 800-53 Rev 5 catalog, it appears that there could be some inconsistencies with the spacing after the parameters that can be inserted when "and" is...
Problem: Representation of objectives changed between 800-53 Rev 4 and 800-53 Rev 5 breaking parsers
### Describe the bug The representation of security control assessment objectives in the OSCAL 800-53 catalogs published by NIST on GitHub changed between Rev 4 and Rev 5 and broke...