As an IT professional with decades of experience at every level of technology and organizationsโfrom cell phone prototyping to banking enterprise architecture, from entry-level to CTOโI can state definitively that I have spent an inordinate amount of time dwelling on and dealing with security. And I know Iโm not alone. This is a common theme. You could almost make a sitcom out of it. โWhat are your developers doing?โ Uhhh … writing code? โThatโs security!โ I could go on, hitting on everything from users to cloud instances and you could fill in the โThatโs security!โ punchline every time.
Thatโs a problem. But not in the way you might think. I spent many years thinking I was somewhat unique in that I always rose to the occasion and approached security issues head-on. Most of the organizations Iโve worked for didnโt have dedicated security (Iโve probably written about that before), so some of us rose to the occasion.ย Nowhere near all of IT, but enough to feel like we were protected.
I now realize that Iโm not all that unique; that more of us are doing the โlearn security to be secureโ thing than are not. I see it in modern organizations all the time. And I think that the real problem is this: Most of these people, like me, did not see themselves as security staffโbut they are. Most organizations donโt recognize them as security staffโbut they are.
Weโve long harped on cultivating security recruits from this pool, and Iโm now going to suggest that you go even further. Make these people part of your planning. If you know that person X on the ReallyCoolApp team is ferreting out security stuff, ask them to just send an email to update InfoSec once a week. Donโt make it a huge burden, and donโt try to force them into a pure security role if they donโt show the aptitude and interest (you really donโt want unwilling security staff) but make use of their talents and drive. Certainly, if this person is doing a good job of making certain ReallyCoolApp is mostly locked down and DevSecOps tools are running against it for a secondary validation, then your limited InfoSec resources can be directed elsewhere.
Replicate this throughout the organization, and โThatโs Security!โ becomes a benefit rather than a hassle to try to lock down. You already do some of thisโsince the automation of passwords, most identity management is handled by operations staff, with security merely providing policy and being available to ops if needed. Iโm simply suggesting that you expand this type of approach to include every IT department (and some non-IT departments in distributed environments). Donโt recruit everyone to be InfoSec, but recruit them to do a little bit of InfoSec in their area of specialty.
People have always said โSecurity is everyoneโs problem,โ which is true, but it’s far too vague to be useful. This is a workable intermediate. โSecurity is every teamโs problemโ and recruiting the people on each team most interested in InfoSec to formalize their involvement is a better approach.
And keep rocking it. We need security everywhere, because neโer-do-wells have made everywhere a part of the InfoSec battleground. So recruit people everywhere without moving them from their current roles/responsibilities. Donโt let the sweet systems youโve nursed through the years get whacked by attackers when a little recruiting and nurturing will fill the gap.




