Since our last major scoring update in August 2024, we've added geopolitical risk detections, such as sanctions list appearances and operations in countries with low political freedom. UpGuard now runs 410 security checks and tracks 13,435 vulnerabilities. The checks now reach beyond the attack surface to risks such as sanctions exposure, credentials stolen by infostealer malware, and shadow AI use.
Now we're updating how the risks we find turn into security ratings. They get new risk weights, based on real breach data, and a new way to count each domain's risks. You can preview the new ratings from December 2nd, and they take effect on March 10th.
There's no change to any organization's identified security risks. The scan results, evidence, and questionnaire answers stay the same. What changes is how much each risk counts, so some ratings will go up, and some will go down. The goal is a rating you can use with confidence when reporting to your board or customers, or when setting thresholds in contracts.
What's changing, and why
The security rating
The security rating comes from the risks our automated scans find across an organization's internet-facing domains and IPs. In Breach Risk, it's your security rating; in Vendor Risk, it's each vendor's rating; on the trust pages you publish with the Trust Center, it's your public rating. Two things are changing:
- Risk weights have been recalibrated from real breach data. We compared about 2,500 breached organizations with similar-sized organizations that weren't breached. Breached organizations were more likely to have DNS misconfigurations and website security gaps; those risks will now count for more. The ten risk categories and their weights stay the same.
- A weak domain now lowers the rating, regardless of how many domains an organization has. Our old Gaussian weighted average method could hide one poorly secured domain among many well-secured ones. The new method compares an organization's weakest domains with what is normal for organizations with a similar number of domains.
From December 2nd, you'll see the new security rating next to your current one. It works like a provisional risk: you can see it, but it doesn't count yet. Your trust pages, badges, reports, and the API keep your current rating until March 10th, when the new one takes effect everywhere.
What to expect:
- Ratings will move in both directions. Ratings are most likely to drop where DNS or website security risks are concentrated. They're most likely to rise where most risks are in encryption (SSL/TLS hygiene) or data leakage.
- Organizations with only a few domains are likely to see little change. Organizations with many domains are likely to see the biggest changes.
- Your rating history, including in reports, will mark March 10th as the date the new scoring took effect. From then, compare new ratings with previous ones.
Per-check risk impact
Alongside the new rating preview, each security check will show its risk impact: how much it lowers your security rating. You can use it to see which risks to fix first.
Key dates
| When | What happens | | --- | --- | | December 7th to December 18th 2026 | If your account is likely to see a large change, your Customer Success Manager will contact you. | | December 2nd 2026 | The preview of new security ratings and per-check risk impact begins in the product only. | | March 10th 2027 | New security ratings take effect everywhere, including trust pages, badges, reports, and the API. |
What to do
If you use Vendor Risk
From December 2nd
- Preview your vendors' new security ratings.
- Check per-check risk impact to see which risks are driving each vendor's rating, and focus remediation requests there.
Before March 10th
- Review notifications and integrations that trigger on rating drops or thresholds, such as webhooks and ServiceNow. They can fire when the new rating takes effect. See How to create custom notifications, How to integrate UpGuard with other services using webhooks, and How to set up ServiceNow Vendor Risk integration with UpGuard.
- If you use rating thresholds in SLAs or acceptance criteria, look for vendors close to a threshold, and decide whether to reassess them.
If you use Breach Risk
Your security rating, and your subsidiaries' ratings, change on March 10th.
From December 2nd
- Compare your projected security rating with your current one. If it's lower, DNS and website security risks are the likely cause, so start there. Anything you fix before March 10th counts toward your new rating.
- Check the risk impact of each security check to see which risks lower your rating the most, and fix those first.
Before March 10th
- Let your board, and anyone else who holds your UpGuard rating, such as customers, insurers, or auditors, know that it changes on March 10th.
- Review notifications and integrations based on your security rating. They can fire when the new rating takes effect.
If you use Trust Exchange
The security rating on your trust pages and badge switches to your new security rating on March 10th. Until then, they show your current rating. If customers or partners view your Trust Center, let them know before then. If you also use Breach Risk, you can preview your new security rating there from December 2nd.
Frequently asked questions
My security rating dropped, but nothing changed. Why?
There's no change to your identified security risks, but each risk now carries a different weight, and the risks most closely linked to real breaches count the most. If you have many domains, one weak domain can also lower your rating even when the others are clean. So a drop points to risks worth reviewing. If your account is likely to see a large change, your Customer Success Manager will contact you before December 18 to walk you through it.
Where can I learn more?
- For general information on how UpGuard introduces changes to the platform, see How UpGuard introduces new risks and scoring algorithm changes.
- For a breakdown of how security ratings currently work, see How are UpGuard's security ratings calculated?
Help articles at help.upguard.com will be updated as these features roll out.
Getting help
- Your Customer Success Manager: If your account is likely to see a large change, they'll contact you between December 7th and 18th. You can also reach out to them at any time.
- Support: Email support@upguard.com, or contact us from within the platform.