Attacks/Breaches
8/30/2013
06:52 PM
Ehsan Foroughi
Ehsan Foroughi
Commentary
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
Video
Cartoon
Current Issue
Flash Poll
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3966
Published: 2015-08-30
The IPsec SA establishment process on Innominate mGuard devices with firmware 8.x before 8.1.7 allows remote authenticated users to cause a denial of service (VPN service restart) by leveraging a peer relationship to send a crafted configuration with compression.

CVE-2015-4555
Published: 2015-08-30
Buffer overflow in the HTTP administrative interface in TIBCO Rendezvous before 8.4.4, Rendezvous Network Server before 1.1.1, Substation ES before 2.9.0, and Messaging Appliance before 8.7.2 allows remote attackers to cause a denial of service or possibly execute arbitrary code via unspecified vect...

CVE-2015-5698
Published: 2015-08-30
Cross-site request forgery (CSRF) vulnerability in the web server on Siemens SIMATIC S7-1200 CPU devices with firmware before 4.1.3 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.

CVE-2015-4497
Published: 2015-08-29
Use-after-free vulnerability in the CanvasRenderingContext2D implementation in Mozilla Firefox before 40.0.3 and Firefox ESR 38.x before 38.2.1 allows remote attackers to execute arbitrary code by leveraging improper interaction between resize events and changes to Cascading Style Sheets (CSS) token...

CVE-2015-4498
Published: 2015-08-29
The add-on installation feature in Mozilla Firefox before 40.0.3 and Firefox ESR 38.x before 38.2.1 allows remote attackers to bypass an intended user-confirmation requirement by constructing a crafted data: URL and triggering navigation to an arbitrary http: or https: URL at a certain early point i...

Dark Reading Radio
Archived Dark Reading Radio
Another Black Hat is in the books and Dark Reading was there. Join the editors as they share their top stories, biggest lessons, and best conversations from the premier security conference.