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

Add confidence since people ask about this too #1904

Merged
merged 3 commits into from
Jan 17, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions docs/kb/rules/understand-severities.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
description: Understand how rule severity is determined.
description: Understand how rule severity and confidence is determined.
tags:
- Rules
- Semgrep Registry
Expand All @@ -23,4 +23,10 @@ In addition to severity, Supply Chain displays an [Exploit prediction scoring sy

* <b>High</b>: 50 - 100%
* <b>Medium</b>: 10 - &#60;50%
* <b>Low</b>: &#60;10%
* <b>Low</b>: &#60;10%

# How are confidence levels assigned to rules?

Confidence level is also set by the rule author, but it is intended to describe the rule, not the vulnerability the rule catches.

The confidence level reflects how confident the rule writer is that the rule patterns capture the vulnerability without generating too many false positive findings. The rule author manually sets the appropriate confidence level. Rules that have more targeted and detailed patterns, such as advanced taint mode rules, typically are given `HIGH` confidence.
Loading