Risk

9/23/2010
01:27 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Report: Government Agencies Lag In DNSSEC Adoption

New report shows DNSSEC adoption slow within the .gov community, with many missing federal mandate deadline

Nine months have passed since the federal government's deadline for deploying DNSSEC, but only 36 percent of federal agencies' domains are authenticated with the DNS security protocol.

A new report from Internet Identity (IID) analyzed nearly 3,000 .gov domains in federal, state, local, and Native American agencies and found that DNSSEC adoption is making little progress. DNSSEC digitally signs DNS domains, which helps prevent cache poisoning attacks that intercept and redirect users' Internet requests to malicious or unintended sites.

Most federal agency domains in .gov are not being signed with DNSSEC, the report found; only 38 percent are doing so as of mid-September. Around 36 percent are fully authenticating their domains with DNSSEC, with 421 federal .gov domains out of a total 1,185. And 2 percent of feds' DNSSEC-signed domains are configured incorrectly and fail when DNSSEC checks are performed, the report found. IID also found that another 2 percent contain misconfigured DNSes.

"This should be a wake-up call that DNSSEC, likely for a multitude of reasons, is still not being implemented across a wide spectrum of .gov domains despite a mandate to do so," said Rod Rasmussen, president and CTO at IID, in a statement. And "even more worrisome, there is a small percentage of .gov domains that are adopting but not properly utilizing DNSSEC, leaving organizations with a false sense of security and likely problems for their users." Of all .gov domains, 15 percent were fully DNSSEC-signed and authenticated. On the state side, Idaho and Vermont have fully authenticated .gov domains with DNSSEC, and Virginia's domain name is fully DNSSEC-authenticated.

Overall, 40 percent of the .gov domains are federal agencies; 57 percent, state and local; 2 percent, Native American; and 1 percent, nonfederal or other types of organizations.

The report says the bottom line is that .gov's DNSSEC adoption is in the works but has missed its deadlines. "Much has been made about the difficulties of implementing an entirely different DNS standard that is highly complex and new to most administrators. The adoption and error rates for .gov deployment bear that out so far. Yet despite the difficulties, there are many success stories: highly sensitive domains for the FBI, the Federal Reserve, DHHS, and the DEA, along with hundreds more, are being fully signed and authenticated," the report says. "It appears that once a particular agency implements their DNSSEC plan, many or most domains controlled by that organization get signed."

A full copy of the IID DNSSEC report is available for download here (PDF).

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
New Cold Boot Attack Gives Hackers the Keys to PCs, Macs
Kelly Sheridan, Staff Editor, Dark Reading,  9/13/2018
Yahoo Class-Action Suits Set for Settlement
Dark Reading Staff 9/17/2018
RDP Ports Prove Hot Commodities on the Dark Web
Kelly Sheridan, Staff Editor, Dark Reading,  9/17/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-3829
PUBLISHED: 2018-09-19
In Elastic Cloud Enterprise (ECE) versions prior to 1.1.4 it was discovered that a user could scale out allocators on new hosts with an invalid roles token. An attacker with access to the previous runner ID and IP address of the coordinator-host could add a allocator to an existing ECE install to ga...
CVE-2018-3830
PUBLISHED: 2018-09-19
Kibana versions 5.3.0 to 6.4.1 had a cross-site scripting (XSS) vulnerability via the source field formatter that could allow an attacker to obtain sensitive information from or perform destructive actions on behalf of other Kibana users.
CVE-2018-3831
PUBLISHED: 2018-09-19
Elasticsearch Alerting and Monitoring in versions before 6.4.1 or 5.6.12 have an information disclosure issue when secrets are configured via the API. The Elasticsearch _cluster/settings API, when queried, could leak sensitive configuration information such as passwords, tokens, or usernames. This c...
CVE-2018-3823
PUBLISHED: 2018-09-19
X-Pack Machine Learning versions before 6.2.4 and 5.6.9 had a cross-site scripting (XSS) vulnerability. Users with manage_ml permissions could create jobs containing malicious data as part of their configuration that could allow the attacker to obtain sensitive information from or perform destructiv...
CVE-2018-3824
PUBLISHED: 2018-09-19
X-Pack Machine Learning versions before 6.2.4 and 5.6.9 had a cross-site scripting (XSS) vulnerability. If an attacker is able to inject data into an index that has a ML job running against it, then when another user views the results of the ML job it could allow the attacker to obtain sensitive inf...