oscal-content icon indicating copy to clipboard operation
oscal-content copied to clipboard

NIST SP 800-53 content and other OSCAL content examples

Results 51 oscal-content issues
Sort by recently updated
recently updated
newest added

For the actions element, it requires a system URI. Can additional details and/or examples be provided to understand how this should be leveraged. As an example, the FedRAMP SSP (legacy...

question

# User Story: As an organization defining use case for existing OSCAL catalogs, I want to leverage the prop[@name] = "response-point" as a means of visually tailoring the control catalog...

enhancement
User Story

Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.2 to 4.1.6. Release notes Sourced from actions/checkout's releases. v4.1.6 What's Changed Check platform to set archive extension appropriately by @​cory-miller in actions/checkout#1732 Update for 4.1.6 release...

dependencies
github_actions

# Describe the bug ### Describe the bug While browsing the example files, it was noted that there are many typos and spelling errors. For example: - `examples\ap\*\ifa_assessment-plan-example.[json|xml|yaml]`: ```diff -...

bug

# Describe the bug While label properties are present for controls, the label property is missing from groups. # Who is the bug affecting? Tool developers and content consumers. #...

enhancement

# Committer Notes Added label properties to groups in NIST SP 800-53 r4, so that tools that honor the label property will have data to use. ### All Submissions: -...

# Committer Notes Added label properties to groups in NIST SP 800-53 r5, so that tools that honor the label property will have data to use. ### All Submissions: -...

Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.2 to 4.1.7. Release notes Sourced from actions/checkout's releases. v4.1.7 What's Changed Bump the minor-npm-dependencies group across 1 directory with 4 updates by @​dependabot in actions/checkout#1739 Bump...

dependencies
github_actions

Validation error seems to conflict with cardinality rules for assessment-method. Located in Local Definitions. ## What was validated ``` "local-definitions":{ "objectives-and-methods":[ { "name":"assessment-objective", "ns":"http://csrc.nist.gov/ns/oscal", "props": [ { "name": "method-id", "ns":"http://csrc.nist.gov/ns/oscal",...

question

# User Story: As an OSCAL {stakeholder}, I want to pass a token styled data, and it still validate as long as the token format is met. ## Goals: Adjust...

enhancement
User Story