High Availability Deployment and SecureXCisco SecureX threat response Integration

Configuring High Availability requires two identical devices that are connected to each other through a dedicated failover link. The devices form an active/standby pair where the active device passes traffic. The standby device does not pass traffic, but synchronizes configuration and other state information from the active device. When the active device fails, the standby device takes over and helps to keep your network operational.

The following describes the guidelines for integrating Firepower Threat Defense High Availability deployment with SecureXCisco SecureX threat response.

• To integrate Firepower Threat Defense High Availability or cluster deployment with SSE, you must integrate all peers with SSE.

• SSE integration requires all Firepower Threat Defense devices in the High Availability deployment to have connectivity to the internet.

• When integrating an active/standby FMC deployment with SecureXCisco SecureX threat response, you must integrate the active peer with SecureXCisco SecureX threat response.

• If you promote the standby FMC peer to active role, the SecureXCisco SecureX threat response configuration gets transferred between the active and standby peers. The SecureXCisco SecureX threat response ribbon continues to appear in both active and standby peers.

• If you break FMC High Availability deployment, both the peers remain integrated with SecureXCisco SecureX threat response.

See the FTD and FMC online help for more information about configuring and managing a High Availability deployment.