Manage your Defenders
The Manage Defender page helps you efficiently manage all aspects of your Defender deployments.
On the Manage Defenders page, you can carry out essential tasks such as:
For each Defender that you have deployed, the Manage Defender page displays the following information, including:
Host: The host where the Defender is installed
Version: The version of the Defender that is running
Cluster: The cluster where the Defender is running
Account ID: The cloud Account ID associated with the Defender
Type: The type of Defender
Connection Status: The current connection status
Messages: Notifications, such as when an upgrade to the Defender is available
Collections: The collection (a logical grouping of your organization’s assets) where the defender is running
Actions: Available actions such as restarting, deleting, or upgrading the Defender, and viewing/downloading the Defender logs
Deploying the Defender
To deploy and configure specific Defender instances, choose from the following list of topics:
Understanding Defenders
Host Defender
App-Embedded Defender
Runtime Restart Scenarios for Defenders
You can expect a runtime restart in the following scenarios:
When a Defender starts.
When a Defender stops.
When you add the first blocking rule.
When you remove the last blocking rule.
When a Defender upgrades because the Defender restarts.
When Defender restarts in Openshift Kubernetes clusters, nodes may become NotReady. The nodes come back online after the kubelet restart is complete.
Last updated
Was this helpful?