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/30/2010
04:03 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Federal Government Imposes New IPv6 Deadlines

'Native' IPv6 by FY 2012 for public-facing servers and services

The Obama administration's CIO has informed federal agencies that they must run native IPv6 on their Web, email, ISP, and DNS servers and services by the end of fiscal year 2012, and their internal client applications by fiscal year 2014.

In a Sept. 28 memo (PDF) sent to federal CIOs, Vivek Kundra, the nation's federal CIO, outlined the steps to speed up deployment of the next-generation IP protocol. He said the feds must move to IPv6 so they can expand their cloud computing, broadband, and smart grid projects; eliminate the need for network address translation (NAT); enable secure end-to-end network communications; and foster the expansion of Internet-based services.

The Office of Management and Budget (OMB) has been pushing IPv6 deployment in the government for about five years, but deployment has been slow. The new deadlines might be a bit too ambitious, however, security experts say.

Guy Snyder, secure communications program manager for ICSA Labs, says Kundra's mention of "native IPv6" by 2012 and 2014 is especially aggressive. "I'm glad they're putting teeth" in the policy, he says. "But this is almost a little too aggressive. I know how much work it takes to do this and the issues they are going to run into. 'Native IPv6' is a little too [ambitious]. I think that's going to get reversed. The government will have to go with a dual stack. I don't see them going native IPv6 [then]."

IPv6, which has been in the works for more than a decade now, is back on the radar screens of some organizations due to the pending saturation of IPv4 address space, which is expected to occur anywhere from spring to June 2011. Unlike IPv4, the "new" protocol was built with security in mind: It comes with IPSec encryption, for instance, and its massive address space could help prevent worms from propagating, security experts say. But the adoption of IPv6 also poses new security issues, everything from distributed denial-of-service (DDoS) attacks to new vulnerabilities in IPv6 to misconfigurations that expose security holes.

"In order to facilitate timely and effective IPv6 adoption, agencies shall: Upgrade public/external facing servers and services (e.g. web, email, DNS, ISP services, etc) to operationally use native IPv6 by the end of FY 20121; Upgrade internal client applications that communicate with public Internet servers and supporting enterprise networks to operationally use native IPv6 by the end of FY 2014," Kundra said in his memo.

Meanwhile, the feds' ultimate adoption of IPv6 will lay the groundwork for private industry. The good news about the feds' pushing IPv6 more forcefully is that it will also result in more and better vendor offerings, ICSA's Snyder says. "Vendors will say no one's asking for IPv6, but if the federal government is asking for it, that will make it available for businesses when they realize they need it," he says. "

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 the Executive Editor of Dark Reading. 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

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.