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

Consider decision points based on FIPS-199 #740

Open
ahouseholder opened this issue Mar 11, 2025 · 1 comment
Open

Consider decision points based on FIPS-199 #740

ahouseholder opened this issue Mar 11, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@ahouseholder
Copy link
Contributor

Is your feature request related to a problem? Please describe.

SSVC has no native decision points to support categorization of systems by security requirement levels.

Describe the solution you'd like

Consider adding decision points to reflect the system security categories listed in FIPS 199

https://nvlpubs.nist.gov/nistpubs/fips/nist.fips.199.pdf

This publication establishes security categories for both information and information systems. The
security categories are based on the potential impact on an organization should certain events occur
which jeopardize the information and information systems needed by the organization to accomplish
its assigned mission, protect its assets, fulfill its legal responsibilities, maintain its day-to-day
functions, and protect individuals. Security categories are to be used in conjunction with vulnerability
and threat information in assessing the risk to an organization.

Image

Note

Although similarly named, these are not the same as the C, I, A impacts in CVSS vectors. However, they are semantically related to CVSS v4's CR, IR, AR vector elements https://www.first.org/cvss/v4.0/specification-document#Confidentiality-Integrity-and-Availability-Requirements-CR-IR-AR

@ahouseholder ahouseholder added the enhancement New feature or request label Mar 11, 2025
@j---
Copy link
Collaborator

j--- commented Mar 11, 2025

If anything is done here, I agree the mapping to CVSS CR, IR, and AR should be documented.
This seems like possibly something that would function in place of mission impact?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants