Red Hat Enterprise Linux 6.6 Beta
Virtualization Security Guide
Securing your virtual environment
Scott Radvan Tahlia Richardson
Thanks go to the following people for enabling the creation of this guide:
Paul Moore Kurt Seifried David Jorm
Red Hat Enterprise Linux 6.6 Beta Virtualization Security Guide
Securing your virtual environment
Scott Radvan
Red Hat Engineering Content Services
sradvan@redhat.com
Tahlia Richardson
Red Hat Engineering Content Services
trichard@redhat.com
Paul Moore
Red Hat Engineering
Kurt Seifried
Red Hat Engineering
David Jorm
Red Hat Engineering
Thanks go to the following people for enabling the creation of this guide:
Legal Notice
Copyright © 2012, 2014 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0
Unported License. If you distribute this document, or a modified version of it, you must provide
attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red
Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,
Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity
Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other
countries.
Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.
Java ® is a registered trademark of Oracle and/or its affiliates.
XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United
States and/or other countries.
MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and
other countries.
Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally
related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/service
marks or trademarks/service marks of the OpenStack Foundation, in the United States and other
countries and are used with the OpenStack Foundation's permission. We are not affiliated with,
endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
This guide provides an overview of virtualization security technologies provided by Red Hat. It
also provides recommendations for securing hosts, guests, and shared infrastructure and
resources in virtualized environments. Note: This document is under development, is subject to
substantial change, and is provided only as a preview. The included information and
instructions should not be considered complete, and should be used with caution.
T able of Cont ent s
Table of Contents
. . . . . . . . . . . . . . .
Pref.ace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
`
1. Do cument Co nventio ns 2
`
1.1. Typ o g rap hic Co nventio ns 2
`
1.2. Pull-q uo te Co nventio ns 3
`
1.3. No tes and Warning s 4
`
2. G etting Help and G iving Feed b ack 4
`
2.1. Do Yo u Need Help ? 4
`
2.2. We Need Feed b ack! 5
` . . . . I . . . . . . . . . . . . . .
Ch.ap.t.er.1. .. .n.t .ro d.u.c.t .ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
`
1.1. Virtualized and No n-Virtualized Enviro nments 6
`
1.2. Why Virtualizatio n Security Matters 7
`
1.3. Leverag ing SELinux with sVirt 8
`
1.4. Further Reso urces 8
` . . . . H. . . . . . . . . . . . . . . . . .
Ch.ap.t.er.2. .. . o.s.t .Secu rit y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. 0
`
2.1. Why Ho st Security Matters 10
`
2.2. Ho st Security Reco mmend ed Practices fo r Red Hat Enterp rise Linux 10
`
2.2.1. Sp ecial Co nsid eratio ns fo r Pub lic Clo ud O p erato rs 11
`
2.3. Ho st Security Reco mmend ed Practices fo r Red Hat Enterp rise Virtualizatio n 11
`
2.3.1. Red Hat Enterp rise Virtualizatio n Netwo rk Po rts 11
` . . . . . . . . .Securit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 . . . . . . . . . .
Ch.ap.t.er.3..Gu.e.st . . . . . . y . 3
`
3.1. Why G uest Security Matters 13
`
3.2. G uest Security Reco mmend ed Practices 13
` . . . . s . . . . . . . . . . . . .
Ch.ap.t.er.4. .. . Virt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. 4
`
4.1. Intro d uctio n 14
`
4.2. SELinux and Mand ato ry Access Co ntro l (MAC) 14
`
4.3. sVirt Co nfig uratio n 15
`
4.4. sVirt Lab eling 16
`
4.4.1. Typ es o f sVirt Lab els 16
`
4.4.2. Dynamic Co nfig uratio n 16
`
4.4.3. Dynamic Co nfig uratio n with Base Lab eling 17
`
4.4.4. Static Co nfig uratio n with Dynamic Reso urce Lab eling 17
`
4.4.5. Static Co nfig uratio n witho ut Reso urce Lab eling 17
` . . . . . . . . . . . . . . . .t . . a. Virt . alized. En viro.n.men. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. 8
Ch.ap.t.er.5..Net wo.rk Secu.ri .y. in . . . . u. . . . . . . . . . . . . t . . . . . . . . . .
`
5.1. Netwo rk Security O verview 18
`
5.2. Netwo rk Security Reco mmend ed Practices 18
`
5.2.1. Securing Co nnectivity to Sp ice 18
`
5.2.2. Securing Co nnectivity to Sto rag e 18
. . . . . I . . . . . . . . . . . . . . .
Fu.rt. her .n f.o.rmat.io.n. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. 9
`
A.1. SELinux and sVirt 19
`
A.2. Virtualizatio n Security 19
. . . . . . . o. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. 0
R.e.vi sio.n .H.ist . ry . . . . . . . . . .
1
Red Hat Ent erprise Linux 6 .6 Bet a Virt ualizat ion Securit y Guide
Preface
1. Document Convent ions
This manual uses several conventions to highlight certain words and phrases and draw attention to
specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The
Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not,
alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later include
the Liberation Fonts set by default.
1.1. T ypographic Conventions
Four typographic conventions are used to call attention to specific words and phrases. These
conventions, and the circumstances they apply to, are as follows.
Mo no -spaced Bo l d
Used to highlight system input, including shell commands, file names and paths. Also used to
highlight keys and key combinations. For example:
To see the contents of the file my_next_bestsel l i ng _no vel in your current
working directory, enter the cat my_next_bestsel l i ng _no vel command at the
shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a key, all presented in mono-spaced bold and
all distinguishable thanks to context.
Key combinations can be distinguished from an individual key by the plus sign that connects each
part of a key combination. For example:
Press Enter to execute the command.
Press C trl +Al t+F2 to switch to a virtual terminal.
The first example highlights a particular key to press. The second example highlights a key
combination: a set of three keys pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values
mentioned within a paragraph will be presented as above, in mo no -spaced bo l d . For example:
File-related classes include fi l esystem for file systems, fi l e for files, and d i r for
directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialog-box
text; labeled buttons; check-box and radio-button labels; menu titles and submenu titles. For
example:
Choose System Preferences Mouse from the main menu bar to launch
Mouse Preferences. In the Butto ns tab, select the Left-hand ed mo use check
box and click C l o se to switch the primary mouse button from the left to the right
(making the mouse suitable for use in the left hand).
To insert a special character into a gedit file, choose Applications
Accessories Character Map from the main menu bar. Next, choose Search
2
Preface
Find& from the Character Map menu bar, type the name of the character in the
Search field and click Next. The character you sought will be highlighted in the
C haracter T abl e. Double-click this highlighted character to place it in the T ext
to co py field and then click the C o py button. Now switch back to your document
and choose Edit Paste from the gedit menu bar.
The above text includes application names; system-wide menu names and items; application-specific
menu names; and buttons and text found within a GUI interface, all presented in proportional bold
and all distinguishable by context.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or
variable text. Italics denotes text you do not input literally or displayed text that changes depending
on circumstance. For example:
To connect to a remote machine using ssh, type ssh username@ domain.name at a
shell prompt. If the remote machine is exampl e. co m and your username on that
machine is john, type ssh jo hn@ exampl e. co m.
The mo unt -o remo unt file-system command remounts the named file system.
For example, to remount the /ho me file system, the command is mo unt -o remo unt
/ho me.
To see the version of a currently installed package, use the rpm -q package
command. It will return a result as follows: package-version-release.
Note the words in bold italics above: username, domain.name, file-system, package, version and
release. Each word is a placeholder, either for text you enter when issuing a command or for text
displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and
important term. For example:
Publican is a DocBook publishing system.
1.2. Pull-quote Conventions
Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in mo no -spaced ro man and presented thus:
books Desktop documentation drafts mss photos stuff svn
books_tests Desktop1 downloads images notes scripts svgs
Source-code listings are also set in mo no -spaced ro man but add syntax highlighting as follows:
static int kvm_vm_ioctl_deassign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0;
struct kvm_assigned_dev_kernel *match;
mutex_lock(&kvm->lock);
match = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
assigned_dev->assigned_dev_id);
if (!match) {
printk(KERN_INFO "%s: device hasn't been assigned before, "
"so cannot be deassigned\n", __func__);
3
Red Hat Ent erprise Linux 6 .6 Bet a Virt ualizat ion Securit y Guide
r = -EINVAL;
goto out;
}
kvm_deassign_device(kvm, match);
kvm_free_assigned_device(kvm, match);
out:
mutex_unlock(&kvm->lock);
return r;
}
1.3. Notes and Warnings
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
Note
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should
have no negative consequences, but you might miss out on a trick that makes your life easier.
Important
Important boxes detail things that are easily missed: configuration changes that only apply to
the current session, or services that need restarting before an update will apply. Ignoring a
box labeled Important will not cause data loss but may cause irritation and frustration.
Warning
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
2. Get t ing Help and Giving Feedback
2.1. Do You Need Help?
If you experience difficulty with a procedure described in this documentation, visit the Red Hat
Customer Portal at http://access.redhat.com. Through the customer portal, you can:
search or browse through a knowledgebase of technical support articles about Red Hat products.
submit a support case to Red Hat Global Support Services (GSS).
access other product documentation.
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and
technology. You can find a list of publicly available mailing lists at
https://www.redhat.com/mailman/listinfo. Click on the name of any mailing list to subscribe to that list
or to access the list archives.
4
Preface
2.2. We Need Feedback!
If you find a typographical error in this manual, or if you have thought of a way to make this manual
better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/
against the product Red Hat Enterprise Linux 6 .
When submitting a bug report, be sure to mention the manual's identifier: doc-
Virtualization_Security_Guide
If you have a suggestion for improving the documentation, try to be as specific as possible when
describing it. If you have found an error, please include the section number and some of the
surrounding text so we can find it easily.
5
Red Hat Ent erprise Linux 6 .6 Bet a Virt ualizat ion Securit y Guide
Chapter 1. Introduction
1.1. Virt ualized and Non-Virt ualized Environment s
A virtualized environment presents opportunities for both the discovery of new attack vectors and the
refinement of existing exploits that may not previously have presented value to an attacker. It is
therefore important to take steps to ensure the security of both the physical hosts and the guests
running on them when creating and maintaining virtual machines.
Non-Virtualiz ed Environment
In a non-virtualized environment, hosts are separated from each other physically and each host has
a self-contained environment, consisting of services such as a web server, or a DNS server. These
services communicate directly to their own user space, host kernel and physical host, offering their
services directly to the network. The following image represents a non-virtualized environment:
Figure 1.1. Non-Virtualiz ed Environment
Virtualiz ed Environment
In a virtualized environment, several operating systems can be housed (as "guests") within a single
host kernel and physical host. The following image represents a virtualized environment:
6
`
Chapt er 1 . Int roduct ion
Figure 1.2. Virtualiz ed Environment
When services are not virtualized, machines are physically separated. Any exploit is therefore usually
contained to the affected machine, with the obvious exception of network attacks. When services are
grouped together in a virtualized environment, extra vulnerabilities emerge in the system. If there is a
security flaw in the hypervisor that can be exploited by a guest instance, this guest may be able to
not only attack the host, but also other guests running on that host. This is not theoretical; attacks
already exist on hypervisors. These attacks can extend beyond the guest instance and could expose
other guests to attack.
1.2. Why Virt ualizat ion Securit y Mat t ers
Deploying virtualization in your infrastructure provides many benefits but can also introduce new
risks. Virtualized resources and services should be deployed with the following security
considerations:
The host/hypervisor become prime targets; they are often a single point of failure for guests and
data.
Virtual machines can interfere with each other in undesirable ways. Assuming no access controls
were in place to help prevent this, one malicious guest could bypass a vulnerable hypervisor and
directly access other resources on the host system, such as the storage of other guests.
Resources and services can become difficult to track and maintain; with rapid deployment of
virtualized systems comes an increased need for management of resources, including sufficient
patching, monitoring and maintenance.
Technical staff may lack knowledge, have gaps in skill sets, and have minimal experience in
virtual environments. This is often a gateway to vulnerabilities.
Resources such as storage can be spread across, and dependent upon, several machines. This
can lead to overly complex environments, and poorly-managed and maintained systems.
Virtualization does not remove any of the traditional security risks present in your environment;
the entire solution stack, not just the virtualization layer, must be secured.
7
Red Hat Ent erprise Linux 6 .6 Bet a Virt ualizat ion Securit y Guide
This guide aims to assist you in mitigating your security risks by offering a number of virtualization
recommended practices for Red Hat Enterprise Linux and Red Hat Enterprise Virtualization that will
help you secure your virtualized infrastructure.
1.3. Leveraging SELinux wit h sVirt
sVirt integrates virtualization into the existing security framework provided by SELinux (Security-
Enhanced Linux), applying Mandatory Access Control (MAC) to virtual machines. The main objective
of sVirt is to protect hosts and guests from attacks via security vulnerabilities in the hypervisor.
SELinux secures a system by applying access policy across different processes. sVirt extends this
capability to hosts and guests by treating each guest as a process, allowing administrators to apply
similar policies designed to prevent malicious guests from accessing restricted resources. For more
information on sVirt, refer to Chapter 4, sVirt.
1.4. Furt her Resources
Red Hat offers a wealth of documentation solutions across its virtualization products. Coverage of
Red Hat Enterprise Linux and its inbuilt virtualization products includes:
Red Hat Enterprise Linux Virtualization Getting Started Guide: This guide provides an introduction
to virtualization concepts, advantages, and tools, and an overview of Red Hat virtualization
documentation and products.
Red Hat Enterprise Linux Virtualization Host Configuration and Guest Installation Guide: This guide
covers the installation of virtualization software and configuration of guest machines on a
virtualization host.
Red Hat Enterprise Linux Virtualization Administration Guide: This guide covers administration of
hosts, networking, storage, device and guest management using either virt-manager or virsh, a
libvirt and QEMU reference, and troubleshooting information.
Red Hat Enterprise Linux Virtualization Security Guide: This guide provides an overview of
virtualization security technologies provided by Red Hat. Also included are recommendations for
securing hosts, guests, and shared infrastructure and resources in virtualized environments.
Red Hat Enterprise Linux Virtualization Tuning and Optimization Guide: This guide provides tips,
tricks and suggestions for making full use of virtualization performance features and options for
your systems and guest virtual machines.
Red Hat Enterprise Linux V2V Guide describes importing virtual machines from KVM, Xen and
VMware ESX/ESX(i) hypervisors to Red Hat Enterprise Virtualization and KVM managed by libvirt.
The Red Hat Enterprise Virtualization documentation suite provides information on installation,
development of applications, configuration and usage of the Red Hat Enterprise Virtualization
platform and its related products.
Red Hat Enterprise Virtualization Installation Guide: This guide describes how to prepare for and set
up a Red Hat Enterprise Virtualization environment, and how to upgrade a Red Hat Enterprise
Virtualization environment to the latest release. It also outlines how to set up hypervisors and
perform initial configuration of a Red Hat Enterprise Virtualization environment.
Red Hat Enterprise Virtualization Administration Guide: This guide describes how to configure and
administer a Red Hat Enterprise Virtualization environment after that environment has been set up
for the first time, including how to add hypervisors, storage domains, and external providers to the
environment, how to manage resources such as virtual machines, virtual disks, and templates,
and how to take and restore backups.
8
`
Chapt er 1 . Int roduct ion
Red Hat Enterprise Virtualization User Guide: This guide describes how to use the User Portal of a
Red Hat Enterprise Virtualization environment, including the functionality provided by the Basic
and Extended tabs, how to create and work with virtual machines and templates, and how to
monitor resource usage.
Red Hat Enterprise Virtualization Technical Guide: This guide describes how to use the REST API,
the Python and Java software development kits, and command-line tools specific to Red Hat
Enterprise Virtualization. It also outlines the underlying technical concepts behind Red Hat
Enterprise Virtualization.
Red Hat Enterprise Virtualization Manager Release Notes: This guide contains information on the
Red Hat Enterprise Virtualization Manager specific to the current release.
Red Hat Enterprise Virtualization Technical Notes: This guide describes the changes that have
been made made between the current release and the previous release.
Note
All of the guides for these products are available at the Red Hat Customer Portal:
https://access.redhat.com/site/documentation/
9
Red Hat Ent erprise Linux 6 .6 Bet a Virt ualizat ion Securit y Guide
Chapter 2. Host Security
2.1. Why Host Securit y Mat t ers
When deploying virtualization technologies, the security of the host should be paramount. The Red
Hat Enterprise Linux host system is responsible for managing and controlling access to the physical
devices, storage and network as well as all virtualized guests themselves. If the host system were to
be compromised, not only would the host system be vulnerable, but so would the guests and their
data.
Virtualized guests are only as secure as their host system; securing the Red Hat Enterprise Linux host
system is the first step towards ensuring a secure virtualization platform.
2.2. Host Securit y Recommended Pract ices for Red Hat Ent erprise
Linux
With host security being such a critical part of a secure virtualization infrastructure, the following
recommended practices should serve as a starting point for securing a Red Hat Enterprise Linux host
system:
Run only the services necessary to support the use and management of your guest systems. If
you need to provide additional services, such as file or print services, you should consider
running those services on a Red Hat Enterprise Linux guest.
Limit direct access to the system to only those users who have a need to manage the system.
Consider disallowing shared root access and instead use tools such as sud o to grant privileged
access to administrators based on their administrative roles.
Ensure that SELinux is configured properly for your installation and is operating in enforcing
mode. Besides being a good security practice, the advanced virtualization security functionality
provided by sVirt relies on SELinux. Refer to Chapter 4, sVirt for more information on SELinux and
sVirt.
Ensure that auditing is enabled on the host system and that libvirt is configured to emit audit
records. When auditing is enabled, libvirt will generate audit records for changes to guest
configuration as well start/stop events which help you track the guest's state. In addition to the
standard audit log inspection tools, the libvirt audit events can also be viewed using the
specialized auvirt tool.
Ensure that any remote management of the system takes place only over secured network
channels. Tools such as SSH and network protocols such as TLS or SSL provide both
authentication and data encryption to help ensure that only approved administrators can
manage the system remotely.
Ensure that the firewall is configured properly for your installation and is activated at boot. Only
those network ports needed for the use and management of the system should be allowed.
Refrain from granting guests direct access to entire disks or block devices (for example,
/d ev/sd b); instead, use partitions (for example, /d ev/sd b1) or LVM volumes for guest storage.
Ensure that staff have adequate training and knowledge in virtual environments.
10
`
Chapt er 2 . Host Securit y
Note
The objective of this guide is to explain the unique security-related challenges, vulnerabilities,
and solutions that are present in most virtualized environments, and the recommended method
of addressing them. However, there are a number of recommended practices to follow when
securing a Red Hat Enterprise Linux system that apply regardless of whether the system is a
standalone, virtualization host, or guest instance. These recommended practices include
procedures such as system updates, password security, encryption, and firewall
configuration. This information is discussed in more detail in the Red Hat Enterprise Linux
Security Guide which can be found at https://access.redhat.com/site/documentation/.
2.2.1. Special Considerations for Public Cloud Operators
Public cloud service providers are exposed to a number of security risks beyond that of the
traditional virtualization user. Virtual guest isolation, both between the host and guest as well as
between guests, is critical due to the threat of malicious guests and the requirements on customer
data confidentiality and integrity across the virtualization infrastructure.
In addition to the Red Hat Enterprise Linux virtualization recommended practices previously listed,
public cloud operators should also consider the following items:
Disallow any direct hardware access from the guest. PCI, USB, FireWire, Thunderbolt, eSATA and
other device passthrough mechanisms not only make management difficult, but often rely on the
underlying hardware to enforce separation between the guests.
Isolate the cloud operator's private management network from the customer guest network, and
customer networks from one another, so that:
the guests can not access the host systems over the network.
one customer can not access another customer's guest systems directly via the cloud
provider's internal network.
2.3. Host Securit y Recommended Pract ices for Red Hat Ent erprise
Virt ualizat ion
2.3.1. Red Hat Enterprise Virtualization Network Ports
Red Hat Enterprise Virtualization uses various network ports for management and other virtualization
features. These ports must be open for Red Hat Enterprise Linux to function as a host with Red Hat
Enterprise Virtualization. The list below covers ports and their usage by Red Hat Enterprise
Virtualization:
Incoming ICMP echo requests and outgoing ICMP echo replies must be allowed.
Port 22 (TCP) should be open for SSH access and the initial installation.
Port 161 (UDP) is required for SNMP (Simple Network Management Protocol).
Ports 5900 to 65535 (TCP) are used for guest console access.
Ports 80 or 443 (TCP), depending on the security settings on the Manager, are used by the vdsm-
reg service to communicate information about the host.
11
Red Hat Ent erprise Linux 6 .6 Bet a Virt ualizat ion Securit y Guide
Port 16514 (TLS) or port 16509 (TCP) is used to support migration communication generated by
libvirt.
Ports 49152 to 49215 (TCP) are used for migrations. Migration may use any port in this range
depending on the number of concurrent migrations occurring.
Port 54321 (TCP) is used by default, by VDSM for management, storage and inter-host
communication. This port can be modified.
Warning
Take special care to filter SNMP on port 161 (UDP) at the border of your network unless it is
absolutely necessary to externally manage devices.
12
`
Chapt er 3. Guest Securit y
Chapter 3. Guest Security
3.1. Why Guest Securit y Mat t ers
While the security of the host system is critical in ensuring the security of the guests running on the
host, it does not remove the need for properly securing the individual guest machines. All of the
security risks associated with a conventional, non-virtualized system still exist when the system is run
as a virtualized guest. Any resources accessible to the guest system, such as critical business data
or sensitive customer information, could be made vulnerable if the guest system were to be
compromised.
3.2. Guest Securit y Recommended Pract ices
All of the recommended practices for securing a Red Hat Enterprise Linux system documented in the
Red Hat Enterprise Linux Security Guide apply to conventional, non-virtualized systems as well as
systems installed as a virtualized guest. However, there are a few security practices which are of
critical importance when running guests in a virtualized environment:
With all management of the guest likely taking place remotely, ensure that the management of the
system takes place only over secured network channels. Tools such as SSH and network
protocols such as TLS or SSL provide both authentication and data encryption to ensure that
only approved administrators can manage the system remotely.
Some virtualization technologies use special guest agents or drivers to enable some
virtualization specific features. Ensure that these agents and applications are secured using the
standard Red Hat Enterprise Linux security features, e.g. SELinux.
In virtualized environments there is a greater risk of sensitive data being accessed outside the
protection boundaries of the guest system. Protect stored sensitive data using encryption tools
such as dm-crypt and G nuPG ; although special care needs to be taken to ensure the
confidentiality of the encryption keys.
13
Red Hat Ent erprise Linux 6 .6 Bet a Virt ualizat ion Securit y Guide
Chapter 4. sVirt
4.1. Int roduct ion
Since virtual machines under KVM are implemented as Linux processes, KVM leverages the standard
Linux security model to provide isolation and resource controls. The Linux kernel includes SELinux
(Security-Enhanced Linux), a project developed by the US National Security Agency to add
mandatory access control (MAC), multi-level security (MLS) and multi-category security (MCS)
through a flexible and customizable security policy. SELinux provides strict resource isolation and
confinement for processes running on top of the Linux kernel, including virtual machine processes.
The sVirt project builds upon SELinux to further facilitate virtual machine isolation and controlled
sharing. For example, fine-grained permissions could be applied to group virtual machines together
to share resources.
From a security point of view, the hypervisor is a tempting target for attackers, as a compromised
hypervisor could lead to the compromise of all virtual machines running on the host system.
Integrating SELinux into virtualization technologies helps improve hypervisor security against
malicious virtual machines trying to gain access to the host system or other virtual machines.
Refer to the following image which represents isolated guests, limiting the ability for a compromised
hypervisor (or guest) to launch further attacks, or to extend to another instance:
Figure 4 .1. Attack path isolated by SELinux
Note
For more information on SELinux, refer to Red Hat Enterprise Linux Security-Enhanced Linux at
https://access.redhat.com/site/documentation/.
4.2. SELinux and Mandat ory Access Cont rol (MAC)
Security-Enhanced Linux (SELinux) is an implementation of MAC in the Linux kernel, checking for
14
`
Chapt er 4 . sVirt
allowed operations after standard discretionary access controls (DAC) are checked. SELinux can
enforce a user-customizable security policy on running processes and their actions, including
attempts to access file system objects. Enabled by default in Red Hat Enterprise Linux, SELinux limits
the scope of potential damage that can result from the exploitation of vulnerabilities in applications
and system services, such as the hypervisor.
sVirt integrates with libvirt, a virtualization management abstraction layer, to provide a MAC
framework for virtual machines. This architecture allows all virtualization platforms supported by
libvirt and all MAC implementations supported by sVirt to interoperate.
4.3. sVirt Configurat ion
SELinux Booleans are variables that can be toggled on or off, quickly enabling or disabling features
or other special conditions. Booleans can be toggled by running either setsebo o l
boolean_name {o n| o ff} for a temporary change, or setsebo o l -P boolean_name
{o n| o ff} to make the change persistent across reboots.
The following table shows the SELinux Boolean values that affect KVM when launched by libvirt. The
current state of these booleans (on or off) can be found by running the command g etsebo o l -
a| g rep vi rt.
Table 4 .1. KVM SELinux Booleans
SELinux Boolean Description
staff_use_svirt Allow staff user to create and transition to sVirt
domains.
unprivuser_use_svirt Allow unprivileged user to create and transition
to sVirt domains.
virt_sandbox_use_audit Allow sandbox containers to send audit
messages.
virt_sandbox_use_netlink Allow sandbox containers to use netlink system
calls.
virt_sandbox_use_sys_admin Allow sandbox containers to use sys_admin
system calls, e.g. mount.
virt_transition_userdomain Allow virtual processes to run as userdomains.
virt_use_comm Allow virt to use serial/parallel communication
ports.
virt_use_execmem Allow confined virtual guests to use executable
memory and executable stack.
virt_use_fusefs Allow virt to read FUSE mounted files.
virt_use_nfs Allow virt to manage NFS mounted files.
virt_use_rawip Allow virt to interact with rawip sockets.
virt_use_samba Allow virt to manage CIFS mounted files.
virt_use_sanlock Allow confined virtual guests to interact with the
sanlock.
virt_use_usb Allow virt to use USB devices.
virt_use_xserver Allow virtual machine to interact with the X
Window System.
15
Red Hat Ent erprise Linux 6 .6 Bet a Virt ualizat ion Securit y Guide
Note
For more information on SELinux Booleans, refer to Red Hat Enterprise Linux Security Enhanced
Linux at https://access.redhat.com/site/documentation/.
4.4. sVirt Labeling
Like other services under the protection of SELinux, sVirt uses process based mechanisms, labels
and restrictions to provide extra security and control over guest instances. Labels are applied
automatically to resources on the system based on the currently running virtual machines (dynamic),
but can also be manually specified by the administrator (static), to meet any specific requirements
that may exist.
4 .4 .1. T ypes of sVirt Labels
The following table outlines the different sVirt labels that can be assigned to resources such as
virtual machine processes, image files and shared content:
Table 4 .2. sVirt Labels
Type SELinux Context Description/Effect
Virtual Machine Processes system_u:system_r:svirt_t:MCS1 MCS1 is a randomly selected
field. Currently approximately
500,000 labels are supported.
Virtual Machine Image system_u:object_r:svirt_image_t Only svirt_t processes with the
:MCS1 same MCS1 fields are able to
read/write these image files and
devices.
Virtual Machine Shared system_u:object_r:svirt_image_t All svirt_t processes are
Read/Write Content :s0 allowed to write to the
svirt_image_t:s0 files and
devices.
Virtual Machine Shared Shared system_u:object_r:svirt_content All svirt_t processes are able to
Read Only content _t:s0 read files/devices with this
label.
Virtual Machine Image system_u:object_r:virt_content_t System default label used when
:s0 an image exits. No svirt_t virtual
processes are allowed to read
files/devices with this label.
4 .4 .2. Dynamic Configuration
Dynamic label configuration is the default labeling option when using sVirt with SELinux. Refer to the
following example which demonstrates dynamic labeling:
# ps -eZ | grep qemu-kvm
system_u:system_r:svirt_t:s0:c87,c520 27950 ? 00:00:17 qemu-kvm
In this example, the q emu-kvm process has a base label of system_u: system_r: svi rt_t: s0 .
The libvirt system has generated a unique MCS label of c87,c520 for this process. The base label
16
`
Chapt er 4 . sVirt
and the MCS label are combined to form the complete security label for the process. Likewise, libvirt
takes the same MCS label and base label to form the image label. This image label is then
automatically applied to all host files that the VM is required to access, such as disk images, disk
devices, PCI devices, USB devices, and kernel/initrd files. Each process is isolated from other virtual
machines with different labels.
The following example shows the virtual machine's unique security label (with a corresponding MCS
label of c87,c520 in this case) as applied to the guest disk image file in
/var/l i b/l i bvi rt/i mag es:
# ls -lZ /var/lib/libvirt/images/*
system_u:object_r:svirt_image_t:s0:c87,c520 image1
The following example shows dynamic labeling in the XML configuration for the guest:
system_u:system_r:svirt_t:s0:c87,c520 system_u:object_r:svirt_image_t:s0:c87,c520 4 .4 .3. Dynamic Configuration with Base Labeling
To override the default base security label in dynamic mode, the
option can besystem_u:system_r:svirt_custom_t:s0 system_u:system_r:svirt_custom_t:s0:c87,c520 system_u:object_r:svirt_image_t:s0:c87,c520 system_u:system_r:svirt_custom_t:s0:c87,c520 system_u:system_r:svirt_custom_t:s0:c87,c520 Red Hat Enterprise Linux OpenStack Platform?rtification 1 0 Policy Guide en US Red Hat Enterprise Linux 7 Kernel Crash Dump Guide en US Red Hat Enterprise Linux 7 Kernel Crash Dump Guide en US Red Hat Enterprise Linux 6 High Availability?d On Overview en US Red Hat Enterprise Linux 6 High Availability?d On Overview en US Red Hat Enterprise Linux 7 High Availability?d On?ministration en US Red Hat Enterprise Linux 6 High Availability?d On Overview en US(1) Red Hat Enterprise Linux 3 Cluster Suite Release Notes en US Red Hat Enterprise Linux 6 Virtualization Security Guide en US Red Hat Enterprise Linux 7 Virtualization Security Guide en US Red Hat Enterprise Linux 6 Virtualization Security Guide en US Red Hat Enterprise Linux 5 Para virtualized Windows Drivers Guide en US Red Hat Enterprise Linux 6 Beta High Availability?d On Overview en US Red Hat Enterprise Linux 6 Virtualization Getting Started Guide en US Red Hat Enterprise Linux 6 Resource Management Guide en US Red Hat Enterprise Linux OpenStack Platform?rtification Test Suite 5 User Guide en US Red Hat Enterprise Linux OpenStack Platform?rtification Test Suite 4 User Guide en US Red Hat Enterprise Linux 6 Hypervisor?ployment Guide en US Red Hat Enterprise Linux 6 V2V Guide en US więcej podobnych podstron