Supported security hardening grades

Last Updated : Apr 13, 2026 |
Prolog information
Metadata
Keywords:
Communication Manager supports standard and hardened installation types from a security point of view. Standard installation is the default installation, and no additional action is required to set up this configuration. The table shows the hardening commands needed to set up a hardened installation.
The two security hardening grades are compared in the following table.
Security attribute
Standard installation
Hardened installation
Hardening command
VM Configuration Hardening
See point 1 in the Note at the bottom of the table.
Y
Y
N
Password Management
Y
Y (more restrictive)
setCMHardening
Login and Session Management
Y
Y (more restrictive)
setCMHardening
System and Application Files Hardening
Y
Y (more restrictive)
setCMHardening
Certificate Management
Y
Y
SMI Certificates Pages
Support TLS
Y
Y
SMI Server Access Page
FIPS 140-2 Compliance
N
Y
fips_mode
Multifactor Authentication (PIV and CAC support)
N
Y
Manual Configuration Required
See point 2 in the Note at the bottom of the table.
SELinux Enabled
N
Y
setCMSelinux
Linux OS Auditing
N
Y
setCMAuditd
AIDE (File Tampering Prevention)
N
Y
setCMAide
Clam AV anti-virus
See point 3 in the Note at the bottom of the table.
N
Y
setCMClamav
Note:
  1. VM ESXi VMX file hardening is applied as part of Solution Deployment Manager (SDM) deployment.
  2. Requires root access to configure the use of authorized keys from “Smart” card for user accounts.
  3. Requires compatible Security Service Pack with latest Communication Manager release.( release 7.1 is still in market. Security Service Pack earlier to the mentioned release will not work for the feature).
For detailed information on the associated commands, see the Maintenance Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers.