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.

The Syrian Electronic Army: 9 Things We Know
(click image for larger view)
The Syrian Electronic Army: 9 Things We Know
In light of the recent domain name system (DNS) hijacking attacks on The New York Times, Twitter and Huffington Post, it's important for CIOs to take a closer look at their DNS security strategy -- and to be able to respond quickly if their company is attacked.

DNS records are basically sets of instructions that help connect your website to the outside world. The following five practices make these records harder to hijack and easier to recover if they are compromised, thereby reducing the damage attackers can cause. When DNS records are hijacked, a company must be able to get them back as quickly as possible because once the malicious records hit the caching servers, it becomes much harder to undo the damage.

1. Use best practices for credentials that allow changes to be made to DNS records.

Your whole service is only as secure as the security of the password to your DNS registrant account. Ensure that access to accounts used to update DNS records is limited to as few people in your organization as possible. Make sure to use hard-to-guess passwords, and avoid reusing passwords at all costs.

[ Here's why you shouldn't buy Android apps from off-brand sites. Read Hack 99% Of Android Devices: Big Vulnerability. ]

2. Revisit the choice of DNS provider regularly as you grow.

Many companies, particularly start-ups, frequently choose DNS registrants and DNS service providers based on a combination of their pricing and the ease of setup and use. Sometimes that means the DNS provider doesn't have much information about the owner other than a username and password used to identify the account. In cases of social engineering attacks or compromised passwords, it might be hard to reclaim the domain.

As companies grow, they should revisit their choice of provider every few months to make sure that it's capable of handling the level of security the company needs. Popular and high-profile services might be targeted by hackers with agendas -- and not every provider is capable of handling the heat that comes with popularity.

3. Make use of SSL certificates.

DNS hijacking can effectively be used to perform man-in-the-middle (MITM) attacks. In a MITM attack, the attacker diverts the user to a malicious server he controls. The malicious server then sends the user's request to the original server and sends the server's response back to the user. This setup allows the attacker to steal the information being passed back and forth, inject malicious content into responses before sending them back to the user, or both.

This is one of the highest risks associated with DNS hijacking and can cause a lot of damage in the form of stolen credentials and injection of malicious content.

To arm yourself, enforce validation of SSL/TLS certificates and use certificate pinning in mobile apps and rich clients. Certificate validation means the attacker must get a certificate tied to the stolen domain before being able to carry out the MITM attack. Pinning certificates in mobile and rich clients will take this restriction even further by ensuring the attacker will need access to the pinned certificate's private keys before being able to carry out the attack. This will reduce the risk of a MITM attack, which means the DNS hijack will do much less prolonged damage.

Previous
1 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-0914
Published: 2014-07-30
Cross-site scripting (XSS) vulnerability in IBM Maximo Asset Management 6.2 through 6.2.8 and 6.x and 7.x through 7.5.0.6, Maximo Asset Management 7.5 through 7.5.0.3 and 7.5.1 through 7.5.1.2 for SmartCloud Control Desk, and Maximo Asset Management 6.2 through 6.2.8 for Tivoli IT Asset Management f...

CVE-2014-0915
Published: 2014-07-30
Multiple cross-site scripting (XSS) vulnerabilities in IBM Maximo Asset Management 6.2 through 6.2.8, 6.x and 7.1 through 7.1.1.2, and 7.5 through 7.5.0.6; Maximo Asset Management 7.5 through 7.5.0.3 and 7.5.1 through 7.5.1.2 for SmartCloud Control Desk; and Maximo Asset Management 6.2 through 6.2.8...

CVE-2014-0947
Published: 2014-07-30
Unspecified vulnerability in the server in IBM Rational Software Architect Design Manager 4.0.6 allows remote authenticated users to execute arbitrary code via a crafted update site.

CVE-2014-0948
Published: 2014-07-30
Unspecified vulnerability in IBM Rational Software Architect Design Manager and Rational Rhapsody Design Manager 3.x and 4.x before 4.0.7 allows remote authenticated users to execute arbitrary code via a crafted ZIP archive.

CVE-2014-3025
Published: 2014-07-30
Multiple cross-site scripting (XSS) vulnerabilities in IBM Maximo Asset Management 6.2 through 6.2.8, 6.x and 7.1 through 7.1.1.2, and 7.5 through 7.5.0.6; Maximo Asset Management 7.5 through 7.5.0.3 and 7.5.1 through 7.5.1.2 for SmartCloud Control Desk; and Maximo Asset Management 6.2 through 6.2.8...

Best of the Web
Dark Reading Radio