How Okta empowers devs to find & fix security issues with Snyk
summary
Okta uses Snyk to continuously scan images added when the release manifest is committed, enriches findings with runtime location and source-repo links, and maps results across about 600 unique images to avoid duplicate work. The pipeline opens single-click PRs and auto-bumps release manifests so fixes deploy automatically; long-term plans prioritize shift-left scanning, automated base-image patching, and centralized asset reporting to replace manual spreadsheets and ticket chasing. Insights for application-impact prioritization enters beta.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:35Okta overview
- 3:09Snyk private instance
- 4:07Snyk private link
- 5:14Scanning containers
- 6:14Deployment abstractions
- 7:03Golden Gate Bridge
- 8:20Reporting
- 9:02Where we are today
- 9:23Image enrichment
- 11:05The future
- 11:37Golden base images
- 11:54Automation
- 12:49Custom base images
- 15:25Common base images
- 16:27Insights
- 18:19Wrap up
related talks
31mFrom Noise to Notes: Orchestrating SAST with Developers... (Adrián Puente Z.)
50mA data driven approach to application security
57mDev-first security: From code to cloud, and back to code (PRT291)
30mDevSecOps: How to Level Up IT Security Expertise in Your Organization
10mGuy Podjarny, Snyk | Node Summit 2017
41mWhat Is Devsecops? Key Steps to Do It Well
31mAdvancing security analytics with Snowflake and AWS at Snyk (PRT329)
18mContinuous Security - Building Security into your Pipelines