Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Operations

2/8/2018
10:30 AM
Joshua Goldfarb
Joshua Goldfarb
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
50%
50%

20 Signs You Need to Introduce Automation into Security Ops

Far too often, organizations approach automation as a solution looking for a problem rather than the other way around.

I've always been a big fan of efficiency. During the period in my career where I built a number of different security operations and incident response programs, I always tried to identify areas where valuable analyst cycles were being spent on time sinks. These time sinks typically involved manual, labor-intensive, often repetitive tasks. If a time sink did not add value to security operations, its value was not worth the time investment, and it could be eliminated. If a time sink was deemed to be essential to security operations, it was an ideal candidate for automation.

Today, talk of automation is everywhere in security. Automation can be a great way to bring about efficiencies, but only if it is done right. Far too often, organizations approach automation as a solution looking for a problem rather than the other way around. How can organizations approach automation intelligently and identify areas that are good candidates for automation? To answer this question, I offer 20 additional questions:

  1. Does your strategic intelligence come in the PDF format? We all need to understand the risks and threats to our organizations at a strategic level, but combing through pages and pages of free-form text isn't the best way to arrive at something actionable that adds value.
  2. Do you make the rounds of several different security news and information sites each day? A noble effort for sure. But first take time to understand exactly what you are looking for and how to integrate into the security workflow.
  3. Where do you get your intelligence? If you mainly source it from emails and portals that require a manual login, it's time to examine what can be done to automate this activity.
  4. How much time do you spend manually cutting and pasting indicators and other such data each day? 
  5. Do you constantly flip between multiple tools and screens? Sometimes this is unavoidable. But other times, technology can help alleviate the "swivel chair" effect.
  6. Do you find yourself manipulating data in Excel (or another such tool) when vetting, qualifying, and/or investigating alerts? 
  7. How often do you cut and paste queries between tools? This is one of the classic time sinks.
  8. How often do you cut and paste query results into and out of incident tickets? 
  9. Do you need to visit numerous log or data sources to get the visibility you need when investigating an alert? This is probably a good opportunity to think about consolidation.
  10. What do I mean by question 9? Is there a more generalized data source that can subsume the data provided by numerous highly specialized data sources?
  11. Do you find yourself running the same queries over and over again? 
  12. Do you know what is on your network, and how it is expected to communicate? Or do you find yourself needing to identify that manually, time and time again?
  13. When a vulnerability is announced, do you find yourself manually performing a set intersect between the vulnerability announcement, your asset database, endpoint data, log data, and network data?
  14. Do you find yourself repeatedly running manual reports for management and executives? Better to take time to understand what they are looking for and to figure out how to get it to them automatically.
  15. Do you find yourself perpetually renewing that consulting contract? Technology has its limitations, and consultants can certainly help in certain situations. But these should be stopgap measures rather than permanent solutions.
  16. When performing vendor risk assessment, do you find yourself buried under a pile of spreadsheets? 
  17. When customers attempt to assess the risk you as a vendor introduce to them, do you find yourself filling out what seems to be the same spreadsheet over and over again?
  18. Do standards and regulations compel you to sit for days on end with auditors and consultants? Perhaps it's worth thinking about automating the way in which you manage and navigate this process.
  19. When wrapping up an incident investigation, do you have to manually check if systems have been remediated and that the issue has indeed been eradicated?
  20. Do you find yourself manually generating post-incident reports on a continual basis? 

There is certainly no shortage of opportunity to introduce automation into the security operations and incident response workflow. Although a blanket approach to automation is seldom productive, targeting automation to specific manual, labor-intensive, and repetitive processes can introduce large efficiencies into a security organization. If done right, the effort will pay large dividends in time and cost savings.

 

Josh (Twitter: @ananalytical) is currently Director of Product Management at F5.  Previously, Josh served as VP, CTO - Emerging Technologies at FireEye and as Chief Security Officer for nPulse Technologies until its acquisition by FireEye.  Prior to joining nPulse, ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
More SolarWinds Attack Details Emerge
Kelly Jackson Higgins, Executive Editor at Dark Reading,  1/12/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4873
PUBLISHED: 2021-01-19
IBM Planning Analytics 2.0 could allow an attacker to obtain sensitive information due to an overly permissive CORS policy. IBM X-Force ID: 190836.
CVE-2020-4881
PUBLISHED: 2021-01-19
IBM Planning Analytics 2.0 could allow a remote attacker to obtain sensitive information, caused by the lack of server hostname verification for SSL/TLS communication. By sending a specially-crafted request, an attacker could exploit this vulnerability to obtain sensitive information. IBM X-Force ID...
CVE-2021-22498
PUBLISHED: 2021-01-19
XML External Entity Injection vulnerability in Micro Focus Application Lifecycle Management (Previously known as Quality Center) product. The vulnerability affects versions 12.x, 12.60 Patch 5 and earlier, 15.0.1 Patch 2 and earlier and 15.5. The vulnerability could be exploited to allow an XML Exte...
CVE-2021-25323
PUBLISHED: 2021-01-19
The default setting of MISP 2.4.136 did not enable the requirements (aka require_password_confirmation) to provide the previous password when changing a password.
CVE-2021-25324
PUBLISHED: 2021-01-19
MISP 2.4.136 has Stored XSS in the galaxy cluster view via a cluster name to app/View/GalaxyClusters/view.ctp.