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 Businesses Fail to Address DNS Security Exposures
Oldest First  |  Newest First  |  Threaded View
tdsan
100%
0%
tdsan,
User Rank: Ninja
9/6/2019 | 4:30:22 PM
I do think there needs to be more clarity as to how to address this problem

Having a granular view of users and applications becomes a standard approach, not an exception. Almost all Internet connections are initiated through DNS, meaning DNS sees 95% of traffic going through the network. Analyzing the behavior of each user brings valuable data for detecting potential menaces hidden in the traffic. This surveillance of each client at such a detailed level is key to successful zero-trust strategy. Plus, administrators also should know the status of the network in real time at all times. 

Ok, this is good from a novice standpoint and it explains what we need from a 50K foot view, but how do we really solve the problem. Zero-trust strategy is good but how can you be Zero-Trust when data is coming from the internet that is constantly changing.

For me, there are a few things we did to help address this problem:
  • Implemented IPv6 to run in most if not all of our environment (enable AES256 VPN ESP/AH Connections to your offsite locations)
  • Implement DNSSEC as part of your DNS solution where keys are exchanged
  • Work with companies like Infobox to help address some of your issues
  • Implement ML as part of your cybersecurity strategy at the DNS and network layers

In addition, we need the DNS providers to come up with an IPv6 token based ML solution where the system puts the errant site in a black-list. this would help address 90% of the issues because the sites could be easily identified at all levels of the network because the token or SHA256 hash could be used to create an index (ex of hash - SHA256 F2A3E9E8B019D93818202BDF3AD362F4BAEC7C64589BC635B92E3A8DFD9AD391). This could be the index for Internet sites around the globe and the process can be associated with bad actors who are sending traffic using the 9 primary DNS sites, they could create a blacklist where the actors are stopped before submitting anything to the public.

T
RonanDavid
50%
50%
RonanDavid,
User Rank: Author
9/10/2019 | 12:09:10 PM
Re: I do think there needs to be more clarity as to how to address this problem

Thanks for your comment. The main purpose of the article is to shed some light on the DNS as a perfect tool to help increase security for enterprises. As part of the zero-trust approach, DNS can help in segmenting the application access and have a detailed view of the intent of user clients.

DNSSEC is effectively a good way to add integrity control on the DNS information transported. DNS over TLS would bring confidentiality at the transport level, but clients need to be updated first in the operating systems.

Flow analysis with advanced methods like neural networks or clustering is also an approach to look at. We at EfficientIP are investing a lot in these directions to increase our detection ability of bad domains (such as zero-day malicious domains or DGA) and non-conforming behavior of applications.

Trusting the DNS providers is probably not enough in the space of the enterprise. The distributed model of the DNS is not easy to centralize (nor a good option for Internet service continuity). Enterprises have not (and will not) moved all their workloads and data into cloud infrastructures- some require a higher level of control on their resources, some are not trusting providers for data security. Internal enterprise DNS is still a perfect way to increase security with filtering, segmenting the access to application and analyzing user behaviors. Feeding SIEM with events from the DNS, and some logs in special circumstances, provides a good way to enhance security for enterprise assets and data as a whole. This is the main purpose of security in IT.

USEC
50%
50%
USEC,
User Rank: Apprentice
10/10/2019 | 11:40:20 AM
Source of stats
Ronan - love this article. I've read it probably 6 times since you posted it. So, thanks!

I wanted to ask for the data for for the statistics you mentioned, namely in the precentages year-over-year growth and of attack base. 

Thanks
USEC
50%
50%
USEC,
User Rank: Apprentice
10/10/2019 | 11:41:34 AM
Source of Stats
Ronan - can you provide the source of the statistics in the article?


COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/27/2020
Are You One COVID-19 Test Away From a Cybersecurity Disaster?
Alan Brill, Senior Managing Director, Cyber Risk Practice, Kroll,  10/21/2020
Modern Day Insider Threat: Network Bugs That Are Stealing Your Data
David Pearson, Principal Threat Researcher,  10/21/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15238
PUBLISHED: 2020-10-27
Blueman is a GTK+ Bluetooth Manager. In Blueman before 2.1.4, the DhcpClient method of the D-Bus interface to blueman-mechanism is prone to an argument injection vulnerability. The impact highly depends on the system configuration. If Polkit-1 is disabled and for versions lower than 2.0.6, any lo...
CVE-2020-26156
PUBLISHED: 2020-10-27
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2020-27853
PUBLISHED: 2020-10-27
Wire before 2020-10-16 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a format string. This affects Wire AVS (Audio, Video, and Signaling) 5.3 through 6.x before 6.4, the Wire Secure Messenger application before 3.49.918 for Android, a...
CVE-2020-7755
PUBLISHED: 2020-10-27
All versions of package dat.gui are vulnerable to Regular Expression Denial of Service (ReDoS) via specifically crafted rgb and rgba values.
CVE-2020-11854
PUBLISHED: 2020-10-27
Arbitrary code execution vlnerability in Operation bridge Manager, Application Performance Management and Operations Bridge (containerized) vulnerability in Micro Focus products products Operation Bridge Manager, Operation Bridge (containerized) and Application Performance Management. The vulneravil...