Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Use case

Third-Party Risk Monitoring: Turn Changes Into Decisions

Third-party risk monitoring is the ongoing review of cyber risk from suppliers after a relationship begins. It tracks changes against the supplier’s criticality, checks evidence with the supplier, and sends material findings to a decision owner. NIST CSF 2.0 calls for supplier risk to be monitored over the course of the relationship under GV.SC-07.

Connected supplier nodes with a highlighted risk change

Use case

Third-party risk monitoring starts with a ranked supplier list and a clear owner for each finding. Check changes in the services, access, and data that matter to your organization. Brandefense third-party risk management solution supports daily risk refresh and continuous monitoring.

Who it is for

Roles
Third-party risk

Last updated

In short

Third-party risk monitoring is the ongoing review of cyber risk from suppliers after a relationship begins. It tracks changes against the supplier’s criticality, checks evidence with the supplier, and sends material findings to a decision owner. NIST CSF 2.0 calls for supplier risk to be monitored over the course of the relationship under GV.SC-07.

The problem

  1. Every supplier gets the same queue

    A critical service provider and a low-impact vendor should not receive the same review effort. NIST GV.SC-04 calls for a known supplier list ranked by criticality. The broader supply chain and vendor risk use case covers the full supplier program.

  2. A public signal is treated as a confirmed incident

    A mention, exposed service, or changed score is a lead for investigation. It does not establish a breach. Record the source and time, then ask the supplier to confirm scope before changing its third-party risk record.

  3. Reviews happen only at renewal

    New access, a service change, or a security finding can alter risk before a contract ends. NIST SP 800-161 recommends regular review intervals and documented triggers for reassessment outside that cycle.

How it works

From first signal to a closed case

Each step hands the next one a finished piece of work.

  1. Rank suppliers by what they support

    Keep a supplier inventory with the service owner, business dependency, data sensitivity, and system access. Set criticality levels using those criteria. NIST’s supply chain quick-start guide names service importance, data sensitivity, and access as examples.

  2. Choose evidence and a change threshold

    For each critical supplier, record the evidence you expect, its source, and the review interval. Include agreed security reports, supplier notices, and changes found by your own team. Define which changes merit a fresh third-party risk management assessment.

  3. Verify the finding with the supplier

    Log the observed change and ask the supplier what is affected, when it began, and what evidence supports its account. Keep the external signal separate from the supplier’s response. Escalate when the finding meets the agreed threshold or the supplier cannot resolve a material gap.

  4. Route three decisions to their owners

    Give security an access decision, procurement a contract or requirement decision, and the service owner a continuity decision. Include relevant suppliers in incident planning and recovery, as NIST GV.SC-08 advises. The third-party risk role coordinates these handoffs.

What you get

What changes once it runs

  • A focused review queue

    Critical suppliers and material changes receive attention first, with the reason for each priority visible.

  • A traceable decision

    Each finding has its source, supplier response, owner, reassessment result, and next review date.

  • Clear action across teams

    Access, contract, and continuity owners can act on the same verified facts without treating a warning as proof of an incident.

Questions

Questions people ask about Third-Party Risk Monitoring: Turn Changes Into Decisions

How often should we review a supplier?

Set an interval based on criticality and the change signals you can collect. NIST SP 800-161 also recommends off-cycle triggers, so a material change can prompt reassessment before the next scheduled review.

What should trigger an unscheduled review?

Examples include new system access, a change to a critical service, a supplier notice, or a security finding that affects agreed requirements. Record the trigger and verify its scope with the supplier before deciding on a response.

Does a dark chat post prove a supplier breach?

No. Brandefense Blackhole counted 3169 Third-Party dark chat posts from August 19 to November 17, 2026. Separate source counts may overlap. A post alone does not establish an incident; verify relevant signals with the supplier and internal evidence.

What is different from an initial supplier assessment?

An initial assessment informs the decision to enter a relationship. Monitoring checks whether the risk picture changes during that relationship and records when the supplier needs a fresh assessment or a different response.

Keep exploring

All use cases

Glossary term

Third-party risk

Third-party risk is the chance that an outside organization you rely on, such as a vendor, supplier or service provider, harms your security.

Read more

Glossary term

Third-Party Risk Management (TPRM)

Third-party risk management (TPRM) is the program a company uses to find, assess, reduce and monitor the risks that come from vendors, suppliers, service providers and other outside parties.

Read more

Next step

Review the next material supplier change

Start with one critical supplier. Check its service, access, and evidence record, then name who will verify the next change and who can approve a response.