When we were defining the security strategy for Authress, the common advice out there was either too rigid and impractical, or a very shallow regurgitation of what everyone does. Not much has changed in the last few years - the advice you get is still the same, but the number and intensity of attacks increased globally for everyone. I wanted to fill that gap with a pragmatic view focused on the why, so that security is more accessible for everyone.

Leaders and practitioners in any sort of enablement role who are curious about security, and disgruntled security people who want a fresh perspective.

I’ll share multiple little tips on securing your development process and I’m hoping everyone will find at least one thing they can immediately apply in their teams. My biggest hope, though, is to impart a way of thinking about security that you can fold into your work that will let you figure out what makes the most sense in your situation.

While everyone has their eyes on AI, we seem rather oblivious to the increasing fragmentation of global markets and how it’s spilling into the digital space. We’ll see way more arbitrary boundaries set by different countries, forcing us to rethink not just our business models, but also how we make our software.