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

improve output of risk severity field. #191

Merged
merged 4 commits into from
Aug 30, 2024
Merged

Conversation

pyth0n1c
Copy link
Contributor

@pyth0n1c pyth0n1c commented Jul 15, 2024

it is now calculated using the risk score.

Note that we may apply this to confidence field as well after discussion
Given ongoing discussions over the existence of the confidence field, we will not make changes to that value in this PR.
Please see this PR for further discussion around the future of risk stuff in our YMLs: #263

it is now calculated using the risk score
@pyth0n1c pyth0n1c added the 4.2 label Jul 16, 2024
@pyth0n1c pyth0n1c added 4.3 and removed 4.2 labels Jul 25, 2024
@patel-bhavin patel-bhavin self-requested a review July 31, 2024 23:33
@patel-bhavin
Copy link
Contributor

Does this code require the risk_score to be present in the yaml since we are trying to remove risk_score and convert it into a computed field as per this security content PR : splunk/security_content#3062

@pyth0n1c
Copy link
Contributor Author

Does this code require the risk_score to be present in the yaml since we are trying to remove risk_score and convert it into a computed field as per this security content PR : splunk/security_content#3062

No, it does not require it to be present. It USES the risk_score value, but that is a computed_field that is determined at runtime from confidence and impact.

@pyth0n1c pyth0n1c changed the base branch from release_v4.2.0 to main August 21, 2024 20:43
@pyth0n1c pyth0n1c changed the base branch from main to release_v4.2.0 August 29, 2024 22:30
@pyth0n1c
Copy link
Contributor Author

Merging this PR to the release branch.
As that branch has many related changes, they will all be evaluated and merged to main at the same time.

@pyth0n1c pyth0n1c merged commit 48e31d3 into release_v4.2.0 Aug 30, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants