A supply chain attack compromises a trusted supplier, update, or component so many downstream customers receive something harmful.
The attacker starts where victims already extend trust, instead of breaking each victim one by one.
How it works
A tainted library, a remote management tool, or a shipment can carry the harm into many organizations at once.
Customers accept the change because the name on it is familiar.
The blast radius is the point, so defense starts with knowing what you depend on.
Signed updates, limited privileges for supplier tools, and a tested rollback shrink the damage.
Concrete examples
- A widely used library update contains an unexpected extra function.
- A provider remote tool is altered and then used across many client networks.
- A hardware shipment is tampered with before it reaches the receiving dock.
Protective measures
- Inventory the suppliers, libraries, and update paths your systems depend on.
- Prefer signed updates and verify them before installation.
- Limit the privileges of tools that a supplier can operate inside your network.
- Practice restoring a known good version when an update looks wrong.