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

Integrate SSVC #169

Closed
dylan-mulligan opened this issue Oct 11, 2023 · 0 comments · Fixed by #170
Closed

Integrate SSVC #169

dylan-mulligan opened this issue Oct 11, 2023 · 0 comments · Fixed by #170
Labels
enhancement New feature or request high priority Mark the issue as a high priority task

Comments

@dylan-mulligan
Copy link
Contributor

dylan-mulligan commented Oct 11, 2023

SSVC score is partially generated from vuln/exploit information, this should happen in the characterization step of the reconciler. We are not truly generating an SSVC score here, just the ML generated components of the score. (automatable, exploitStatus, technicalImpact) Exploit status is both an input and output, where we treat the output as "more correct" than the input. We should be sending cve-id, description, and whether or not we have found an exploit for said cve (exploit table contains matching cve), and as a result, get automatable, exploitStatus, and technicalImpact values, to be stored in the db. We will not be storing the actual score anywhere, but querying a second endpoint from ssvc with the values already collected, and will receive 3 scores that correspond to the possible values for missionAndWellbeing (LOW, MEDIUM, HIGH). The API layer will handle querying the second endpoint for these scores when a vulnerability page is loaded, and the UI will display the scores, and which missionAndWellbeing value they correspond to.

This brings up a question of performance/traffic to the ssvc api, do we cache data for a certain amount of time to reduce repetitive calls of the same cve?

@dylan-mulligan dylan-mulligan added enhancement New feature or request high priority Mark the issue as a high priority task labels Oct 11, 2023
@dylan-mulligan dylan-mulligan self-assigned this Oct 11, 2023
@dylan-mulligan dylan-mulligan linked a pull request Oct 11, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request high priority Mark the issue as a high priority task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant