Menu

Not A Vendor, Still A Breach: Vercel’s Third-Party Risk Failure
📰

Not A Vendor, Still A Breach: Vercel’s Third-Party Risk Failure

Forrester·Alla Valente·7 months ago
#70uNBkXu
#statement#masthead#page#risk#access
Reading 0:00
15s threshold

Some security incidents are complex. The Vercel incident is more troubling because it was predictable. The attackers did not exploit a procurement gap. They exploited a definition gap.

Here’s what happened. A Vercel employee signed up for Context.ai’s AI Office Suite using a corporate Google account and clicked something effectively equivalent to “Allow All,” granting broad read access across Google Workspace. That tool was not an Vercel vendor , not under contract, and not in any third‑party inventory. Later, when Context.ai was compromised upstream, attackers reused those OAuth permissions to access Vercel’s internal environment and data.

No zero‑day was required. No controls were bypassed. The access was already approved.

The Freemium Fallacy At Work

This reflects a persistent and dangerous assumption dangerous assumption inside third‑party risk management (TPRM): if the company does not pay for a tool, it is not really a third party .…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.