Attacks/Breaches
8/30/2013
06:52 PM
Ehsan Foroughi
Ehsan Foroughi
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Thwart DNS Hijackers: 5 Tips

Domain name system attacks hit The New York Times and Twitter hard last month. Here are five ways to make your DNS records harder to hack and easier to recover if they're compromised.

4. Avoid having low TTL where possible, specifically on master records.

DNS caching can delay a DNS hijacking. The higher the TTL (time to live), the longer a hijacked domain needs to stay hijacked before it can reach the masses. However, many services use low TTL; for instance, only one minute, for load-balancing purposes.

One way of avoiding low TTL on the master record in high-traffic services is to have the master record point to a number of static servers that serve a lean landing page and have all other services use a sub-domain with low TTL.

For example, you can have "your-service.com" with high TTL to serve a small landing/login page, and use "www.your-service.com" and "api.your-service.com" with low TTL service for the rest of the application. As long as the DNS records for "your-service.com" are set up with high TTL and point to your secure DNS servers, hijacking the registrar will take a fairly long time to hit the majority of users due to the caching nature of the DNS.

5. Use high TTL for MX records to delay the hijackers' ability to reroute your emails.

Despite the fact email is known to be inherently insecure, a large amount of confidential information gets passed around in email inside companies. DNS hijackers can essentially steal these emails and cause considerable damage to an organization. Using high TTL for mail exchanger (MX) records in a DNS adds a delay for hijacking emails. Using email encryption such as PGP (pretty good privacy) will also ensure that attackers can't steal the information in the emails.

Previous
2 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio