and beyond: Securely managing open source on AWS
summary
Open source code appears in 99% of projects and Synopsys finds 75% contain vulnerabilities, so rely on concrete controls: use Ubuntu Pro: 10-year security for ~30,000 packages to get extended patches for OS and universe packages, run daily rebuild pipelines because containers are immutable, scan and prioritize fixes with AWS Inspector and SSM Patch Manager, prefer Canonical LTS container images on ECR (fewer known vulnerabilities), and plan for FIPS, Graviton support and SLA-backed vendor maintenance.
AI-written summary · about
chapters (6)
- 0:00Introduction to Canonical
- 3:14Open source challenges
- 5:05Vendor support and maintenance
- 8:41Compliance and best practices
- 9:38Introducing Ubuntu Pro
- 11:30AWS partnership and conclusion
related talks
59mSecurity in the Open: OSS and AWS
41mManaging the risk and growth of using Open Source Software
52mCollaborating to Improve Open Source Security: How the Ecosystem Is Stepping Up
29mSecuring the Unseen: Defending Against Open Source Software Supply Chain Attacks
01h 06mStrengthen open source software supply chain security: Log4Shell to xz
49mTrustworthy Open Source: The Consequences of Success
41mManaging the Risk of Software Supply Chain Attacks
41mBack to Security Basics: Evaluating, Consuming, and Contributing Open Source...