Important
There are two versions of IAM. If the URL you use to access the IAM UI ends with
fireeye.com, this document pertains to you. If the URL you use to access the IAM UI ends withtrellix.com, see the Trellix IAM Guide for information regarding IAM.
Task | Information | Done |
|---|---|---|
Verify that the customer ID on the appliance matches the ID in the IAM Web UI. |
| |
Standalone appliances: Prevent the appliance from automatically connecting to the Helix Enterprise-enabled cloud Central Management System appliance (if any). | Run the See Preventing connections to a cloud Central Management appliance. | |
Enable Helix Enterprise mode on each appliance. | Run the Run the See Enabling Helix Mode. | |
Central Management System-connected appliances: Ensure that alerts and health statistics are streamed directly to Helix Enterprise and not through the Helix Enterprise-enabled Central Management System appliance. | Run the Run the Run the See Sending alerts and health status directly from appliances. | |
Configure the HelixConnect Client on each appliance. | The HelixConnect Client is enabled automatically when Helix Enterprise mode is enabled, but additional steps may be required. | |
If your appliances use an HTTP proxy for outbound communication: Enable the appliances to communicate with Helix Enterprise through the proxy. | Run the | |
Configure which alerts should trigger email notifications from Helix Enterprise. Otherwise, you could be overwhelmed by notifications, especially if you push prior alerts as described in Verification. |
| |
Email Security — Server appliances only: Add the Helix Enterprise sender address to the Allowed List on the appliance. Otherwise, additional Email Security — Server analysis will be performed on malicious links that might be included in Helix Enterprise email notifications. |
|