Skip to main content

Align Target Risk Meter Color With Severity Context

Update the Target Risk Meter color logic so that targets with only low-severity findings (e.g., Severity 3) are visually represented as low risk, with a color that reflects minor exposure rather than a misleading “perfect/fully healthy” state.

Current Behavior

  • A target with a Severity 3 vulnerability (example: TLS 1.1 enabled) may have an overall risk score of 100.

  • Based on current thresholds:

    • Low risk: 0–299

    • Medium risk: 300–599

    • High risk: 600+

  • The target is marked green on the risk meter, visually implying no meaningful risk, even though an actionable vulnerability exists.

Problem

  • The current green risk meter conflates “low risk” with “no risk.”

  • Customers interpret a fully green meter as “nothing to address,” which reduces visibility of:

    • Minor but actionable hygiene issues (TLS 1.1, weak ciphers, minor headers, legacy protocols).

  • This causes confusion when:

    • An issue list clearly shows open vulnerabilities

    • But the target visually appears “perfect”

Requested Enhancement

Red - High Risk Target
Orange - Medium Risk Target
Yellow - Low Risk Target
Green or another color - Fully Clean Target

Status: Completed1 comment

Log in to comment and vote

Comments1

  • Nick Merritt

    Team•

    Dec 5, 2025

    Just enabled upvotes on this request because color-coding risk is inherently subjective, and I’m not entirely sure we’ve landed on the best default. A fully green meter when low-severity but actionable findings still exist feels misleading to many users, while others prefer the current strict approach. Rather than decide on my own, letting the community vote and share their experiences will quickly clarify whether most people want a distinct “Low Risk” visual state (or customizable colors) versus keeping green reserved for truly clean targets.