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
7 Tips To Improve 'Signal-to-Noise' In The SOC
Newest First  |  Oldest First  |  Threaded View
jg@npulsetech.com
[email protected],
User Rank: Apprentice
4/23/2014 | 9:58:54 AM
Re: Lowering the noise level -- gut feelings
Another excellent question Marilyn, thank you.  Gut feelings, or put another way, intuition, can certainly catalyze and inspire investigation and analysis.  Not every feeling or intuition is going to lead in a productive direction of course, and only experience can really help determine what may be a promising intuition vs. what may not be a good use of resources.  For example, it is reasonable to say "I don't think we have any legitimate business traffic to any .ce.ms domains."  Following this hypothesis, the organization should seek the ground truth that is contained in the data.  In my experience, what creates a dangerous feeling or intuition is when decisions are based solely on that feeling or intuition.  If decisions are made based upon investigation and analysis of the data catalyzed by those initial feelings or intuitions, then that can be a good thing in my opinion.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
4/23/2014 | 9:45:40 AM
Re: Lowering the noise level -- gut feelings
Phrases like "this feels like it's less actionable" or "I think this is always a false positive" can be dangerous.

How do you quantify those "gut feelings." And is there no place for them in the SOC?
jg@npulsetech.com
[email protected],
User Rank: Apprentice
4/22/2014 | 2:07:52 PM
Re: Lowering the noise level
Excellent question, Marilyn, and thank you.  In my experience, organizations too often take an "all or nothing" approach to managing the noise level.  For example, an organization may say "we get too many alerts from source X, so we are just going to ignore or turn off all alerts from source X."  I think a better approach would be "let's think about what business, operational, and security needs we can address through alerts from source X and tune source X delicately to address those needs."  Additionally, organizations will sometimes emote or intuit noise reduction.  Phrases like "this feels like it's less actionable" or "I think this is always a false positive" can be dangerous.  The best source for educated decisions is the data.  The data do not lie and form the basis for good security decision making (and the tips provided in the article of course).
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
4/22/2014 | 12:43:17 PM
Lowering the noise level
Thanks for sharing you wisdom with the Dark Reading community Joshua. In your experience, what do you think are the biggest mistakes SOCs make in loweirng the noise level?


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Creating an Effective Incident Response Plan
Security teams are realizing their organizations will experience a cyber incident at some point. An effective incident response plan that takes into account their specific requirements and has been tested is critical. This issue of Tech Insights also includes: -a look at the newly signed cyber-incident law, -how organizations can apply behavioral psychology to incident response, -and an overview of the Open Cybersecurity Schema Framework.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-24999
PUBLISHED: 2022-11-26
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query strin...
CVE-2022-45909
PUBLISHED: 2022-11-26
drachtio-server 0.8.18 has a heap-based buffer over-read via a long Request-URI in an INVITE request.
CVE-2022-45907
PUBLISHED: 2022-11-26
In PyTorch before trunk/89695, torch.jit.annotations.parse_type_line can cause arbitrary code execution because eval is used unsafely.
CVE-2022-45908
PUBLISHED: 2022-11-26
In PaddlePaddle before 2.4, paddle.audio.functional.get_window is vulnerable to code injection because it calls eval on a user-supplied winstr. This may lead to arbitrary code execution.
CVE-2022-44843
PUBLISHED: 2022-11-25
TOTOlink A7100RU V7.4cu.2313_B20191024 was discovered to contain a command injection vulnerability via the port parameter in the setting/setOpenVpnClientCfg function.