DevOps.com

  • Latest
    • Articles
    • Features
    • Most Read
    • News
    • News Releases
  • Topics
    • AI
    • Continuous Delivery
    • Continuous Testing
    • Cloud
    • Culture
    • DevSecOps
    • Enterprise DevOps
    • Leadership Suite
    • DevOps Practice
    • ROELBOB
    • DevOps Toolbox
    • IT as Code
  • Videos/Podcasts
    • DevOps Chats
    • DevOps Unbound
  • Webinars
    • Upcoming
    • On-Demand Webinars
  • Library
  • Events
    • Upcoming Events
    • On-Demand Events
  • Sponsored Communities
    • AWS Community Hub
    • CloudBees
    • IT as Code
    • Rocket on DevOps.com
    • Traceable on DevOps.com
    • Quali on DevOps.com
  • Related Sites
    • Techstrong Group
    • Container Journal
    • Security Boulevard
    • Techstrong Research
    • DevOps Chat
    • DevOps Dozen
    • DevOps TV
    • Digital Anarchist
  • Media Kit
  • About
  • AI
  • Cloud
  • Continuous Delivery
  • Continuous Testing
  • DevSecOps
  • Leadership Suite
  • Practices
  • ROELBOB
  • Low-Code/No-Code
  • IT as Code
  • More Topics
    • Application Performance Management/Monitoring
    • Culture
    • Enterprise DevOps

Home » Features » The Problem With Security

Collaborative Security - DevOps Connect - DevSecOps - RSAC - RSA Conference - CrowdSec - cybersecurity - security - DevOps

The Problem With Security

By: Don Macvittie on April 20, 2022 Leave a Comment

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.

DevOps/Cloud-Native Live! Boston

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.

Recent Posts By Don Macvittie
  • DevSecOps Tools: Hot Air Ahead
  • Security Debt: Speed vs. Common Sense
  • What We Don’t Know is Dangerous
More from Don Macvittie
Related Posts
  • The Problem With Security
  • Q & A with Kevin Behr on DevOps, its impact on security, and the challenges of bringing change to the organization
  • DevOps Chat: AppSec and DevSecOps with Contrast Security’s Jeff Williams
    Related Categories
  • Blogs
  • DevOps Practice
  • Enterprise DevOps
  • Features
    Related Topics
  • CISO
  • devops culture
  • devsecops
  • gamification
  • infosec
  • security
Show more
Show less

Filed Under: Blogs, DevOps Practice, Enterprise DevOps, Features Tagged With: CISO, devops culture, devsecops, gamification, infosec, security

Sponsored Content
Featured eBook
The 101 of Continuous Software Delivery

The 101 of Continuous Software Delivery

Now, more than ever, companies who rapidly react to changing market conditions and customer behavior will have a competitive edge.  Innovation-driven response is successful not only when a company has new ideas, but also when the software needed to implement them is delivered quickly. Companies who have weathered recent events ... Read More
« Encore Platform for Running Distributed Apps in the Cloud Arrives

TechStrong TV – Live

Click full-screen to enable volume control
Watch latest episodes and shows

Upcoming Webinars

2022 Container Security Trends: Expert Panel Livestream
Wednesday, April 20, 2022 - 11:00 am EDT
Building High-Performing DevOps Teams
Wednesday, April 20, 2022 - 1:00 pm EDT
How Bitso Empowers Its Devs to Troubleshoot K8s Independently
Thursday, April 21, 2022 - 11:00 am EDT

Latest from DevOps.com

The Problem With Security
April 20, 2022 | Don Macvittie
Encore Platform for Running Distributed Apps in the Cloud Arrives
April 19, 2022 | Mike Vizard
Blast Radius of GitHub Breach Major Security Concern
April 19, 2022 | Mike Vizard
How Engineers Can Contribute to API Security
April 19, 2022 | Austin Jones
Quali Adds Control Plane to Platform to Manage IaC
April 19, 2022 | Mike Vizard

Get The Top Stories of the Week

  • View DevOps.com Privacy Policy
  • This field is for validation purposes and should be left unchanged.

Download Free eBook

DevOps: Mastering the Human Element
DevOps: Mastering the Human Element

Most Read on DevOps.com

Russian Dev Exodus | Puppet IPO FAIL | Intel 18A Ahead of Sc...
April 14, 2022 | Richi Jennings
The Rising Demand for DevSecOps Talent
April 15, 2022 | Keyur Talati
DevSecOps Tools: Hot Air Ahead
April 13, 2022 | Don Macvittie
Why MTTR is a Vital Metric for DevOps Teams
April 14, 2022 | Ganesh Datta
15 DevSecOps Best Practices
April 15, 2022 | Anas Baig

On-Demand Webinars

DevOps.com Webinar ReplaysDevOps.com Webinar Replays
  • Home
  • About DevOps.com
  • Meet our Authors
  • Write for DevOps.com
  • Media Kit
  • Sponsor Info
  • Copyright
  • TOS
  • Privacy Policy

Powered by Techstrong Group, Inc.

© 2022 ·Techstrong Group, Inc.All rights reserved.