AI in the Security Stack
summary
Panelists argue enterprises must move faster and instrument pipelines with concrete controls: they claim 85% of code comes from the software supply chain, so enforce SBOM+CBOM+AI BOM provenance and avoid pasting proprietary code into public models like Copilot or Mythos. Practical tools are curation, deception/honeypots, identity for agents and discovery, plus versioned YAML stage gates in global CI/CD templates and telemetry. Outcome: governance as code that produces real-time evidence, not post facto screenshots.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 1:00AI in security: speed vs complexity
- 6:30Security as enabler not blocker
- 15:00Software supply chain threats
- 21:50Proving security with AI
- 29:10Embedding security in AI
- 32:00Never give up this control
related talks
33mAI sovereignty, provenance and compliance
25mAI-Driven Supply Chain Security: Using AI-BOM to Detect Hidden Vulnerabilities
12mDevSecOps Playbook for AI-Era CI/CD Pipelines
22mThe AI Accountability Mandate: Securing the Software Supply Chain
24mAI Governance for developers: A practical framework for deploying autonomous coding agents safely…
47mAI and the Future of Software Development
16mNavigating the AI Jungle
28mAI for Everything After Code