Skip to Content
AdvancedBeeScore

BeeScore

The BeeScore is a score that is calculated for each vulnerability and action plan. It is used to prioritize the vulnerabilities.

When you are reading a vulnerability from the monitor page, the BeeScore is displayed in the top right corner of the vulnerability details page. It is also displayed in the action plan page.

In both cases, the BeeScore is personalized with your context as defined in your watchlists.

Otherwise, when you are reading a vulnerability from the catalog page, the BeeScore displayed in the top right corner of the vulnerability details page is a generic BeeScore assessing the priorization of the vulnerability in a typical deployment context for the product.

BeeScore calculation

The BeeScore is calculated based on the following factors:

  • The severity of the vulnerability: CVSS v4.0 BTE score.
  • The likelihood of the vulnerability being exploited: based on the EPSS  score.
  • Qualitative assessment of the vulnerability context: exploit automatibility, provider urgency, national CERT alerts, etc.

On top of these factors, environmental factors are taken into account to personalize the BeeScore.

Sensitivity level of the watchlist

In the case the BeeScore is personalized, it takes into account the sensitivity level of the watchlist. The sensitivity level sets a threshold on the exploitation likelihood. The higher the sensitivity level, the lower is the threshold on exploitation likelihood.

Product exposure

The product exposure allows to take into account the network context in which the product is deployed.

VulnPilot categorizes products into one of the following exposure levels:

  • RestrictedAdminNetwork: the product is deployed in a restricted admin network.
  • LocalNetwork: the product is deployed in a local network.
  • Internet: the product is deployed on the internet.
  • LocalMachine: the product is deployed on a local machine.

This categorization is used to adjust the CVSS scoring and by extension the BeeScore.

Note

The product exposure will be configurable in the future inside the watchlist definition.

Qualitative assessment of the vulnerability context

The BeeScore calculation takes into account a qualitative assessment of the vulnerability context. It is a combination of the following factors: exploit automatibility, provider urgency, national CERT alerts, human safety, etc.

Among these factors, the national CERT alerts are the most important. They are used to assess high risk vulnerabilities by taking into account several risks at once:

  • There is a high risk of exploitation due to wide spread use of exploits.
  • There is a compliance risk for regulated organizations: national CERT alerts often enforce strict remediation deadlines.
  • Incident response teams are actively responding to vulnerability exploitation events.

BeeScore interpretation

The BeeScore is a score between 0 and 10. It is interpreted using SSVC-aligned priority bands as follows:

  • 0–2: Defer — these vulnerabilities are not critical and can wait. Recommended action delay: 90 days or the next system upgrade.
  • 2–4.5: Scheduled — these vulnerabilities are important but can follow a normal remediation cycle. Recommended action delay: 60 days.
  • 4.5–6.5: Out-of-Cycle — these vulnerabilities could cause significant damage and should be addressed outside the normal cycle. Recommended action delay: 14 days.
  • 6.5–10: Immediate — these vulnerabilities are known to cause significant damage and should be addressed immediately. Recommended action delay: 3 days.

This scale is not linear. It is designed to reflect the fact that the most important vulnerabilities are not the most severe ones, but the ones that are the most likely to cause significant damage.

These priority bands are also used when you configure notification filters.

Last updated on

© 2026 Sentibee SAS.