Risk

8/16/2018
10:30 AM
Jen Andre
Jen Andre
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
100%
0%

Overcoming 'Security as a Silo' with Orchestration and Automation

When teams work in silos, the result is friction and miscommunication. Automation changes that.

While security continues to evolve, adapt, and innovate, there has been a consistent, underlying theme across the industry: Teams are struggling to balance their increasing workloads with the limited resources at their disposal. As a result, it is becoming progressively more difficult for them to accomplish their goals. However, a lesser-known problem has risen, which I like to refer to as a different kind of SaaS: "security as a silo."

It should come as no surprise that large organizations often struggle with teams working in silos. This creates friction and miscommunication, essentially serving as barriers that hinder the accomplishment of important goals. In many respects, security is no different from other business functions this way. But a few organizations have figured out how to utilize specific technologies to increase productivity, efficiency, and effectiveness among employees and processes

The DevOps Revolution
It wasn't long ago when software development and IT operations were siloed themselves. Each function was responsible for specific tasks: developers coded and built software, while IT operations deployed and delivered it. However, this method of software development and delivery wasn't time- or cost-effective, especially as the tech landscape continued to change. Teams were expected to build fast, and deliver even faster, leading to a dev and ops breakdown.

Some good did come out of this, as the heavy stream of security fire drills paved the way for a revolution known as orchestration and automation, which in turn led to the birth of DevOps. With a simple purpose of a single team building, deploying, and delivering software, DevOps changed the game.

The Precipice of Change for Infosec
It's no secret that security teams are distressed, and many suffer the same challenges that developers and operations teams did before the birth of DevOps. To make matters worse, they are inundated with false positives that need to be investigated, causing teams to chase down logs and other intel, only to find that there's not an actual threat. Meanwhile, alerts that do pose a real danger may not be investigated fast enough or at all.

The threat landscape is growing exponentially, and bad actors are more creative than ever — think Mirai, botnets, and unique malware. It's increasingly difficult for defenders to keep up, let alone get ahead of these threats.

Sound familiar?

Security is reaching an inflection point again, and just as security orchestration and automation solutions brought change to software development and IT operations, it will bring change to security operations (SecOps).

The Great Uniters — Orchestration and Automation
As an industry, it's time that we invested in technologies and methodologies that will enhance our tools, processes, and people. We know that orchestration and automation were critical technologies for DevOps to succeed. Why not bring these same concepts to SecOps?

Orchestration unites disparate systems and tools, while also paving the way for machine-to-machine automation. Machines are fantastic at handling a series of repetitive tasks, while humans are great at deriving context from data. Why not offload these repetitive tasks to machines and allow humans to focus on data correlation?

Therein lies the beauty of automation — and coupled with orchestration, it can be extremely flexible. So, what does this mean for security as a whole? Some initial benefits include:

  • The security function is streamlined and more productive.
  • Defenders can get ahead and aren't constantly working from behind.
  • The industry is stronger, more connected and more effective.
  • The way is paved for unity amongst IT teams.

Given the well-known cybersecurity shortage and budget constraints, adding automation to security operations seems unachievable for many organizations, but that doesn't have to be the case. These types of technologies are becoming increasingly accessible for businesses of all sizes, and there is more clarity around which operations should be automated and which require human interaction at some level. Ultimately, the goal is simple — provide security teams with the fastest way to add automation to security processes.

Related Content:

Learn from the industry's most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Early-bird rate ends August 31. Click for more info

Before joining Rapid7, Jen Andre was the Founder & CEO of Komand (acquired by Rapid7), the fastest way to automate your time-intensive security processes. Previously, she co-founded Threat Stack, a pioneering cloud security monitoring company. Jen has spent her career in ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Russia Hacked Clinton's Computers Five Hours After Trump's Call
Robert Lemos, Technology Journalist/Data Researcher,  4/19/2019
Tips for the Aftermath of a Cyberattack
Kelly Sheridan, Staff Editor, Dark Reading,  4/17/2019
Why We Need a 'Cleaner Internet'
Darren Anstee, Chief Technology Officer at Arbor Networks,  4/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-11486
PUBLISHED: 2019-04-23
The Siemens R3964 line discipline driver in drivers/tty/n_r3964.c in the Linux kernel before 5.0.8 has multiple race conditions.
CVE-2019-11487
PUBLISHED: 2019-04-23
The Linux kernel before 5.1-rc5 allows page->_refcount reference count overflow, with resultant use-after-free issues, if about 140 GiB of RAM exists. This is related to fs/fuse/dev.c, fs/pipe.c, fs/splice.c, include/linux/mm.h, include/linux/pipe_fs_i.h, kernel/trace/trace.c, mm/gup.c, and mm/hu...
CVE-2018-7576
PUBLISHED: 2019-04-23
Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent.
CVE-2018-8825
PUBLISHED: 2019-04-23
Google TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local).
CVE-2019-10688
PUBLISHED: 2019-04-23
VVX products using UCS software version 5.8.0 and earlier with Better Together over Ethernet Connector (BToE) application version 3.8.0 and earlier uses hard-coded credentials to establish a connection between the host application and device.