Rik Oostveen
Sr. Software Engineer
How not to wipe out
A snow sports enthusiast's guide to cybersecurity
Every ski school teaches the same ten FIS rules: control your speed, respect the signs, help when someone falls. Software security has its own version of those rules, and most wipeouts happen when we blindly rely on our ability to ship like it's a Schuss.
We start where a ski day normally ends: in the hut, during the après, talking over our wildest crashes. What went wrong at Odido, and what is going on with Albert Heijn? Then we take the first lift back up and go down for a few runs: static analysis (SAST), dynamic testing (DAST), reviewing AI-written code, AI-assisted adversarial reviews, and we test our stuff against a deliberately vulnerable .NET app. We finish off-piste, where AI-driven bots are hunting for your endpoints, and where you can lead them into a whiteout of honeypots and endless generated nonsense (preferably without opening yourself up to a Denial of Wallet attack).
For developers who ship like they ski/snowboard, and want to keep it that way without ending up in the safety netting.
