Method
How the Sentinelt Intelligence Engine works.
Official data in, prioritized decisions out — with the evidence visible at every step and a person reviewing the result.
1 · Official public sources
We start from data anyone can verify.
National Vulnerability Database
NIST NVD
The official U.S. record of published vulnerabilities: description, affected products and technical severity (CVSS).
Known Exploited Vulnerabilities
CISA KEV
The U.S. government catalog of vulnerabilities confirmed as exploited in the wild.
Exploit Prediction Scoring System
FIRST EPSS
A daily, data-driven estimate of how likely a vulnerability is to be exploited in the next 30 days.
This product uses the NVD API but is not endorsed or certified by the NVD.
2 · Matching & context
Only what applies to you.
We match public records against the products and versions you tell us you run, and add the context you provide — which systems face the internet, which hold sensitive data, which are business-critical.
3 · Prioritization
A priority, not a risk score.
The Sentinelt Cyber Priority Score combines confirmed exploitation, the probability of exploitation, technical severity and your context into tiers — from Immediate to Monitor. It answers “what first?”, not “how safe are we?”.
4 · Human review
A person checks every deliverable.
Automated matching has known limits — product names collide, versions are ambiguous. An analyst reviews every report before it reaches you and flags anything uncertain instead of hiding it.
Limitations we state openly
- Our priority reflects public evidence plus the context you provide — not a scan of your systems.
- A KEV listing means exploitation was observed somewhere, not that you are compromised.
- EPSS is a population-level estimate, not a prediction for your company.
- The result is only as complete as the inventory we receive.
Have a decision that depends on data?
Tell us what you need to decide. In 20 minutes we will tell you honestly whether we can help — and how.