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
Newest First  |  Oldest First  |  Threaded View
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.

tdsan
50%
50%
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


AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4147
PUBLISHED: 2019-09-16
IBM Sterling File Gateway 2.2.0.0 through 6.0.1.0 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 158413.
CVE-2019-5481
PUBLISHED: 2019-09-16
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
CVE-2019-5482
PUBLISHED: 2019-09-16
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
CVE-2019-15741
PUBLISHED: 2019-09-16
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. An unsafe interaction with logrotate could result in a privilege escalation
CVE-2019-16370
PUBLISHED: 2019-09-16
The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.