Skip to main content

What is a supply chain attack?

A supply chain attack compromises a trusted vendor, software dependency, or update channel to reach that supplier's customers.

Glossary
Updated 2 min read

Definition

Supply chain attack

Also called Supply chain compromise, Software supply chain attack, T1195

A supply chain attack compromises a product, service, or supplier that organizations trust, such as a software dependency, build system, update channel, or IT provider, in order to reach the supplier's customers.

How it works

MITRE ATT&CK describes supply chain compromise (T1195) as manipulating products or product delivery mechanisms before a final consumer receives them, in order to compromise data or systems. It splits the technique into three parts: compromising software dependencies and development tools, compromising the software supply chain itself, and compromising hardware.

Attackers looking to run code have often focused on malicious additions to legitimate software in distribution or update channels. Popular open-source packages are targets because one poisoned dependency reaches every application that uses it. Attackers may push malware to a broad set of customers but only follow up with chosen victims, and MITRE notes "second-order" compromises, where access from one supply chain breach is used to compromise another software component. Service providers are a related route: compromising an IT provider can give access to the organizations it manages.

NIST's cybersecurity supply chain risk management (C-SCRM) program frames the defensive side as identifying, assessing, and mitigating risks across the whole life cycle of ICT and OT products and services, from design to destruction. CISA and NIST's joint guidance explains how software customers and vendors can apply C-SCRM and the Secure Software Development Framework to these risks.

Example

A widely used build tool's update server is breached and a signed update carries a backdoor. Thousands of customers install it as routine. Weeks later, a vendor advisory names the affected versions and the backdoor's network destinations. The SOC's job is to answer quickly: which hosts ran the affected version, did any contact those destinations, and what did the tool's service account do afterward?

Why it matters for a SOC

Supply chain attacks arrive through software and accounts that are trusted by design, so preventive controls rarely stop them. Response depends on fast, accurate asset and software inventory, logs retained long enough to look back to the compromise window, and threat intelligence that turns an advisory into specific hunts and detections. Limiting what trusted software and service accounts can reach, a core idea of zero trust, reduces the blast radius when one of them turns hostile.

Sources

  1. Supply Chain Compromise, Technique T1195 - Enterprise | MITRE ATT&CK · accessed November 16, 2026
  2. Defending Against Software Supply Chain Attacks | CISA · accessed November 16, 2026
  3. Cybersecurity Supply Chain Risk Management | CSRC · accessed November 16, 2026

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo