Ray Gauss II
Ray Gauss II
Contribution of tika-exiftool for review
# Describe the bug Similar to #103, the JSON templates contain imports that reference XML rather than JSON files. For example, the SSP template [import-profile points to the XML moderate...
- Added support for optionally using Maven, enabling more recent snapshots and custom deployments - Added support for application of AMPs - Updated Alfresco version - Updated Java version to...
As part of a previous issue, it was found that the JSON schemas NIST produces contain `$ref` elements by `$id` rather than path which [seems to only be supported in...
### Description As a developer of the OSCAL Viewer, I would like styles to be declared at a global level for easy reusability among components. ### Acceptance Criteria * A...
Currently the `getControlOrSubControl` in `OSCALControlResolver` only supports a single level depth of controls when searching for controls but that depth is unbounded in the OSCAL specification, which we should support....
As a user involved in the governance, risk, and compliance of systems and components exploring controls, I want to be able to easily view the basic elements available on a...
As a user involved in the governance, risk, and compliance of systems and components, I want the navigation between control implementation by components of System Security Plans to be obvious...
As a user consuming OSCAL React Libraries, I would like to edit properties listed underneath [system-characteristics](https://pages.nist.gov/OSCAL/reference/latest/system-security-plan/json-reference/#/system-security-plan/system-characteristics) to fit the policy I'm creating. ## Acceptance Criteria - [ ] An editable...
We currently have a few instances of modifying objects like `oscalData` to add things like `resolvedControls` and `oscalSource` but should revisit this approach. ### Subtasks - [ ] https://github.com/EasyDynamics/oscal-react-library/issues/499