Skip to content
  • There are no suggestions because the search field is empty.

Vendor Risk: Preparing for the March 2027 Security Rating Update

Overview

On March 10th 2027, the automated scan rating behind every vendor's security rating will switch to UpGuard's new scoring method, on the same day for all vendors. Vendors' identified risks won't change, but their ratings can move up or down.

Anything in your third-party risk management (TPRM) program that relies on a vendor's rating — thresholds, notifications, integrations, reassessment triggers, contract minimums, or reports — can react to a change in UpGuard's method rather than a change at the vendor. Use the preview from December 2nd 2026 to find what's affected, and decide how to handle it before March 10th 2027.

For why UpGuard is making the change, see the Scoring Update announcement.

🎵 Security Profile assessment ratings changed separately on November 4th 2026 — see Security Profile Rating Update: November 2026. Security Profile assessments that include automated scanning checks will also change on March 10th 2027.

Preview your vendors' new ratings

From December 2nd 2026, you'll see each vendor's new rating next to its current one. The current rating still counts until March 10th 2027. Start with your most critical vendors and with vendors close to a threshold you use.

❗ The preview won't be available through the API, so GRC tools, dashboards, or other systems that pull vendor ratings won't show a change until March 10th 2027.

Rating thresholds, tiering, and contracts

If your policies, tiering, or contracts set a minimum vendor rating — for example, a rating of at least 800 for tier 1 vendors, or a grade of C or better for all vendors — some vendors may cross that line on March 10th 2027, in either direction, without anything changing at the vendor. Before then:

  • List where you use a minimum rating — policies, tiering rules, and contracts — so you can check those vendors against the preview from December 2nd 2026, starting with your most critical tiers.
  • Decide how to treat vendors that cross. For example, keep the threshold, add a grace period, or review it. Record the decision and its effective date in your policy.
  • Check contracts that refer to an UpGuard rating. Involve your legal or procurement team before March 10th 2027. For new contracts, your legal team may want wording that allows for scoring updates.
  • Check rating-based tiering. If you use the rating to tier vendors, some vendors could change tier. Consider a manual review before any tier change takes effect.

Notifications, webhooks, and integrations

From March 10th 2027, notifications and integrations that trigger on a vendor's rating will use the new rating, so they can fire for vendors whose identified risks haven't changed. UpGuard will publish recommended notification settings for the new ratings before then. In the meantime, find everything that uses vendor ratings:

  1. On the Home screen, click Manage notifications. In the Vendor Risk section, note which notifications on vendor scores are switched on. See How to manage your Home screen.
  2. If you're an administrator, click the Settings icon, then Custom Notifications, and note any custom notifications that use a vendor's score, such as a vendor's score dropping by 10 points in 7 days. See How to create custom notifications.
  3. If you're an administrator, click the Settings icon, then the Integrations tab, and note any integrations with score triggers, such as "When a vendor's score drops by 10 in 7 days". See How to integrate UpGuard with other services using webhooks.
  4. If you use the ServiceNow Vendor Risk integration, open UpGuard CyberRisk Settings in ServiceNow and note the Score Drop Delta and Minimum Score values, which create issues from rating changes. See How to set up ServiceNow Vendor Risk integration with UpGuard.
  5. List any GRC tools, dashboards, or risk scores that pull vendor ratings through the API.

Pay most attention to anything that contacts vendors or opens tickets automatically, and tell the owners of any integrations that ratings will change on March 10th 2027.

❗ Don't change your notification thresholds yet — your current rating counts until March 10th 2027, so thresholds set for the new ratings would misfire before then.

🎵 If you also use Breach Risk, see Breach Risk: Preparing for the March 2027 Security Rating Update for notifications on your own rating.

Reassessments and remediation requests

  • Check what changed before you contact a vendor. If a vendor's rating moved but its identified risks didn't, the change comes from how risks are weighted, not from anything the vendor did. Decide whether its risks still call for a remediation request under your risk tolerance.
  • Use rating impact to prioritize. From March 10th 2027, each risk will show its rating impact, so you can see which of a vendor's risks weigh most and start your requests there. Rating impact explains the rating; it isn't a forecast of what a fix is worth.
  • Expect questions from vendors. If you contact a vendor about a rating drop, the vendor may ask why its rating moved when it hasn't changed anything. Its identified risks may well be the same, so point to the risks behind your request: each risk's rating impact will show what drives the vendor's rating. You can also share the Scoring Update announcement, which explains the change.
  • Review rating targets. Targets in remediation plans or vendor scorecards may be met or missed because of the update rather than remediation.
  • Compare Security Profile assessments on the same side of November 4th 2026. A reassessment after that date may score differently from the previous one even if nothing about the vendor changed.

Reporting, audit, and exceptions

  • Board and executive reporting. Before March 10th 2027, tell your board or risk committee that some movement in vendor ratings will come from the update, not the vendors. Keep a record of vendor ratings just before and after March 10th 2027 so you can show which changes came from the update. Your rating history will mark the date the new scoring method takes effect.
  • Audit records. Published Security Profile assessments keep their original rating, and reports you've already downloaded don't change. Add the effective dates — November 4th 2026 for Security Profile assessment ratings and March 10th 2027 for security ratings — to any methodology documents that refer to UpGuard ratings.
  • Risk exceptions. After March 10th 2027, update the ratings recorded in your exceptions register, and check which vendors now fall above or below your threshold. Consider tying close conditions to fixing specific risks rather than reaching a rating.

Record your vendors' ratings

Do this just before March 10th 2027, and again just after, so you can show which changes came from the update:

  1. Go to Vendor Risk > Vendors.
  2. Optional: to include extra fields, such as custom vendor attributes, click Columns and select them.
  3. Click Export, select Excel, and click Export.