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
When Layers On Layers Of Security Equals LOL Security
Newest First  |  Oldest First  |  Threaded View
RyanSepe
RyanSepe,
User Rank: Ninja
9/29/2014 | 11:42:04 AM
Re: Solution?
I think a correlation of all of those things is a step in the right direction. Unfortunately, to your last comment involving the enforcement of certain protections, many corporations don't start implementing more stringent security capabilities until their burnt so to speak. However, reactive this may be, this is the case with many of the organzations involved in recent breaches.

As Information Security professionals, we need to make it one of the highest priorities to display value in proactive management instead of reactive management. Only then will we even be close to staying ahead of the game.
IMjustinkern
IMjustinkern,
User Rank: Strategist
9/29/2014 | 11:21:27 AM
Solution?
So, does infosec just need better layers? Updated understanding and training of security practices? Or (ugh) compliance/regulation to enforce certain protections?
Otherwise, I'm missing the alternative or secondary path to protect enterprise data.
RyanSepe
RyanSepe,
User Rank: Ninja
9/29/2014 | 9:26:34 AM
Layered Approach
The last snippet sounds like honeypot functionality which I am not entirely certain is the best approach. There are many interesting points made in this article.

I saw McAfee has a type of deterrant program to protect against rootkit if all your systems are an i5 or higher. Which I think in this article would be deemed pretty useful. It seems that in the layered approach consistency is the downfall. I think the point here is evolution. Antivirus and other security layers need to evolve with threats similar to how an IPS uses anomalies to determine if new traffic should be blocked or not. Older technologies that ues the same logic tend to be exploited specifically because they have been out for such a long time and can be tested against. Not to say that AV has not changed but in its core architecture, it models very closely in its procedures to older AV's.

I know this article provides a different perpsective to Defense in Depth but how does the dark reading community feel about UTM? Does this fall into the layered approach due to its all in one housing or does incorporating layers into a cohesive process alleviate some of the woes provided in layered security?


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-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.
CVE-2022-44844
PUBLISHED: 2022-11-25
TOTOlink A7100RU V7.4cu.2313_B20191024 was discovered to contain a command injection vulnerability via the pass parameter in the setting/setOpenVpnCfg function.