Results. However, “results” implies a couple of things. First, it implies that you know what you’re after, and secondly, it implies that you know how to measure it. Following on from the theme of “things I hear when speaking with people” from yesterday, I often come across people who’ve been exposed to SABSA in particular, […]
You’re already doing security architecture…
One thing that comes up from time to time when I’m speaking to security leaders, like the CISO or the CSO or whomever is in charge of the function, and that’s how far down on the priority list security architecture often is. There’s always new threats to tackle, new fundamental, health & hygiene controls to […]
Is security driving from the back seat?
I have to admit, I was the perfect demographic for the original release of Police Academy in 1984—even though I was too young to go to the cinema to see it by myself. However, I remember thinking it was pretty funny at the time. For some reason, when I was thinking about the problems security […]
Who owns your calendar—really?
One of the things that I’ve heard from people, since I’ve started yammering on about the February cohort of Building Effective Security Architectures in response to the course requirements of 5-10 hours per week for 7 weeks, was a concern about how they would fit it in to their existing workload. And it’s a truly […]
Artifact overload getting you down?
As you might’ve discovered in your own architecture work, it’s pretty easy to get overwhelmed with security architecture documentation. I remember the very first “proper” architecture description I did according to then IEEE1471:2000 (now ISO/IEC/IEEE 42010:2011) was 165 pages. And that was supposed to only be about the federated identity solution I was working on […]
- « Previous Page
- 1
- …
- 27
- 28
- 29
- 30
- 31
- …
- 57
- Next Page »
