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

Create Support Level to associate different types of support with an artifact. #628

Merged
merged 3 commits into from
Feb 7, 2024

Conversation

kestewart
Copy link
Contributor

The support available for a software artifact is a factor increasingly being used in risk assessment. equirement of listing the support type available. This set of enumerations has been based on the enumerations in "Managing Legacy Technology Security (HIC-MaLTS)" from the Healthcare & Public Health Sector Coordinating Councils, with additional categories being added after discussion with the AI & Data profile working groups. It can be applied to software components, AI/ML trained models and datasets; in the medical industry as well as other industries.

Signed-off-by: Kate Stewart kstewart@linuxfoundation.org

The support available for a software artifact is a factor increasingly being used in risk assessment.  equirement of listing the support type available.   This set of enumerations has been based on https://healthsectorcouncil.org/wp-content/uploads/2023/03/Health-Industry-Cybersecurity-Managing-Legacy-Technology-Security-HIC-MaLTS.pdf, with additional categories being added after discussion with the AI & Data profile working groups.   It should be able to be applied to software components, AI/ML trained models and datasets.
Add information about the level of support that can be expected for a specific artifact.
Add the supportLevel property to the artifact
@kestewart kestewart changed the title Create SupportType.md Create Support Level to associate different types of support with an artifact. Feb 5, 2024
@kestewart kestewart added this to the 3.0-rc2 milestone Feb 5, 2024
@kestewart kestewart requested review from zvr and goneall February 5, 2024 11:23
Copy link
Member

@goneall goneall left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@bennetkl bennetkl left a comment

Choose a reason for hiding this comment

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

The SPX-AI WG discussion talked about also adding No Assertion, which I see you have done, because currently at least with AI/Dataset, none of these artifacts have any kind of support. We probably should add an example of limited support ie. is that limited to specific times of day? type of issues? or something else.

Approved to merge into main

Copy link
Member

@maxhbr maxhbr left a comment

Choose a reason for hiding this comment

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

LGTM

@kestewart
Copy link
Contributor Author

Thanks @bennetkl, @goneall, @maxhbr for the quick turn on the reviews! Merging this now.

@kestewart kestewart merged commit f04b4ed into main Feb 7, 2024
1 check passed
@kestewart kestewart deleted the kestewart-support-level branch February 7, 2024 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants