Building Trust in Fintech: DevSecOps Strategies at Saxo Bank
summary
Saxo Bank runs a DevSecOps platform that shifts security left with automated checks: SonCube code quality and test coverage, JFrog and "jrog" scanning for dependencies, image signing and a private registry, hardened base images and Helm charts for developers. Platforms auto-enforce gates, log and monitor runtime (CTIC, Kono), and use a service-orchestrator for access provisioning; bank processes 16 billion USD daily trades, serves ~1.2M clients and backs fixes with a bounty program.
AI-written summary · about
chapters (8)
- 0:00Introduction and Saxo Bank overview
- 2:09Quantifying trust in fintech
- 7:37From DevOps to DevSecOps
- 14:20Saxo Bank’s DevSecOps approach
- 21:49Developer experience and automation
- 26:23Live exploits and bounty programs
- 27:07Change management and compliance
- 35:23Q&A and closing
related talks
46m360 ° DevSecOps Enterprise Adoption
44mThe Implementation and Practice of DevSecOps
33mThe Four Horsemen of DevSecOps
42mThe Challenge and Solutions to Implement DevSecOps into Large Banks
42mThe Challenge and Solutions to Implement DevSecOps into Large Banks
21mDevOps in a Highly Regulated Financial Infrastructure Company
30mThe 3 Ways of DevSecOps – Making Shift Happen
58mDEVOPS in a Multi-Banking World