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.

Risk

9/8/2009
03:22 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

DNSSEC Secures Another Domain

The .edu domain will adopt DNSSEC next March amid more concern over Domain Name System security

Education and academic community domain .edu is about to become the next top-level domain adopt the Domain Name Systems (DNS) security protocol.

Domains ending in .edu will be able to digitally sign their domains with DNSSEC by the end of next March. DNSSEC is basically an extra layer of authentication that helps protect the DNS translation process from being compromised by attackers.

DNSSEC has been gaining momentum during the past year in the wake of researcher Dan Kaminsky's finding of a major DNS cache poisoning flaw. The .org domain is signed, federal agencies must adopt DNSSEC by December for their .gov domains, and new FISMA regulations call for agencies to sign their intranet zones with DNSSEC by the middle of next year. And VeriSign plans to sign .net with DNSSEC by the end of 2010, and .com in early 2011.

While .edu's move to DNSSEC will allow institutions to digitally sign their domain names, security experts and officials say just when or if the registrants themselves will go DNSSEC is unclear. "The first step is to make the necessary changes in the zone so that individual registrants can take advantage of it," says Steve Worona, director of policy and networking programs for EDUCAUSE, which operates the .edu domain. "And it's [their] decision of when and whether they will sign their [domain]."

The .edu domain is one of the smallest, with about 6,000 registrants, but its adoption of DNSSEC could serve as a case study for the larger domains, Worona says. "This is quite a technologically savvy community [as well]. People understand what DNSSEC is and what its value would be," he says.

EDUCAUSE and VeriSign, which is the .edu registry, are launching a DNSSEC testbed this month in order to gradually roll out the protocol in the domain.

"It's great to see .edu signing their zone -- educational institutions are aggregations of enormous numbers of nodes, all of which may have legitimate reasons to need to identify one another across university boundaries," says Kaminsky, director of penetration testing for IOActive. "DNSSEC will help with this."

The U.S. Department of Homeland Security (DHS) in a report (PDF) report last month declared DNS one of the most at-risk pieces of the U.S. IT infrastructure. "And it points directly at DNSSEC as a way to mitigate risk" of DNS attack, notes Cricket Liu, vice president of architecture for Infoblox.

DHS also flagged identity management as a key component to shoring up Internet security. "I've been saying for a while: Fixing DNS is how we fix the Internet's inability to scalably authenticate," Kaminsky says. "So it's really interesting to see DHS call out weaknesses in present authentication models right after calling for DNSSEC -- the latter is broken precisely because of the former."

But even with .edu, .gov, and .org onboard with DNSSEC, one big missing link remains: signing the root with DNSSEC. "It's great to have parent zones signed," Liu says. "But unless you protect the entire transaction from root to authoritative name server to give you the ultimate answer, DNSSEC is not that helpful."

And DNS administrators won't consider going DNSSEC until the root is signed, Kaminsky says. "None of this work is operationally useful until the day the root is signed," he says. "Second, DNSSEC needs to be completely and utterly automatic. Cookbooks are not the answer."

Gopala Tumuluri, vice president of marketing at Nominum, says there's been more progress with DNSSEC adoption in the past year than there has been in the protocol's nearly 15 years of existence, and agreement on the root is making some inroads. "There have been some political battles at the root...with ICANN and other top-level domain owners over who should sign and own the root. More recently, there's been some convergence on shared responsibility there," Tumuluri says.

Earlier this month ICANN announced it will work with the National Telecommunications and Information Administration (NTIA_, the National Institute of Standards and Technology (NIST), and VeriSign to ensure the Internet's root zone is digitally signed with DNSSEC this year.

Meanwhile, signing domains is a big step, but there's still a long way to go for DNSSEC to trickle down to an actual organization's Website. "A lot of organizations don't have DNS experts sitting around, and a lot of operators don't understand it," Tumuluri says. "This is a big challenge. And DNSSEC adds a whole new dimension of complexity to DNS operations, which could cause problems. There will be slow movement to it because people don't want to take big leaps and screw things up."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Microsoft Patches Wormable RCE Vulns in Remote Desktop Services
Kelly Sheridan, Staff Editor, Dark Reading,  8/13/2019
The Mainframe Is Seeing a Resurgence. Is Security Keeping Pace?
Ray Overby, Co-Founder & President at Key Resources, Inc.,  8/15/2019
GitHub Named in Capital One Breach Lawsuit
Dark Reading Staff 8/14/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-15132
PUBLISHED: 2019-08-17
Zabbix through 4.4.0alpha1 allows User Enumeration. With login requests, it is possible to enumerate application usernames based on the variability of server responses (e.g., the "Login name or password is incorrect" and "No permissions for system access" messages, or just blocki...
CVE-2019-15133
PUBLISHED: 2019-08-17
In GIFLIB before 2019-02-16, a malformed GIF file triggers a divide-by-zero exception in the decoder function DGifSlurp in dgif_lib.c if the height field of the ImageSize data structure is equal to zero.
CVE-2019-15134
PUBLISHED: 2019-08-17
RIOT through 2019.07 contains a memory leak in the TCP implementation (gnrc_tcp), allowing an attacker to consume all memory available for network packets and thus effectively stopping all network threads from working. This is related to _receive in sys/net/gnrc/transport_layer/tcp/gnrc_tcp_eventloo...
CVE-2019-14937
PUBLISHED: 2019-08-17
REDCap before 9.3.0 allows time-based SQL injection in the edit calendar event via the cal_id parameter, such as cal_id=55 and sleep(3) to Calendar/calendar_popup_ajax.php. The attacker can obtain a user's login sessionid from the database, and then re-login into REDCap to compromise all data.
CVE-2019-13069
PUBLISHED: 2019-08-17
extenua SilverSHielD 6.x fails to secure its ProgramData folder, leading to a Local Privilege Escalation to SYSTEM. The attacker must replace SilverShield.config.sqlite with a version containing an additional user account, and then use SSH and port forwarding to reach a 127.0.0.1 service.