TRIS. True Risk Intelligence Score

Stop drowning in
CVSS noise

TRIS 3 scores every vulnerability from how likely it is to be exploited, backtested against later CISA KEV additions, plus what your environment says about it. Know exactly what to patch first.

0-100
TRIS 3 Score
4
Priority Bands
328K+
CVEs Scored
85%
Noise Reduction

Two findings, both 9.8, get different answers

Thirty seconds on why TRIS scores the vulnerability you actually run, not the one in the database.

CVEasy AI · TRIS scoring · 0:30

CVSS is lying to your team

When everything is "critical," nothing is. Your analysts are drowning in noise while real threats hide in the backlog.

59,000+
CVEs Published in 2026
Critical
17,700
High
14,160
Medium
16,520
Low
10,620

Based on CVSS alone, nearly 30% are "Critical"

The CVSS-only trap

CVSS was designed to measure technical severity, not business risk. It tells you HOW BAD a bug could be, not whether anyone is actually exploiting it or if it even affects your environment.

The result? Security teams burn weeks patching theoretical "Critical" vulnerabilities while actively exploited, moderate-scoring bugs slip through.

  • 30% of CVEs rated "Critical" have zero known exploits
  • Average team wastes 40% of patching cycles on low-real-risk items
  • SLA violations spike when everything has the same urgency label
  • Alert fatigue causes analysts to miss the vulns that actually matter

How TRIS 3 scores a finding

One function scores a finding on an asset and a CVE in the catalogue, in four stages. There is no weighted average, so each input moves the score only in its own direction: adding risk never lowers it and adding a mitigation never raises it. TRIS 3 replaced the twelve-layer TRIS v2 in release 1.7.4. The v2 white paper remains as the record of the earlier model.

Exploitation likelihood

The probability a CVE is added to CISA KEV, from a logistic model over EPSS, CVSS, age, network reachability without authentication, and vendor reports of exploitation. Fitted on four point-in-time EPSS snapshots with later KEV additions as the label. In a leave-one-date-out backtest it reached ROC-AUC 0.89 to 0.92, against 0.83 to 0.87 for TRIS v2 and 0.67 to 0.73 for EPSS alone at the time. An unknown EPSS or CVSS takes the population average, so missing data never reads as safe.

STAGE 1
Points

Mitigation

Finding-specific verdicts (blocked by a control, not reachable, does not apply, patched) and verified controls such as EDR, WAF, MFA and network segmentation multiply the likelihood down. They never push it up.

STAGE 2
Lowers

Asset context

Fixed points for asset criticality, crown-jewel proximity, internet exposure, environment and spread across your estate. Context you have not recorded adds nothing: unknown is neutral, never a discount.

STAGE 3
Points

Confirmed exploitation

CISA KEV, a threat actor documented using the CVE, BASzy proof, or exploitation observed in your environment lifts the finding into ACT and keeps it ordered there. Only a finding-specific verdict can waive it.

STAGE 4
Floor

Same CVE, different conclusions

See how TRIS transforms a panic-inducing CVSS score into an actionable, contextualized priority.

CVSS Score Only
9.8
CRITICAL
CVE-2024-38063

Windows TCP/IP Remote Code Execution. CVSS says: drop everything and patch immediately across your entire fleet.

  • ✗ No exploit context considered
  • ✗ No asset exposure data
  • ✗ No business impact weighting
  • ✗ No threat intelligence
  • ✗ Same score for every environment
vs
TRIS Score
18
MONITOR
CVE-2024-38063

TRIS 3 weighed the likelihood and your context and determined: this is not an emergency for YOUR environment right now.

  • ✓ Not in CISA KEV catalog
  • ✓ EPSS: 0.04% exploitation probability
  • ✓ Likelihood model: 20.7 points
  • ✓ Your affected hosts are internal-only: minus 3
  • ✓ Medium criticality: no change

This is one example. Every organization gets different TRIS scores based on their unique asset exposure, business context, and threat landscape.

Four priority bands, zero ambiguity.

TRIS maps every vulnerability into actionable SLA bands so your team always knows the timeline.

80 - 100
ACT Fix within 72 hours
60 - 79
ATTEND Fix within 14 days
35 - 59
TRACK Fix within 90 days
0 - 34
MONITOR No SLA, review next cycle

SLA windows are defaults. Fully configurable per organization, asset group, or compliance framework.

TRIS vs CVSS vs EPSS

Each scoring system was designed with a different purpose. TRIS uses both as inputs and adds your environment.

Capability TRIS™ CVSS v3.1/4.0 EPSS
Technical severity ✓ ✓ ✗
Exploitation probability ✓ ✗ ✓
Active exploitation (KEV) ✓ ✗ ✗
Business context ✓ ✗ ✗
Your asset exposure ✓ ✗ ✗
Threat campaign data ✓ ✗ Partial
Vulnerability age ✓ Optional metric ✗
Actionable SLA bands 4 bands with timelines 4 static labels Raw percentage
Environment-specific Unique per org Same for everyone Same for everyone
Auto-remediation guidance ✓ AI-generated ✗ ✗

CVSS and EPSS are valuable inputs. TRIS 3 uses both inside its likelihood model. The difference is that TRIS 3 also adds your environment: asset criticality, exposure, verified controls, and exploitation confirmed by CISA KEV, threat actors, or BASzy.

Prioritize, then fix

Once TRIS tells you what to patch first, CVEasy AI generates the exact fix commands for your operating systems.

AI-generated remediation per OS

TRIS scoring does not stop at prioritization. For every vulnerability that needs action, CVEasy AI's local LLM generates step-by-step remediation tailored to your actual environment.

  • OS-specific patch commands (Ubuntu, RHEL, CentOS, Windows, macOS)
  • Pre-patch verification steps to avoid breaking changes
  • Rollback procedures if something goes wrong
  • Compensating controls when patching is not immediately possible
  • Bulk remediation scripts for fleet-wide deployment
  • Generated 100% locally, never touches external APIs
# TRIS Score: 91. CRITICAL PRIORITY
# CVE-2026-21974. OpenSSH Pre-Auth RCE
# Affected: 14 internet-facing hosts

$ cveasy remediate CVE-2026-21974

# --- Ubuntu 22.04 / 24.04 ---
sudo apt update
sudo apt install openssh-server=1:9.6p1-3ubuntu1
sudo systemctl restart sshd

# --- RHEL 9 / CentOS Stream ---
sudo dnf update openssh-server
sudo systemctl restart sshd

# --- Verify fix ---
ssh -V
OpenSSH_9.6p1, OpenSSL 3.2.1

# --- Compensating control ---
# If patching is delayed:
sudo ufw deny from any to any port 22
sudo ufw allow from 10.0.0.0/8 to any port 22
Restrict SSH to internal network only

Go from guessing
to knowing

See how TRIS 3 scoring transforms your vulnerability management program: one score, one clear answer.

Request a Demo → Contact Sales