Risk
7/22/2010
02:37 PM
50%
50%

NIST Releases Virtualization Security Guidelines

The security of a virtualization solution is "heavily dependent" on the security of each of its components, according to the National Institute of Standards and Technology.

The National Institute of Standards and Technology (NIST) has issued new guidelines for the implementation of full virtualization that address common security concerns with the technology.

In the "Guide to Security for Full Virtualization Technologies," published this month, NIST makes several recommendations to garner the full benefit of using virtualization to improve operational efficiency and cut costs.

Though it's not as swift on adoption as the private sector, the federal government is increasingly using virtualization across agencies. A recent report from CDW found that 77 percent of federal, state and local agencies are implementing at least one form of virtualization, and of those, 89 percent said they are benefiting from the technology.

Above all, organizations should carefully plan their virtualization deployments, factoring security in as they plan installation and configuration of the system, according to NIST. The standards body said that many performance and security problems with virtualization solutions can be traced back to a lack of planning or management controls in the initial stage of the project.

The security of a virtualization solution also is "heavily dependent" on the security of each of its components, according to NIST.

The standards body recommends that organizations secure each individual component of a virtualization implementation -- such as the hypervisor, host OS, guest OSes, applications and storage -- to ensure the deployment as a whole is secure.

A general rule of thumb should be to apply the same security standards to a virtualized OS as an organization would apply to one running on physical hardware, according to NIST.

"If the organization has a security policy for an application, it should apply the same regardless of whether the application is running on an OS within a hypervisor, or on an OS running hardware," according to the guide.

Organizations also should restrict and protect administrator access to a virtualized solution to improve security. This is especially important because some virtualization products offer multiple ways to manage hypervisors, according to NIST.

"Organization should secure each management interface, whether locally or remotely accessible," the standards body recommended.

In terms of hypervisors, NIST recommends that each one of those be individually secured and monitored for signs of compromise. Moreover, organizations also should provide physical access controls for the hardware on which the hypervisor is running.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-6090
Published: 2015-04-27
Multiple cross-site request forgery (CSRF) vulnerabilities in the (1) DataMappingEditorCommands, (2) DatastoreEditorCommands, and (3) IEGEditorCommands servlets in IBM Curam Social Program Management (SPM) 5.2 SP6 before EP6, 6.0 SP2 before EP26, 6.0.3 before 6.0.3.0 iFix8, 6.0.4 before 6.0.4.5 iFix...

CVE-2014-6092
Published: 2015-04-27
IBM Curam Social Program Management (SPM) 5.2 before SP6 EP6, 6.0 SP2 before EP26, 6.0.4 before 6.0.4.6, and 6.0.5 before 6.0.5.6 requires failed-login handling for web-service accounts to have the same lockout policy as for standard user accounts, which makes it easier for remote attackers to cause...

CVE-2015-0113
Published: 2015-04-27
The Jazz help system in IBM Rational Collaborative Lifecycle Management 4.0 through 5.0.2, Rational Quality Manager 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Team Concert 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Requirements Composer 4.0 through 4.0.7, Rational DOORS Next Generation...

CVE-2015-0174
Published: 2015-04-27
The SNMP implementation in IBM WebSphere Application Server (WAS) 8.5 before 8.5.5.5 does not properly handle configuration data, which allows remote authenticated users to obtain sensitive information via unspecified vectors.

CVE-2015-0175
Published: 2015-04-27
IBM WebSphere Application Server (WAS) 8.5 Liberty Profile before 8.5.5.5 does not properly implement authData elements, which allows remote authenticated users to gain privileges via unspecified vectors.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.