You're only as secure as your weakest supplier. Supply chain security addresses the risk that comes from third parties and the software you build on — a top concern after SolarWinds and Log4j.
Supply Chain Security
Third-party and software dependency risk.
Tap or hover a part to learn more.
Log4j lesson.
Your app depends on many open-source libraries; a vulnerable or compromised one (like Log4j) becomes your vulnerability.
Check your understanding
1. What is an SBOM?
2. What's the lesson of SolarWinds/Log4j?
Keep learning
The two supply chains
- Software supply chain — your app depends on countless open-source libraries; a compromised or vulnerable dependency (like Log4j) becomes your vulnerability. Use dependency scanning (SCA) and an SBOM (Software Bill of Materials) to know what you're running.
- Vendor/third-party — suppliers with access to your systems or data expand your attack surface; assess and monitor their security (vendor risk management, part of GRC).
- Provenance & integrity — verify signed artefacts and trusted sources (container images).
The lesson of recent attacks: attackers target the trusted supplier to reach many victims at once.
