Blog dedicado al estudio de la Seguridad de la Información - Privacidad - Seguridad Informatica - Auditoria informática.
(Recopilación de principales noticias, eventos, politicas de seguridad, guías de buenas practicas, normas, estándares, herramientas, otros)
jueves, 21 de febrero de 2013
DNSSEC Deployment: The Time is Now
on making the Internet as secure as possible began alongside the growth
of the Internet. And we’re still having those discussions because, as
the Internet has evolved, so have the ways of securing it. Every aspect
of the Internet calls for a unique means of being secured. As one
example, let me address Internet security and domain names.
you likely know, anything you type into your browser’s address bar or
click in an email must be translated into its numerical equivalent to be
located on the Internet. The translation from typed name to its numeric
form is made via the Domain Name System (DNS). For example, the DNS
translates a domain name like www.google.com
into its IP address equivalent (126.96.36.199). And, in turn, that IP
address number lets your computer locate the website in question.
most things on the Internet, however, the system has vulnerabilities.
Not surprisingly, those vulnerabilities offer a way for attackers to
hijack requests for specific online destination, in a process called
“pharming.” To help mitigate the possibility of that type of attack,
comes DNS Security Extensions (DNSSEC) that let users know if the
address of a website or online service is accurate.
does not solve every Internet-based security issue, but it does offer a
more advanced level of user security for directory look-ups than is
currently in use. It also complements other security technologies and
provides a platform for yet-to-be-developed innovations.
For example, DNSSEC can ensure that a Web browser knows where to find
the site you are trying to reach. Browsers can employ this information
to help protect users from phishing attacks and from being hijacked.
Although browsers don't use DNSSEC in this way today, they easily could
(and probably should.) Although you can still be hijacked and your site
could still be the victim of phishing attacks, including DNSSEC in an
overall security strategy will help to mitigate the risk to users.
DNSSEC Deployment Challenges
its strong security benefits, DNSSEC has not had an equally strong
deployment track record. As recently as a year ago, DNSSEC had been
deployed on less than one percent of the Internet and on only 82 out of
the 300-plus top-level domains, including .INFO, .ORG, .GOV, .NET and
.COM. Today, the story remains the same with no progress on 98 percent
of all industry domains tested in January 2013 by National Institute of
Standards and Technology (NIST), an agency of the U.S. Department of
At least the ball is starting to roll. Last year, Comcast moved to DNSSEC-validating DNS servers for its millions of customers. It also signed all of the domains used by the company, such as www.comcast.net.
While that is terrific news, it makes Comcast only the first large ISP
in North America to have fully implemented DNSSEC. The fact that it took
until 2012 for a large American ISP to take the plunge doesn’t bode
well for the rapid adoption of DNSSEC (as noted by the 98 percent “no
progress” figure I cited above).