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.

Comments
Why Automation Will Free Security Pros to Do What They Do Best
Newest First  |  Oldest First  |  Threaded View
ssmall
100%
0%
ssmall,
User Rank: Apprentice
9/10/2018 | 6:02:37 PM
Automation can be great, but it's no quick fix...
Nice article, Roy. Automation and orchestration are indeed 'hot' topics at the moment and are helping many organizations address issues faster and more consistently than they were before. The topics are perhaps also premier candidates for leading the latest round of fads in industry marketing.

Some caveats worth mentioning: new buyers of security automation products may find themselves experiencing sticker shock or falling victim to a still-maturing product space. Many vendor products are prohibitively expensive to the organizations that might benefit most (i.e., the long tail) and too often lock-in users with proprietary workflow formats. That said, automation is worth exploring—and perhaps adopting—for many organizations. My organization has realized numerous benefits to date.

An additional note of caution: I see many organizations rushing to automate workflows without first running the numbers; and, while automation has many benefits, it is first and foremost a matter of economics. Deciding what could, should, and will be slated for automation is an issue of resource management and optimization, whether those resources are people hours, pay-by-use cloud services, or particular team members with in-demand skills and limited availability.

Finally, organizations new to automation need to recognize that deploying new automation workflows is, in many ways, similar to deploying a new "product"—in that the workflows may (in more ways than expected) require additional support resources and know-how for testing, monitoring, and maintenance.


News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23381
PUBLISHED: 2021-04-18
This affects all versions of package killing. If attacker-controlled user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23374
PUBLISHED: 2021-04-18
This affects all versions of package ps-visitor. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23375
PUBLISHED: 2021-04-18
This affects all versions of package psnode. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23376
PUBLISHED: 2021-04-18
This affects all versions of package ffmpegdotjs. If attacker-controlled user input is given to the trimvideo function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23377
PUBLISHED: 2021-04-18
This affects all versions of package onion-oled-js. If attacker-controlled user input is given to the scroll function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.