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:

Image Credit: DuMont Television/Rosen Studios. Public domain, via Wikimedia Commons.
Image Credit: DuMont Television/Rosen Studios. Public domain, via Wikimedia Commons.

  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 an experienced information security leader who works with enterprises to mature and improve their enterprise security programs.  Previously, Josh served as VP, CTO - Emerging Technologies at FireEye and as Chief Security Officer for ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...