Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjusted information-type/*-impact constraints #1888

Conversation

nikitawootten-nist
Copy link
Contributor

@nikitawootten-nist nikitawootten-nist commented Aug 15, 2023

Committer Notes

Fixes #1795 by allowing other impact values.

What about #1872

#1872 trialed a broader change, allowing for other impact types falling outside of the CIA triad as well as an @ns attribute for optional constraints.

It is clear this issue requires more care. This PR will be followed up with an OSCAL-DEFINE entry usnistgov/OSCAL-DEFINE#34.

All Submissions:

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

Changes to Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you included examples of how to use your new feature(s)?
  • Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.

Copy link
Contributor

@aj-stein-nist aj-stein-nist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Short, sweet, and to the point.

@aj-stein-nist aj-stein-nist linked an issue Aug 15, 2023 that may be closed by this pull request
4 tasks
@aj-stein-nist aj-stein-nist merged commit bb454ed into usnistgov:develop Aug 16, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use other security categorization frameworks besides FIPS 199 in an SSP
2 participants