Risk
12/9/2011
03:51 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

White House Plans Cloud Security Program's Next Steps

Federal CIO Steven VanRoekel marked the official "launch" of the FedRAMP security accreditation service yesterday, but more needs to be done before agencies can take advantage the new program.

50 Most Influential Government CIOs
Slideshow: 50 Most Influential Government CIOs
(click image for larger view and for slideshow)
The White House on Thursday officially released a highly anticipated security framework that it says will accelerate the adoption of cloud computing in government, but agencies won't be able to take advantage of the Federal Risk and Authorization Management Program (FedRAMP) just yet.

FedRAMP will create a government-wide security authorization process that federal CIO Steven VanRoekel estimated on a phone call with reporters Thursday will save the government 30% to 40% in assessing, authorizing, and procuring cloud services.

That's thanks to what he called the program's "do-once, use-many-times framework" in which the FedRAMP program management office would authorize a service, and then other agencies could leverage that authorization, obviating the duplicative and time-consuming security accreditation process that's required today. Without FedRAMP, agencies that want to adopt cloud computing typically duplicate the tests already done by other agencies, which leads to longer-than-necessary lead times to deploy new services.

Although FedRAMP will change this, the program's initial launch, which included the release of a policy memo detailing the program in new depth and setting deadlines for its ramp-up, is just a first step. FedRaMP won't become fully operational and able to take on its full assessment, authorization, and monitoring duties until sometime within the next six months.

[Should we worry about government migrating to the cloud? See Feds: Cloud Computing Doesn't Increase Security Risk.]

FedRAMP has been a long time coming already. The program began in October 2009 in the Cloud Computing Advisory Council's security working group and was first publicly discussed in March 2010. The first draft iteration of the FedRAMP process was released in November 2010. The government missed several deadlines it had publicly announced for the project's release.

The new guidance outlines how the FedRAMP program will actually operate. The General Services Administration and the Department of Homeland Security will run FedRAMP's Joint Authorization Board, which will oversee the overall FedRAMP process. That will include approving private sector companies to assess cloud services for government agencies, prioritizing service authorizations, and issuing initial operational authority to cloud service providers.

In addition to the Joint Authorization Board, FedRAMP will be managed through a program management office in the GSA's Office of Citizen Services and Innovative Technologies. "We'll be performing a lot of the punt, pass, and kick to make it run smoothly," says Dave McClure, director of the office of citizen services and innovative technologies.

The office will create service level agreements, templates, and other elements for the program, as well as a repository to house and securely share assessment, accreditation, and authorization information across agencies.

The National Institute of Standards and Technology, meanwhile, has played a critical role in the development of FedRAMP, developing the applicable system requirements under FISMA and designing and implementing the assessment program itself, and will continue to work on standard assessment procedures.

There are several steps between where FedRAMP is today and its actual initial operating capacity. Within 30 days, the CIO Council will publish FedRAMP's standardized baseline security controls. Within 60 days, the program management office will publish more-detailed process documentation. Within 90 days, the Joint Authorization Board will publish its governance model.

GSA will hold an industry day on Dec. 16 to educate industry members on FedRAMP and its third-party assessment process, which will allow private companies to perform "initial and periodic assessment" of cloud systems in line with FedRAMP requirements, according to an overview of the program.

Our annual Federal Government IT Priorities Survey shows how agencies are managing the many mandates competing for their limited resources. Also in the new issue of InformationWeek Government: NASA veterans launch cloud startups, and U.S. Marshals Service completes tech revamp. Download the issue now. (Free registration required.)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
Partner Perspectives
What's This?
In a digital world inundated with advanced security threats, Intel Security seeks to transform how we live and work to keep our information secure. Through hardware and software development, Intel Security delivers robust solutions that integrate security into every layer of every digital device. In combining the security expertise of McAfee with the innovation, performance, and trust of Intel, this vision becomes a reality.

As we rely on technology to enhance our everyday and business life, we must too consider the security of the intellectual property and confidential data that is housed on these devices. As we increase the number of devices we use, we increase the number of gateways and opportunity for security threats. Intel Security takes the “security connected” approach to ensure that every device is secure, and that all security solutions are seamlessly integrated.
Featured Writers
White Papers
Cartoon
Current Issue
Dark Reading's October Tech Digest
Fast data analysis can stymie attacks and strengthen enterprise security. Does your team have the data smarts?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2021
Published: 2014-10-24
Cross-site scripting (XSS) vulnerability in admincp/apilog.php in vBulletin 4.4.2 and earlier, and 5.0.x through 5.0.5 allows remote authenticated users to inject arbitrary web script or HTML via a crafted XMLRPC API request, as demonstrated using the client name.

CVE-2014-3604
Published: 2014-10-24
Certificates.java in Not Yet Commons SSL before 0.3.15 does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2014-6230
Published: 2014-10-24
WP-Ban plugin before 1.6.4 for WordPress, when running in certain configurations, allows remote attackers to bypass the IP blacklist via a crafted X-Forwarded-For header.

CVE-2014-6251
Published: 2014-10-24
Stack-based buffer overflow in CPUMiner before 2.4.1 allows remote attackers to have an unspecified impact by sending a mining.subscribe response with a large nonce2 length, then triggering the overflow with a mining.notify request.

CVE-2014-7180
Published: 2014-10-24
Electric Cloud ElectricCommander before 4.2.6 and 5.x before 5.0.3 uses world-writable permissions for (1) eccert.pl and (2) ecconfigure.pl, which allows local users to execute arbitrary Perl code by modifying these files.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Follow Dark Reading editors into the field as they talk with noted experts from the security world.