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.)