SpyCloud, a company specializing in preventing account takeover and fraud, has launched its Supply Chain Threat Protection solution. This new offering aims to close a critical visibility gap in third-party risk management (TPRM). Instead of relying on periodic vendor assessments and questionnaires, the platform provides continuous, real-time intelligence on identity-related threats affecting an organization's entire vendor ecosystem. By analyzing data recaptured from criminal sources—including breach data, malware logs, and dark web markets—SpyCloud can alert an organization when a partner's employee credentials have been stolen or their device is infected with malware. This enables security teams to take proactive measures to prevent a supply chain compromise from impacting their own environment.
Supply chain attacks are a growing threat, with adversaries increasingly targeting smaller, less secure vendors to gain a foothold into larger, more valuable organizations. The 2025 Verizon Data Breach Investigations Report highlighted that third-party involvement in breaches doubled year-over-year. The specific threats addressed by SpyCloud's solution include:
SpyCloud noted that in the previous year, the top 98 Defense Industrial Base (DIB) suppliers had over 11,000 credentials exposed on the dark web, highlighting the scale of the problem.
SpyCloud's solution shifts the paradigm of vendor risk management from a passive, compliance-based activity to an active, threat-informed defense.
By identifying compromised vendor accounts, the solution enables organizations to apply stricter controls or remediation actions to these specific privileged or semi-privileged third-party accounts.
Enforcing MFA for all third-party access is a critical control that mitigates the risk of a compromised vendor credential being used to gain initial access.
Mapped D3FEND Techniques:
When SpyCloud identifies a compromised credential belonging to a third-party vendor, security teams must immediately increase monitoring on all accounts associated with that vendor. This involves using Local Account Monitoring (and its domain equivalent, D3-DAM) to scrutinize their activities. Create specific SIEM rules to alert on any login event from the compromised vendor account, any attempt to access sensitive resources, or any changes in account permissions. By correlating SpyCloud's external intelligence with internal log data, you can quickly determine if the compromised credential has been used to access your environment and initiate an incident response, turning a potential breach into a detected and blocked attempt.
For critical third-party vendors, organizations should establish a baseline of normal activity using Job Function Access Pattern Analysis. A vendor who provides HVAC support should only be accessing building management systems, not financial databases. When SpyCloud flags a vendor as high-risk due to identity exposure, security teams can apply this baseline to their activity. Any deviation from their expected job function—such as accessing unusual file shares or attempting to RDP to servers outside their scope—should trigger a high-priority alert. This behavioral analysis helps detect when a compromised vendor account is being abused by an attacker for purposes beyond the legitimate job function.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats