SpaceX is using Syft, Grype, and OWASP Dependency Check as Software Bill of Materials (SBOM) and vulnerability discovery tools integrated into their software development process and continuous integration pipelines to secure diverse supply chains across interconnected systems.
- SpaceX is launching a rocket a week and putting thousands of satellites into space, which requires a secure software development process
- The government process is slow and manual, so SpaceX is bridging the gap by implementing an automated process
- SpaceX is using Syft, Grype, and OWASP Dependency Check as SBOM and vulnerability discovery tools to reduce the cycle time for developers to respond to potential vulnerabilities
- The integration of these tools has allowed SpaceX to more efficiently prioritize how developers work across projects
SpaceX had a problem with a complex binary that builds from a couple of different projects internally and then gets built itself into a container. The binary has a lot of dependencies, making it difficult to determine the full scope of software, libraries, and tooling contained within a diverse set of components. SpaceX solved this problem by implementing an automated process using Syft, Grype, and OWASP Dependency Check as SBOM and vulnerability discovery tools integrated into their software development process and continuous integration pipelines.