Today’s been a bit hectic for me, so I’m going keep this one short. It’s inspired by a conversation I just had with someone we’ve worked with previously who reminded me that of all the stuff I’ve talked about so far, one of the the…well, many things I haven’t yet talked about that you’ll learn if you’re part of next week’s cohort is how to use the architectures you produce…
…to create “mind blowing” realizations of the value of architecture…
…within the operations teams.
Yeah, that’s right. Because one of the things that is normally a pit deeper than the Mariana Trench is the place where the architecture artifacts you manage to create (if you manage to create them at all) eventually end up.
The very idea that you can use the methods of The Agile Security System™ that you’ll learn as part of the next cohort of Building Effective Security Architectures to connect the organization’s strategy to security strategy…to security operations…
…is pretty-much unheard of.
It’s kinda dragon, griffon and unicorn mythical-beast territory. Sure, theoretically, it’s possible, but what most of the people who try quickly learn…
…is they don’t have the right foundation on which to actually pull it off.
Hint: a control library is CERTAINLY not going to be up to the job.
You need something more. Something formalized and based on a unified theory…
…that can be practically implemented in a systematic way.
In our case, SABSA provides the former, and The Agile Security System provides the latter.
Now you might be thinking that this is a pretty tall order to fill – especially if you’ve tried to do this sort of thing in the past. Because you don’t really know what’s important…you see a sequential set of steps…
…or you get lost in 66 cells of the 2 main SABSA matrices.
What you’ll specifically learn as part of Module 3 when we start putting all of the puzzle pieces we’ve worked to individually identify and flesh out in the previous modules is this:
The specific value of each of our potential customers can get from our architecture efforts. And this is effectively the same whether it’s a DevOps, Agile or “traditional” waterfall/SDLC approach you’re trying to support.
Sure the mechanics are different – which you’ll also learn – but the value – that’s right, the VALUE each of our security customers requires will be the same.
What’s that value?
I guess you’ll just have to join the cohort to find out. But time’s running out since there’s only 2 more days to make sure you get in before the 11:59pm US/Eastern registration deadline.
If you want to:
…understand the most powerful ways to justify the architecture you want to build
…learn how to integrate “real” architecture with Agile and DevOps—the right way, and
…build extensible, SABSA-based, enterprise (non-technical to technical) security architectures one piece at a time that are ALWAYS going to fit together
Then here’s the link to join the cohort starting next week:
Andrew S. Townley
Archistry Chief Executive