Best practices for securing virtual machines
To significantly decrease the risk of your virtual machines (VM) being infected with malicious code and used as attack vectors to infect your host system, you can increase the security of your systems by using a variety of methods.
On the guest side:
- Secure the virtual machine as if it was a physical machine. The specific methods available to enhance security depend on the guest operating system (OS).
If your VM is running RHEL 10, see Securing RHEL 10 for detailed instructions on improving the security of your guest system.
On the host side:
- When managing VMs remotely, use cryptographic utilities such as SSH and network protocols such as SSL for connecting to the VMs.
- Ensure SELinux is in Enforcing mode:
# getenforceEnforcingIf SELinux is disabled or in Permissive mode, see the Using SELinux document for instructions on activating Enforcing mode.
Note SELinux Enforcing mode also enables the sVirt RHEL 10 feature. This is a set of specialized SELinux booleans for virtualization, which can be manually adjusted for fine-grained VM security management.
- Use VMs with Secure Boot:
Secure Boot ensures that a VM is running a cryptographically signed OS. This helps prevent attacks against the guest OS and improves the protection for the host OS.
Secure Boot can only be applied when installing a Linux VM that uses UEFI firmware on an AMD64, Intel 64, or ARM 64 host. For instructions, see Creating a Secure Boot virtual machine.
- Do not use
qemu-*commands, such asqemu-kvm.QEMU is an essential component of the virtualization architecture in RHEL 10, but it is difficult to manage manually, and improper QEMU configurations may cause security vulnerabilities. Therefore, using most
qemu-*commands is not supported by Red Hat. Instead, use libvirt utilities, such asvirsh,virt-install, andvirt-xml, as these orchestrate QEMU according to the best practices.Note, however, that the
qemu-imgutility is supported for management of virtual disk images.