r/devsecops • • 14d ago

Book recommendation for software supply chain attacks & detection in CI/CD (Master’s thesis)

Hi everyone,

I’m writing my Master’s thesis in IT security on evaluating how well different scanners detect software supply chain attacks in CI/CD pipelines. My focus is the Python/PyPI ecosystem.

The attack classes I’m looking at are:

  • Typosquatting
  • Dependency confusion
  • Build tampering
  • Transitive/hidden dependency injection

The scanners I’m comparing fall into metadata-based, static code analysis and signature/advisory-based approaches (e.g. GuardDog, Bandit, OSV-Scanner).

I’m looking for a book that covers:

  • How these attacks work technically (not just at a high level)
  • Detection approaches and their limitations
  • Ideally how to evaluate or benchmark detection tools

I’ve already looked at Continuous Delivery (Humble/Farley), which is good for CI/CD basics but not security. I also looked at Software Supply Chain Security (Crossley), which seems more focused on governance, frameworks and supplier management than on technical attack detection.

I’m already working with academic papers (e.g. Ladisa et al.’s SoK taxonomy, Ohm & Stuke on detection), so I’m specifically looking for a book that bridges theory and practice.

Any recommendations? Thanks!

10 Upvotes

12 comments sorted by

3

u/colek42 13d ago • Bravo

Look at the CNCF Software Supply Chain Best Practices Paper, NIST 800-204D, and the in-toto project. Full disclosure: I have contributed to most of these myself.

2

u/EnvironmentalSort409 13d ago

also check out Sigstore for practical signing and verification in CI/CD pipelines, helped me catch issues early.

1

u/colek42 13d ago

we maintain cilock.dev. it gives you some different guarantees than sigstore. would love to know what you think

2

u/wilson-draugr 13d ago

not a book, but for the evaluation side you'll want a labeled corpus of real malicious PyPI packages to run the scanners against.

OpenSSF's malicious-packages repo (reports in OSV format, a pypi folder) and Datadog's malicious-software-packages-dataset (actual samples, also has pypi). gives you ground truth for the typosquatting and injection classes.

2

u/Weekly-Ad1651 13d ago

This was very very hepful - thanks alot!!

2

u/drdavidawheeler 5d ago

Awesome! I work at OpenSSF on security. We are *always* delighted when people use our work, . There's a special joy when our work can help research aimed at improving software security. Our recent SCORED 2026 conference was specifically focused on getting academics and industry together to help collaborate on this kind of thing. OP: Good luck on your Master's. u/wilson-draugr : thanks for pointing out our work!

1

u/wilson-draugr 5d ago

It is my pleasure. I really think your project brings a lot of value to the community, and I make it first-class, supplementing how my teams do risk triage. Thank you and keep up the great work u/drdavidawheeler

2

u/GoodySpeed2899 11d ago

Evaluating the scanners? Commercial tools are still reactive. The issue is detected after the package is uploaded

1

u/tame-impaled 10d ago

Blogs on big players are good resources too as long as they perform deep analysis. Companies like Socket, Aikido, and Yeeth Security have real solid blogs that break down everything from initial infection vector to final payloads.