SecureCloud 3.5 Key Management Server Web Console Help

Collapse AllExpand All
  • accounts
    • See user management
  • activation code [1]
  • administration tasks [1]
    • configuring date format and time zone [1]
    • configuring Deep Security [1]
    • configuring session timeout [1]
    • setting up notifications [1]
  • Advanced Encryption Standard (AES) [1]
  • authentication [1]
  • auto-detection [1]
  • automatic provisioning [1]
  • auto-provisioning [1]
  • cloning
    • adding clones to the Inventory [1]
  • cloning devices [1]
  • Configuration and Provisioning Wizard for Microsoft Windows [1]
  • Configuration Tool [1] [2] [3] [4]
  • credential keys, in Amazon EC2 [1]
  • Deep Security, configuring [1]
  • Default Policy [1] [2] [3]
  • device cloning [1]
  • device keys [1]
  • devices
    • and Inventory screen [1]
    • checking status [1]
    • creating a RAID array [1]
    • deleting from the Inventory [1]
    • deleting RAID arrays [1]
    • managing [1]
    • manually encrypting [1]
    • restoring [1]
  • encryption
    • boot volume [1]
    • full disk [1]
  • encryption key requests [1] [2]
    • approving manually [1]
  • Google Authenticator [1] [2] [3]
  • integrity checking [1] [2] [3] [4]
    • running on-demand [1]
    • scheduling [1]
  • inventory [1]
  • Inventory
    • deleting devices [1]
  • Inventory screen [1]
  • Key Exporter tool [1]
  • Key Management Server [1] [2] [3] [4]
  • license
    • See product license
  • logs [1]
    • archive time limit [1]
    • managing [1]
    • running a query [1]
    • types of [1]
  • Managed Service Provider (MSP) [1]
  • multi-factor authentication (MFA) [1] [2] [3] [4]
    • activating MFA accounts [1]
    • managing [1]
    • MFA backup codes [1]
    • system requirements for MFA devices [1]
    • unregistering MFA devices [1]
    • using MFA backup codes [1]
  • new features [1]
  • notifications, setting up [1]
  • password, changing [1]
  • policies [1] [2] [3]
    • and rules [1]
    • creating [1]
    • editing or deleting [1]
    • See also Default Policy
  • product license [1] [2]
  • provisioning
    • See encryption
  • provisioning, automatic [1]
  • provisioning pass phrase [1]
  • RAID array
  • reports [1]
    • generating [1]
    • managing [1]
    • types of [1]
    • viewing archived reports [1]
  • restoring devices [1]
  • rules [1]
  • SecureCloud
    • about [1]
    • components [1]
    • getting started [1]
    • Key Management Server [1]
    • SecureCloud Agent [1]
    • Web Console [1]
  • SecureCloud Agent [1] [2]
    • configuring [1] [2]
    • encrypting devices [1]
    • installing [1]
    • installing on Linux [1] [2]
    • installing on Linux with a custom kernel [1]
    • installing on Microsoft Windows [1]
    • system requirements [1]
    • troubleshooting migration [1]
    • updating to a newer version [1]
  • SecureCloud Hosted Service [1]
  • Software as a Service (SaaS) [1]
  • subscribing
    • activating a subscription [1]
    • SecureCloud Hosted Service [1]
    • via a Managed Service Provider (MSP) [1] [2]
    • via Trend Micro [1] [2]
  • user management [1]
    • adding user accounts [1]
    • changing your password [1]
    • user rules [1]
  • Web Console [1]
    • logging on [1] [2] [3] [4]
    • logging on using an MFA code [1]
    • logging on via the Licensing Management Platform [1]
    • logging on with an MFA backup code [1]
    • troubleshooting log on issues [1]
    • troubleshooting MFA log on issues [1]

Installing the SecureCloud Agent with a Custom Linux Kernel Parent topic

Before you begin

All dependent packages must be present in the system before installing the SecureCloud Agent on a Linux system. During installation, the SecureCloud Agent installer attempts to download all the dependent packages from the repository. If the installer cannot download the necessary packages, administrators must download them manually from the Internet or a trusted network repository.
The dependent packages for the SecureCloud Agent on a Linux system are:

Dependent Packages for Linux

Platform Dependency
All
  • gcc
  • curl
  • make
  • gawk
CentOS/RHEL 5.x
  • kernel-headers
  • kernel-xen-devel
CentOS/RHEL 6.x
  • kernel-headers
  • kernel-xen-devel
Ubuntu
linux-headers
SUSE 11
SUSE 11 requires that you specify the information below. This information is based on the 2.6.32.46 version of the Linux kernel. 
$yast --install kernel-source
$cp /boot/symvers-2.6.32.46-0.3-ec2.gz /usr/src/linux/Module.symvers.gz
$gunzip /usr/src/linux/Module.symvers.gz
$cd /usr/src/linux
$make cloneconfig
$make modules_prepare
$ln -s /usr/src/linux /lib/modules/2.6.32.46-0.3-ec2/build
$rpm -ivh scagent-3.5.0.xxx.rpm

Procedure

  1. To customize kernels, identify the kernel source and set the path using one of the following commands:
    • $ln -s /usr/src/linux /lib/modules/<kernel-version>/build #SUSE
    • $ln -s /usr/src/kernels/<kernel-version> /lib/modules/<kernel-version>/build #CentOS/RHEL
    • $ln -s /usr/src/linux-source-<kernel-version> /lib/modules/<kernel-version>/build #Ubuntu
    If using a custom Linux kernel, the complete kernel source is required because the Trend Micro Encryption Module driver cannot function without the proper kernel source.
  2. Ensure thata soft link exists to the kernel source path. For example:/lib/modules/<kernel version>/build
    Use the following command to check the kernel version: uname -r
  3. To compile the kernel, refer to the instructions in the Linux user guide.