Inventory That: Building an Automated DevSecOps for 40K Repositories
summary
Describes building an automated DevSecOps inventory pipeline for 40,000 code repositories: what metadata to collect and store in a database, how the inventory process works, and how to use the collected data to solve DevSecOps tasks. Includes sharing the implementation code so teams with fewer repositories can apply the same techniques.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:01What is inventory
- 5:58Implementation challenges
- 7:44Open source release
- 8:29Analytics scenarios
- 13:05DevSecOps pipeline
- 19:13Duplicate results handling
- 21:40Summary
- 24:54Q&A
related talks
42mSecurity, Standards and Maintenance: How to Do It with 5k Repositories?
42mThe Data Behind DevSecOps: The Power of Hindsight to Protect your Supply Chain
43mBuilding a Secure DevOps Pipeline
40mSecure by Default: Building an AI-Augmented, OSS-Powered Reusable CI/CD Pipeline
30mDevSecOps: More Than Just Pipelines
27mSecure by Design: Embedding DevSecOps into Your GitOps Workflows
36mImproving Security while Reducing Toil with DevSecOps
27mStandard Classification: Automate Security, Don't Tell Your Boss
