Software Supply Chain, lesson 2
Knowing what you run
Keep an inventory that tells you within hours if an advisory hits you.
"Choosing and updating dependencies" kept bad packages out and fixes flowing in. When a new advisory lands, a different question comes first: which of your services carry the flawed code at all? You'll make that a query over one inventory per build, split the services that ship the code from those that run it, and find the two ways a query says "not affected" when it's wrong.
Part of Pro
In this lesson
- A bill of materials for each build
- Shipping the code, and running it
- Where matching fails quietly
Cybersecurity comes with Pro: every lesson in every module.
Software Supply Chain overviewSpotted a mistake? Tell us.