Cloud Control

Corbis

A program aimed at simplifying the required security documentation for cloud companies is more of an obstacle course than an access way into the government sector, some agency and industry officials say.

The Federal Risk and Authorization Management Program, or FedRAMP, has blessed only five out of about 100 vendors applying for certifications that affirm their Web services are safe for agencies governmentwide. All cloud providers interested in selling technology to agencies must comply with FedRAMP controls, such as data backups, by June 2014.

Federal officials say part of the reason for the low passing rate is the rigor of the criteria. FedRAMP bills itself as a standardized approach to cloud security assessments, authorization and monitoring. The idea is for companies to endure the process once and then not have to undergo separate evaluations by each agency customer, officials say. 

“Every cloud provider we’ve worked with has been completely blown away by the level of effort that it takes to do this,” says FedRAMP program manager Matthew Goodrich. “While the first lift is going to be incredibly hard, you don’t have to do that lift again . . . Once it’s done once, there’s not repeated questions, there’s not additional things to ask.”

However, agencies still need to meet other security prerequisites after a company’s service is approved to activate the cloud technology. For instance, a FedRAMP-authorized cloud does not provide certain access restrictions mandated by regulations under the 2002 Federal Information Security Management Act, or FISMA. To meet those requirements, an agency must add more security components, as such as two-factor authentication and the ability to record Web sessions.  

Meanwhile, agencies that are uneasy with any answers they see in FedRAMP documentation can ask the vendor to undergo additional scrutiny, or refuse to accept the contractor at all.

Kevin Dulany, chief of risk management oversight for the Pentagon’s office of the chief information officer, cites Amazon as an example. The server giant clinched a FedRAMP authorization in May.

“I’m going to use your security artifacts and that body of evidence for me to make my own risk decision,” he says. “My process is going to be about a two-week process of verification, and I’m going to make my own decision.”  And the judgment, he adds, might be that “I can’t accept that risk based upon my own operational mission needs.”

In Dulany’s hypothetical situation, even if he chooses to accept Amazon’s security level, the system still would need more controls, according to Amazon’s business collaborators. So the Web services industry is not convinced that FedRAMP makes security assessments more efficient. 

“It certainly runs the risk of being a process that drags everybody down,” says Mike Hettinger, a director at the Software and Information Industry Association. The small number of approvals reflects the difficulty of the method, he says.

Officials at the General Services Administration, the agency running FedRAMP, say documents illustrating how cloud providers meet federal security requirements and any associated risks will differ among providers.

Officials acknowledge that even with FedRAMP, by order of FISMA, agencies still must apply a risk management framework, as well as select, implement and assess appropriate controls.

Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
FROM OUR SPONSORS
JOIN THE DISCUSSION
Close [ x ] More from GovExec
 
 

Thank you for subscribing to newsletters from GovExec.com.
We think these reports might interest you:

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

    Download
  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

    Download
  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

    Download
  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

    Download
  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

    Download
  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

    Download
  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.

    Download

When you download a report, your information may be shared with the underwriters of that document.