THIRD PARTY
THREAT HUNTING™

Threat Hunters Trophy · Field guide · Jenna Wells

The Early Warning Field Guide

How to hunt vendor risk across every domain, not just cyber: real-time signals, service-delivery locations, fourth parties and a board story that lands. From our conversation with Jenna Wells of Supply Wisdom.

Episode airs Tuesday, October 20, 2026

Save as PDF
“True operational resilience is the oversight and ability to anticipate and adapt while rapidly recovering from disruptions, maintaining critical operations and customer service at the same time.”Jenna Wells

01Are You Hunting in a Single Risk Domain?

  • Your most recent view of a critical vendor is a questionnaire answer, which went stale the moment it was sent
  • Cyber, financial and geopolitical signals come from separate tools, on different scales, and someone stitches them together by hand
  • You monitor where a vendor is headquartered, not where its service is actually delivered
  • You learn about a vendor's new AI providers or fourth parties at renewal, if at all
  • Every alert for every vendor lands on the same small team, so most of them get ignored
  • Your board only hears from third-party risk after something has gone wrong

02Five Moves From Reactive to Preemptive

  1. Make real-time intelligence the baseline and the questionnaire the supplement.A questionnaire still gives you a useful baseline, for example whether a data center has fire suppression. But use continuous signals to decide when to send one, instead of sending them on a calendar.
  2. Look below the waterline.The breach is the tip of the iceberg. Months or years before it there are usually leadership changes, heavy turnover, financial disclosures, a stock dip, a regulatory fine or operational disruption. Watch those domains together and you can start asking questions, and lining up a backup vendor, before the incident.
  3. Monitor where the work happens.Track service-delivery locations, not just headquarters, and layer them across every risk domain. A site can keep its power and connectivity and still stop delivering: when a conflict breaks out, hundreds of thousands of reservists can be called up within days. The city is open and the people who do the work aren't there. Watching location signals such as conflict, sanctions and unrest gives you time to move work to a secondary site before the disruption reaches you.
  4. Route alerts by ownership and threshold.Each risk, procurement, resilience or business owner should see only the vendors they're responsible for, and get alerted only when something crosses a threshold that matters, such as a vendor moving from medium to high. That's how you cut alert fatigue without going blind.
  5. Make fourth-party and AI changes visible.Every contract should require vendors to tell you when they add a fourth party. Map your nth parties so a change at a shared provider shows up against every supplier that uses it. And treat AI as its own risk domain with its own yardstick: your cybersecurity framework alone isn't enough, so adopt an AI risk management framework alongside it.

03Don't Spread It Like Chunky Peanut Butter

None of this means monitoring 8,000 vendors equally. Start where the risk is concentrated. Set your risk appetite from the top, with executive support. Then identify your vendor population, who has access to your data, and which providers are single points of failure, the ones that are systemically critical: if they can't turn their lights on, neither can you. Those go into continuous monitoring first. Everyone else follows as your program matures.

04Show Your Work to the Board

What to show

How many vendors you monitor, how many events hit them this period by domain (financial, cyber, operational, location, compliance), where the portfolio is trending, and what you did about the critical ones.

How to frame it

Articulate the exposure: “this isn't a problem today, but it could be.” After a major incident, send a same-day readout, even when the answer is “we're not exposed.” Agree whether the board wants it quarterly or on demand.

Third-party risk is a cost center, and that's fine: it's insurance. But if leadership only hears from you when a vendor gets breached, they'll associate you with bad news. Regulators are moving the same way. The EU's Digital Operational Resilience Act (DORA) expects financial entities to monitor their ICT providers on an ongoing basis, and US bank regulators increasingly expect it too. In Jenna's experience, examiners are reasonable when you can show a program that's based on your risk appetite and shows steady progress. A shrug is no longer an acceptable answer.

This Week's One Move

Go back to basics and get your baseline. Pull a complete inventory of your vendors (who you've paid in the last 24 months is a good start), then tag every vendor that touches your data and every single-provider dependency. Those vendors are your first continuous-monitoring cohort. Don't chase the newest AI risk until you understand the landscape you already have.

Jenna Wells is Chief Executive Officer of Supply Wisdom, a continuous third-party risk monitoring platform. She was Supply Wisdom's first beta tester in 2015, as a third-party risk practitioner, and later served as a global head of third-party risk. She began her career as a captain and signals intelligence officer in the United States Marine Corps, training at the NSA, and has spent her career turning large data sets into actionable intelligence.