-
Notifications
You must be signed in to change notification settings - Fork 101
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
Change the way we manage severity #728
Comments
Discussion item:
|
To confirm @gmontard, if the final severity is warning (1), do we want to keep the current behaviour and not fail the CI? e.g.
|
I'm happy with this. Keeps the rules simpler 👍 |
@elsapet Absolutely about the warning, we keep current behavior on how we manage that, no changes. |
PR #730 updated |
* Updating rules severity Associated with: #728 * Cleaning rules by removing severity low (new default), updating doc * feat: update rules severity (#739) * feat: update rules severity * chore: update snapshots for rules * fix: linting * fix: fix e2e snapshots * fix: fix unit test * chore: update snapshots * chore: update snapshots * fix: update severity according to CWE listing --------- Co-authored-by: elsapet <[email protected]>
We'd like to simplify the severity level of the rules, and defer any calculation leading to increase the severity level globally (depending on the sensitive data categories). This will allow simplifying the rules, reinforce common standard and later-on more easily allow user's custom severity configuration.
Impact on the Rule structure
The severity node will end-up being a single value, representing the rule default severity (when triggered).
Changing:
to:
Dynamic severity calculation
Rules can get triggered depending on the
triggered
options, essentially associated with the direct (trigger: local
) or global (trigger: global
) presence of sensitive data, and sometimes even if none are present (trigger: presence
ortrigger: absence
).When a rule trigger is associated with sensitive data, we want to increase its default severity level in relation to the sensitive data categories (PHI, PDS, PD, PII).
Proposed algorithm
We allocate points to each rule severity (using Fibonacci numbers), level:
We also assign points to each sensitive data categories:
And a weight to the trigger type:
Ultimately, we perform this calculation and assign the closest lower severity score:
Example:
The text was updated successfully, but these errors were encountered: