Risk
1/25/2012
02:09 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Feds Issue Comprehensive Cloud Security Guidance

National Institute of Standards and Technology urges government and private sector users not to leave cloud security to providers or service arrangements.

Federal Data Center Consolidation Makes Progres
Federal Data Center Consolidation Makes Progress
(click image for larger view and for slideshow)
There's no silver bullet to ensuring security in the public cloud, but organizations need to take the reins and not leave security up to service providers and service arrangements, the National Institute of Standards and Technology (NIST) said in comprehensive new cloud security guidance.

In addition to exhorting cloud users not to leave security up to service providers, the Guidelines on Security and Privacy in Public Cloud Computing, which was first made available in draft form last year, boils the keys of cloud security down to a few salient points and provides recommendations on how organizations should navigate contracting for and using cloud services.

Thanks to its statutory role in setting cybersecurity requirements for federal agencies, most NIST security documents place a sharp focus on government users. While the new security guidance is nominally prepared for federal agencies, it appears to have a broader audience in mind as well--unlike many NIST documents, few sections of the 80-page document focus exclusively on the federal government.

[ Learn more about government cloud operations. See Federal Researchers Push Limits Of Cloud Computing. ]

Though the document doesn't focus exclusively on federal agencies, it's the type of thing that they may well be digging into. As the White House pushes agencies to shift toward the cloud, security has been such a high-level concern that the government created an entirely new security accreditation process, FedRAMP, to help guide agencies and service providers through the vagaries of federal cloud security, and agency CIOs regularly raise concerns about security in the cloud. NIST released a final list of FedRAMP's security controls earlier this month.

The guidance details a few of the risks about which organizations should remain particularly wary. For example, large and complex cloud environments provide a large attack surface and numerous points of potential failure; multi-tenant architectures, with only virtual separation between instances, open up a risk that attackers could overcome separation mechanisms; and the mere fact that the services are available over the Internet opens up new threats from outside a company's own networks.

"Accountability for security and privacy in public cloud deployments cannot be delegated to a cloud provider and remains an obligation for the organization to fulfill," NIST program manager Tim Grance said in a statement.

The document laid out recommendations on how organizations should tackle cloud deployments, beginning with specifying a litany of security, privacy, and other requirements--from access control to vulnerability scanning--to narrow the choices among service and delivery models. According to the document, once requirements are penned, risks should be assessed in relation to the type of data that the organization plans to host in the cloud. For example, personally identifiable information might be subject to more risks and therefore more controls than a public-facing website might. That should be followed by an assessment of cloud providers' security.

At the next stage, NIST said organizations should establish strong contractual obligations around security, delineating the roles and responsibilities of both the service provider and the organization that will be using the cloud. Once the contract is in place, NIST said, organizations should continually assess contractor performance and make sure that, before they switch to a new cloud provider, they eliminate providers' access rights to their data and resources and get that data back.

In addition to its cloud security guidance, NIST also released draft reports detailing how federal agencies should continuously monitor IT systems for security vulnerabilities. Continuous monitoring, rather than compliance as a paperwork exercise, has become the central theme of federal cybersecurity guidelines over the last few years. Those documents include a technical reference architecture to facilitate continuous monitoring, technical specs for that reference model, and a document that focuses on applying the reference architecture to asset, configuration, and vulnerability management.

As enterprises ramp up cloud adoption, service-level agreements play a major role in ensuring quality enterprise application performance. Follow our four-step process to ensure providers live up to their end of the deal. It's all in our Cloud SLA report. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
creadk9j
50%
50%
creadk9j,
User Rank: Apprentice
2/2/2012 | 4:02:46 PM
re: Feds Issue Comprehensive Cloud Security Guidance
Anything to avoid being efficient. It might put some union workers out of their comfy jobs and pensions.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading, January 2015
To find and fix exploits aimed directly at your business, stop waiting for alerts and become a proactive hunter.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5437
Published: 2014-12-17
Multiple cross-site request forgery (CSRF) vulnerabilities in ARRIS Touchstone TG862G/CT Telephony Gateway with firmware 7.6.59S.CT and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) enable remote management via a request to remote_management.php,...

CVE-2014-5438
Published: 2014-12-17
Cross-site scripting (XSS) vulnerability in ARRIS Touchstone TG862G/CT Telephony Gateway with firmware 7.6.59S.CT and earlier allows remote authenticated users to inject arbitrary web script or HTML via the computer_name parameter to connected_devices_computers_edit.php.

CVE-2014-7285
Published: 2014-12-17
The management console on the Symantec Web Gateway (SWG) appliance before 5.2.2 allows remote authenticated users to execute arbitrary OS commands by injecting command strings into unspecified PHP scripts.

CVE-2014-7880
Published: 2014-12-17
Multiple unspecified vulnerabilities in the POP implementation in HP OpenVMS TCP/IP 5.7 before ECO5 allow remote attackers to cause a denial of service via unspecified vectors.

CVE-2014-8133
Published: 2014-12-17
arch/x86/kernel/tls.c in the Thread Local Storage (TLS) implementation in the Linux kernel through 3.18.1 allows local users to bypass the espfix protection mechanism, and consequently makes it easier for local users to bypass the ASLR protection mechanism, via a crafted application that makes a set...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.