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
Security Analysts Are Only Human
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
2/25/2019 | 11:17:49 AM
Re: Automation is KEY
Tier 1 analysts have the highest turnover and burnout rates. That makes sense. It is a tiring workflow, trying to catch one thing in a mass is frustrating too.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
2/25/2019 | 11:14:38 AM
Automation
Viewing alerts is unsustainable in its current form. The role needs to transition to a fully automated process I think this is the important step in security analysist workflow, they can not possible to go over all those false positives.
MariaColeman
50%
50%
MariaColeman,
User Rank: Apprentice
2/25/2019 | 5:21:53 AM
Re: Automation is KEY
Very correctly and logically said.
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
2/22/2019 | 3:45:00 PM
Minimizing Mistakes by Maximizing Actionable Intelligence
As the title denotes, Security Analysts are only human. A human element will always be needed to one degree or another but they are prone to error. For this reason, Security Professionals need to look towards maximizing automatic logic. As stated, receiving 10K alerts per day would be an impossible task to review without automated logic built into the coding of your SOC. We've made great progress but if we can continue to push the limits of our efficiency we can continue to diminish the degree of error that is inherent to our being.
barefoot_marine
100%
0%
barefoot_marine,
User Rank: Apprentice
2/21/2019 | 1:22:07 PM
Automation is KEY
Definitely agree. Implementing solutions that replace Tier 1 assets is critical to effective security growth of an organization. Tier 1 analysts have the highest turnover and burnout rates. We ask them to help secure our infrastructure, but in reality, all they become are button monkeys, clicking yes/no. Barely able to keep up with that, let alone do research to validate the escalation. 

A SOC, coupled with the right internal and external intelligence, plus orchestration can effectively automate Tier 1, finally allowing jr SOC analysts a place to grow into more meaningful workflows.
<<   <   Page 2 / 2


Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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-2020-27348
PUBLISHED: 2020-12-04
In some conditions, a snap package built by snapcraft includes the current directory in LD_LIBRARY_PATH, allowing a malicious snap to gain code execution within the context of another snap if both plug the home interface or similar. This issue affects snapcraft versions prior to 4.4.4, prior to 2.43...
CVE-2020-16123
PUBLISHED: 2020-12-04
An Ubuntu-specific patch in PulseAudio created a race condition where the snap policy module would fail to identify a client connection from a snap as coming from a snap if SCM_CREDENTIALS were missing, allowing the snap to connect to PulseAudio without proper confinement. This could be exploited by...
CVE-2018-21270
PUBLISHED: 2020-12-03
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
CVE-2020-26248
PUBLISHED: 2020-12-03
In the PrestaShop module &quot;productcomments&quot; before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.
CVE-2020-29529
PUBLISHED: 2020-12-03
HashiCorp go-slug before 0.5.0 does not address attempts at directory traversal involving ../ and symlinks.