Innovate w/ confidence across your AI-powered software supply chain
summary
Survey of ~400 companies finds 96% use generative AI coding tools while 75% of teams report unauthorized use and the c-suite is 5x more likely to call that risk “not risky”. Fewer than 20% ran a POC before adoption, two thirds of developers get little or no training, and AppSec flags more insecure code. Recommendations: require POCs with KPIs, prioritize AppSec input, enable cross‑functional governance, and add scanning/SAST guardrails to scale secure AI-assisted development.
AI-written summary · about
chapters (9)
- 0:00Introduction to AI in software
- 1:242024 AI readiness report overview
- 3:12Research methodology and personas
- 5:00Unexpected findings and hypotheses
- 8:10C-suite underestimating AI risks
- 11:47Policy gaps despite AI awareness
- 13:32Lack of preparation before adoption
- 15:39Four key recommendations for AI adoption
- 19:14Closing and resources
related talks
38mGenerative DevOps
15mThe reality of developers using AI | State of Code Developer Survey
24mAI Governance for developers: A practical framework for deploying autonomous coding agents safely…
22mThe AI Accountability Mandate: Securing the Software Supply Chain
12mTrusting AI with Code: How Secure is AI-written code?
34mBuilding Guardrails for AI Coding Systems
52mAI Governance: The Security Perspective
30mGenAI Opportunities and Challenges: Where 370 Enterprises Are Focusing Now