The DNS flaw scare appears to have spooked the feds into requiring widespread adoption of DNSSEC.
A new federal policy issued this week says all federal agencies must adopt the secure DNS standard, DNSSEC, by December of 2009 for their DNS servers. The new Office of Management and Budget (OMB) mandate is a departure from its previous policy that recommended that only high and moderate impact systems adopt the DNS Security Extensions technology, which digitally signs DNS records so that DNS responses can be validated as legitimate.
DNS security has been front-burnered lately, with the exposure of the big DNS flaw and subsequent attacks on servers that havent patched it. Not everyone agrees that DNSSEC is the answer, however: The only thing DNS and DNSSEC have in common are the first three letters in their names, says David Ulevitch, CEO of OpenDNS and a DNS expert. I dont think its a good move for the federal government to adopt DNSSEC, he says.
Ulevitch argues that DNSSEC adoption requires an overhaul of the DNS infrastructure and that there are better and simpler options out there. For DNSSECs validation model to work for DNS servers, it has to be adopted from end to end, he says. If any along the path dont [implement] it, its useless, Ulevitch says. It requires a whole signing infrastructure, which is expensive and manpower-intensive, not to mention politically charged issue of control over the digital keys, he says.
Mark Beckett, vice president of marketing at Secure64, a DNSSEC vendor, says that DNSSEC deployment is less complex now, with products such as Secure64s that help ease the process. DNSSEC adds critically needed security to DNS that no other technology can duplicate. Time spent on developing other solutions will just delay closing the vulnerability, Beckett says.
OpenDNSs Ulevitch and others have come up with alternative DNS security solutions that are easy to deploy and dont making radical changes to the DNS infrastructure, Ulevitch says. Not everyone has to deploy it for it to be effective immediately, he says of the solution he helped build, called DNS Ping.
Meanwhile, the federal government has set an ambitious deadline of January of next year for converting the top-level .gov domain to DNSSEC. This policy requires that the top level .gov domain will be DNSSEC signed and processes to enable secure delegated sub-domains will be developed. Signing the top level .gov domain is a critical procedure necessary for broad deployment of DNSSEC, increases the utility of DNSSEC, and simplifies lower level deployment by agencies, wrote Karen Evans, administrator for the OMBs Office of E-Government and Information Technology in a memorandum to agencies sent out late last week.
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