07:34 PM
Connect Directly
Repost This

Comcast Internet Service Now Fully DNSSEC-Based

ISP finishes its rollout of the DNS security protocol

Comcast today became one of the first major ISPs in North America to fully run the Domain Name System Security Extensions (DNSSEC) protocol as part of its services.

Jason Livingood, vice president of Internet systems in Comcast's network and operations, today blogged that DNSSEC is now part of its Comcast Constant Guard from Xfinity service. That means that nearly 18 million residential customers of the Xfinity Internet service are using DNS servers that use DNSSEC validation. Comcast's more than 5,000 domain names are also now digitally signed by DNSSEC.

DNSSEC has been gradually rolling out across the Internet over the past year or so. Several major top-level domains, including .com, .org, .net, and .gov, are now DNSSEC-enabled. DNSSEC is a protocol for preventing attackers from redirecting users to malicious websites by redirecting them -- it basically ensures DNS entries remain unchanged in transit and are digitally signed to ensure their authenticity.

[After a sluggish start, DNSSEC is finally catching on after more than a decade in the making. See DNSSEC Finally Comes To .com, But Secure DNS Still Has A Long Way To Go .].

"Now that nearly 20 million households in the U.S. are able to use DNSSEC, we feel it is an important time to urge major domain owners, especially commerce and banking-related sites, to begin signing their domain names. While in the past those domains may have wanted to do so but felt it would have limited effect, they now can work on signing their domains knowing that the largest ISP in the U.S. can validate those signatures on behalf of our customers," Livingood said in his post.

Security expert Dan Kaminsky, who discovered a major DNS caching vulnerability in 2008 that helped expedite DNSSEC's adoption, says he's thrilled that Comcast has stepped up and implemented the protocol. "DNSSEC is the proper fix to my 2008 attack, and I am extremely proud of Comcast for taking this step to protect their users," Kaminsky says. "I am particularly happy that they correctly judged the importance of genuine responses higher than their minor income stream from injecting advertisements.

"The integrity of the DNS is of critical importance to present and future security technologies, and Comcast has done their users a service by investing in DNSSEC," he says.

Now when a Comcast subscriber visits a website, Comcast's DNS servers confirm the domain name and check that its signature is valid and legitimate. Comcast also cryptographically signs its own domain names, like xfinity.com.

Comcast traditionally has been ahead of the curve in security for ISPs. More than two years ago, it was one of the first to employ a bot-notification service that notifies customers whose machines it spots as bot-infected. It then directs the infected user to the antivirus center, where he follows directions to remove the bot malware.

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

Kelly Jackson Higgins is Senior 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 Magazine, ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Current Issue
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2014-04-24
Cisco IOS before 15.3(2)S allows remote attackers to bypass interface ACL restrictions in opportunistic circumstances by sending IPv6 packets in an unspecified scenario in which expected packet drops do not occur for "a small percentage" of the packets, aka Bug ID CSCty73682.

Published: 2014-04-24
Cisco ASR 1000 devices with software before 3.8S, when BDI routing is enabled, allow remote attackers to cause a denial of service (device reload) via crafted (1) broadcast or (2) multicast ICMP packets with fragmentation, aka Bug ID CSCub55948.

Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in IBM SmartCloud Analytics Log Analysis 1.1 and 1.2 before allows remote attackers to inject arbitrary web script or HTML via an invalid query parameter in a response from an OAuth authorization endpoint.

Published: 2014-04-24
The openshift-origin-broker in Red Hat OpenShift Enterprise 2.0.5, 1.2.7, and earlier does not properly handle authentication requests from the remote-user auth plugin, which allows remote attackers to bypass authentication and impersonate arbitrary users via the X-Remote-User header in a request to...

Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

Best of the Web