When dependency hell came for us: A small team's Agile security journey
summary
Quantavia is a tiny aviation-software shop that hits dependency hell when npm supply‑chain attacks (notably an Axios compromise (March, >100M weekly downloads)) steal credentials and poison CI pipelines; mitigations include adopting npm security features (11.6.0 and the upcoming npm2), slowing dependency updates by seven days, and tightening trust in libraries. The team retakes Cyber Essentials Plus required rework to meet buyers, runs regular retrospectives to surface vulnerabilities, uses the free Linux Foundation LFD121 course for training, and adds an AI policy to document legacy code.
AI-written summary · about
chapters (12)
- 0:00Introduction and context
- 3:18Best time to think about security
- 11:26What is dependency hell
- 15:45Supply chain worm Shyid
- 20:37Building on legacy products
- 23:25Cyber Essentials and ISO 27001
- 27:20Who should think about security
- 28:03Embedding security culture
- 32:59Turning things around with retrospectives
- 34:06Lessons from Quantavia
- 39:25Key takeaways and next steps
- 40:30Closing and Q&A
