Skip to content

Vulnerabilities and rules

Malware is never a preference: a detection is a critical finding for everyone. Vulnerabilities are your policy: the same CVE can block for one organization and only be highlighted for another.

  • Permission: Manage security (security:write) to change feeds, rules and exceptions. security:read to view.

Go to Security › Feeds. Each feed is on or off for your organization.

Feed Gives Default
NVD CVEs with CVSS scores and affected version ranges On
CISA KEV Marks CVEs exploited in the wild On
FIRST EPSS The probability a CVE is exploited in the next 30 days On

Turning a feed off stops its data being used for your organization.

  1. Go to Security › Rules and choose New rule.
  2. Tick the conditions. All ticked conditions must hold:
    • Severity at or above
    • CVSS score at least
    • Known exploited (CISA KEV)
    • Exploit probability (EPSS) at least
    • A fixed version is available
    • Only these packages
  3. Check Impact today to see what the rule would match.
  4. Choose the action:
    • Save and block: matching versions can’t be approved, and approved ones stop being served.
    • Save as highlight: matching versions are shown to admins. Approval is still allowed after a confirmation.

When you accept the risk of a CVE for a package, add an exception from Security › Vulnerabilities with Add exception. Enter why the risk is accepted. Exceptions last at most a year, and the reason goes in the audit log.

Problem Fix
A version you need is blocked by a rule Add an exception for that CVE and package, or change the rule.
No CVEs match anything Check that NVD is on in Security › Feeds.