πŸ‘‹ Welcome to Unlocked

This week we're tackling a glaring blind spot in the world of cybersecurity - digital supply chain compromise.

Your organization's security isn't solely defined by your firewalls, policies, or even your team anymore. It's actually defined by the weakest API, vendor, or plugin that's connected to your environment.

As the saying goes: "Your strength is only as good as the weakest link in your chain".

In today's digital ecosystem, everything relies on trust - and that trust is being exploited. Attackers are targeting software providers, managed service partners and other vendors to take down dozens or even thousands of downstream targets in one hit.

The SolarWinds breach and the MOVEit Transfer hack showed just how easily one compromised link can spread like wildfire across the globe. Yet, despite this, very few organizations have a clear view of who their vendors rely on - or what's lurking beneath the surface.

So let's dive in.

🧩 The Hidden Web of Third- and Fourth-Party Risk

When organizations talk about supply chain risk, most people think about their direct vendors. But the reality is, your vendors have their own vendors, and your software dependencies are pulling in code from all over the place.

That's fourth-party risk - a problem you can inherit without even realizing it, let alone having any control over it.

  • The average enterprise uses over 1,200 cloud services, according to Netskope.

  • Gartner estimates that 60% of organizations will face a supply chain attack via a third-party relationship by 2026.

  • And according to Black Kite, 98% of companies have at least one third-party vendor that’s already suffered a breach.

All of these relationships can't just be firewalled away - they need to be mapped, monitored and managed continuously - not just when you're onboarding new vendors.

The key takeaway here is: Extend your visibility beyond just your first-tier vendors. Adopt continuous monitoring and require vendors to share their own dependency chains with you

(See: NIST Special Publication 800-161: Supply Chain Risk Management Practices for Federal Information Systems and Organizations.)

πŸ› οΈ SBOMs: The Software Ingredient Label We’ve Needed

Just like how food labels tell you exactly what's in your meal, a Software Bill of Materials (SBOM) is a list of every component that's inside your software - including open-source libraries, frameworks and dependencies.

When done right, SBOMs allow organizations to:

But adoption remains slow. A Linux Foundation report found that while 78% of organizations recognize SBOMs as critical, fewer than 35% have fully implemented them.

WWhy? Because it's just too complicated, there's no standardization, and vendors are often resistant to sharing this information. Yet as attacks like Log4j and XZ Utils showed, not knowing what's in your software isn't bliss - it's basically an invitation to an attacker.

Takeaway: Ask your vendors to provide SBOMs and integrate them into your vulnerability management pipeline. Visibility is your best line of defense.

πŸ” Vendor Access: The Overlooked Doorway

Even with all your internal controls in place, many breaches start with vendor credentials. A third-party IT provider, HVAC company or analytics platform often has privileged access - and attackers know it.

The issue isn't that we don't trust our vendors - it's that we over-trust them.

Vendors need limited, temporary and auditable access. But too often, credentials just stay active long after the project ends or the scope changes.

Quick fix: Audit all external accounts every quarter. Revoke stale API keys, rotate vendor passwords and enforce MFA for every external user.

For the more advanced organizations, consider adopting zero trust for third parties - treat every external connection as untrusted until you've verified it.

πŸ“¦ Continuous Monitoring: Don’t Just Vet β€” Verify

Most vendor risk programs just stop at the initial security questionnaire. But threats don't just stand still - neither should our visibility.

Continuous monitoring platforms can flag issues like:

  • Domain expirations or hijacks

  • Breached credentials

  • New vulnerabilities in open-source components

  • Policy or compliance lapses

Tools like SecurityScorecard, UpGuard, and Panorays can help make this process automatic, giving teams a real-time view of their vendor posture.

Takeaway: Move away from static assessments and towards dynamic, risk-based monitoring. Your third-party risk surface is constantly changing - your defenses need to be too.

⚠️ Why This Matters

Every company now operates as a web of interdependencies - vendors, APIs and software with all sorts of connections that leave you vulnerable to a single point of failure. When one link goes down the whole thing can come crashing down.

The MOVEit breach alone impacted over 2,000 organizations through a single file-transfer vendor. That’s the new reality we’re looking at.

The harsh reality is you can't get rid of third party risk entirely. But you can make it visible, measurable, and something you can actually do something about.

For more on how MSPs can turn secure vendor management into a value-add, check out Everykey’s guide for MSPs.

πŸ›‘οΈ How to Fortify Your Digital Supply Chain

For IT & Security Teams:

  • 🧩 Build and maintain a vendor inventory β€” including fourth-party dependencies.

  • πŸ“¦ Require SBOMs and integrate them into vulnerability management workflows.

  • πŸ” Implement continuous vendor monitoring tools.

  • 🧰 Enforce least-privilege and time-bound access for all vendors.

  • 🧾 Review and renew vendor risk assessments annually β€” or after any major vendor change.

For Business Leaders:

  • 🀝 Make supply chain risk a board-level priority.

  • πŸ’° Fund automated monitoring and third-party audits.

  • βš–οΈ Embed security clauses in all vendor contracts.

  • 🧠 Train teams to recognize hidden risks in SaaS procurement and integrations.

πŸ’‘ Unlocked Tip of the Week

Take a look at what kind of components the top 5 software vendors you use are relying on and what third-party libraries they have. You might be surprised at just how many you hadn’t noticed before.

πŸ“Š Poll of the Week

Do you currently track your vendors’ fourth-party dependencies?

Login or Subscribe to participate

πŸ™‹ Author Spotlight

Meet Mike McDonald - Cybersecurity Solutions Consultant

With nearly two decades of entrepreneurial experience in the charity and nonprofit space, Mike McDonald brings a people-first approach to his role as a Cybersecurity Solutions Consultant at Everykey. Passionate about technology and innovation, Mike thrives on helping businesses transform their access management processes through practical, human-centered solutions.

A lifelong learner and natural connector, Mike loves exploring emerging technologies, building relationships, and understanding what drives others to succeed. Outside of work, Mike’s energy carries into fitness β€” he’s been a personal trainer for over 17 years and was formerly a sponsored runner with New Balance and Under Armour.

βœ… Wrapping Up

We're all part of a larger network of connections these days and that means we've got to start thinking of our enterprise like one - a bunch of interconnected pieces that have to all work together.

But putting trust in something without really checking is just waiting for trouble to strike.

By mapping out all your dependencies, getting the transparency you need and continuously monitoring who you partner with you can turn your supply chain from your biggest weak point into a real competitive advantage.

Stay vigilant. Stay connected. Stay secure.

Until next time,

The Everykey Team



Keep Reading

No posts found