The Power Of DevSecOps In Web3 And Blockchain
summary
Argues that DevSecOps must be a developer‑first mindset and shows concrete practices: threat modeling hybrid DApp architectures, using chain explorers and Dune for inventory, writing unit tests in Rust and automating them in CI, and fixing a real dice roller contract overflow by changing integer types and redeploying on NEAR. Calls out surprising scale — 5 people managing $60B — and notes audits alone fail; the demos run fast and the fixes are practical and verifiable.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:50Web3 and DevSecOps
- 8:27Software dev and security evolution
- 16:09Web3 vs traditional SDLC
- 23:28Security approaches compared
- 30:11Future of Web3 security
- 33:01Threat modeling in Web3
- 39:39Smart contract testing
- 46:12Asset inventory in blockchain
- 50:06Q&A
related talks
30mThe 3 Ways of DevSecOps – Making Shift Happen
31mDevOps: You Build It, You Secure It
51mSecDevOps: Current Research and Best Practices
33mDefense-Oriented DevOps for Modern Software Development - James Wickett, Signal Sciences
48mHow practical is “DevSecOps” really? – A field report
31mWhy SecDevOps is the new way in Cybersecurity?
30mDevSecOps State of the Union
39mSecurity in a DevOps World