liveBook · Manning

Software supply-chain attack

A software supply-chain attack compromises a trusted software component, provider, development process, or distribution channel to affect downstream systems or users.

How 3 Manning books explain it

Grokking Software Architecture

A supply chain attack compromises a trusted supplier, dependency, build process, or distribution channel to reach downstream users.

How it is used
Frames third-party dependencies and build pipelines as primary attack vectors in architectural security.
How deep it goes
Defines the attack and traces three incidents, but stops short of detailed prevention steps.
Examples
Contrasts the SolarWinds build compromise, XZ Utils maintainer backdoor, and event-stream package attack.
What you can do after
Evaluate third-party dependencies and build pipelines as potential paths into production.

Read how Grokking Software Architecture explains software supply-chain attack →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

A supply-chain attack compromises software, infrastructure, or dependencies through a provider, maintainer, distribution channel, or development process.

How it is used
Protects infrastructure-as-code adoption by assessing modules and tools before they enter organizational environments.
How deep it goes
Defines the attack and gives a practical screening, isolation, testing, and approval workflow, while acknowledging that risk assessment is simplified.
Examples
Uses leaked passwords during dry runs, unauthorized HTTP endpoints, isolated module deployments, and security and compliance tests.
What you can do after
Evaluate and approve infrastructure modules or tools through code review, isolated testing, scanning, and security and compliance verification.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains software supply-chain attack →

Software Security for Developers

A security attack that compromises software components, providers, or delivery processes to affect downstream applications.

How it is used
Protects applications by treating dependencies and external providers as part of the security boundary.
How deep it goes
Explains dependency compromise through an incident and gives practical scanning, validation, rescanning, and upgrade practices.
Examples
Uses the Event-Stream backdoor, Copay wallet versions 5.0.2–5.1, and a legacy Java library blocking upgrades.
What you can do after
Operate/configure dependency scanning and CI/CD checks to detect, block, and rapidly patch vulnerable libraries.

Read how Software Security for Developers explains software supply-chain attack →

Also covered in

What to know first

Related concepts

Questions about software supply-chain attack

What is software supply-chain attack?

A software supply-chain attack compromises a trusted software component, provider, development process, or distribution channel to affect downstream systems or users.

Which Manning books explain software supply-chain attack?

Grokking Software Architecture, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform and Software Security for Developers.

What should I know before learning software supply-chain attack?

Manning books that teach software supply-chain attack usually introduce infrastructure as code and security first.

What is software supply-chain attack a kind of?

Software supply-chain attack is a kind of cyberattack. A cyberattack is an intentional attempt to gain unauthorized access to, compromise, disrupt, damage, or misuse digital systems, networks, or data.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.