-
Notifications
You must be signed in to change notification settings - Fork 17
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
✨ Add a source to scores #1431
✨ Add a source to scores #1431
Conversation
Test Results 1 files 24 suites 18s ⏱️ Results for commit 36c80e4. ♻️ This comment has been updated with latest results. |
policy/cnspec_policy.proto
Outdated
@@ -640,6 +640,9 @@ message Score { | |||
int64 failure_time = 11; | |||
// risk factors that were applied to this score | |||
ScoredRiskFactors risk_factors = 12; | |||
// Source of the score | |||
// Currently, this only applies to vulnerability scores | |||
string source = 13; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have questions:
- One score can have multiple sources. Eg. MVD can find a CVE and MS defender can find a CVE. Then what lands in the source
- I am not sure a simple string is enough. On GraphQL layer we need to return: source id, source title, source icon. How do we achieve that without storing all the data all the time. eg. we track a list of data sources per space and then refer ids?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recommend we do the following:
// Source is used to identify the source.
message Source {
// Required. Name of the source
string name = 1;
// Optional. URL of the source
string url = 2;
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion. I changed it accordingly.
Signed-off-by: Christian Zunker <[email protected]>
f31d8ec
to
77f3d47
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @czunker
No description provided.