Summary
This article explains the limitations of Securecloud.
Details
SecureCloud Agent
Previous versions of the SecureCloud Agent (3.0 or older) cannot provision new devices or update the inventory on the Key Management Server.
Operating System
If a previous version of the SecureCloud Agent (3.0 or older) is installed on a machine that uses an operating system that is no longer supported in version 3.5, Trend Micro does not recommend upgrading the SecureCloud Agent to 3.5.
Volume Encryption
Volume encryption has the following limitations and requirements:
- GPT-formatted partitioned devices are not supported.
- Devices that have a file system without a partition are not supported.
- The device on which the SecureCloud Agent is installed is not supported.
Boot Volume Encryption
Boot volume encryption has the following limitations and requirements:
- A Dynamic Host Configuration Protocol (DHCP) server and a Domain Name System (DNS) must be available at boot time so the SecureCloud Agent can connect to the Key Management Server to retrieve the boot volume key.
- Boot volume encryption is only available for machines running the Linux operating system if the boot partition has more than 30MB free space (100MB recommended).
- Boot volume encryption is not available for machines running the Linux operating system in AWS EC2 cloud environments.
- Boot volume encryption is only available for machines running the Linux operating system if disks are managed using a logical volume manager (LVM).
- Boot volume encryption is only available for machines running the Linux operating system if there is a boot partition (/boot).
- Boot volume encryption is not available for machines running the Linux operating system if the kernel version is under 2.6.18.
- Boot volume encryption is only available for machines running the Windows operating system if the SecureCloud Agent is installed in the boot volume (C: drive).
- It is not possible to uninstall the SecureCloud Agent if the root volume is encrypted.
