Like other Elastic integrations, Endpoint Security can be integrated into the Elastic Agent through Fleet. Upon configuration, the integration allows the Elastic Agent to monitor for events on your host and send data to the Elastic Security app.
To configure the Endpoint Security integration on the Elastic Agent, you must have permission to use Fleet in Kibana. You must also have admin permissions in Kibana to access the Endpoints page in the Elastic Security app.
Before you beginedit
If you’re using macOS, some versions may require you to grant Full Disk Access to different kernels, system extensions, or files. Refer to requirements for Elastic Endpoint if you’re installing the Elastic Endpoint or requirements for the Endgame sensor for more information.
Add the Endpoint Security integrationedit
In Kibana, select Security → Endpoints. If this is not your first time using Elastic Security, select Management → Integrations, then search for and select Endpoint Security.
Select Add Endpoint Security on either the Endpoints page of the Elastic Security app or the Endpoint Security integration page (Management → Integrations). The integration configuration page appears.
- Configure the Endpoint Security integration with an Integration name and optional Description.
- Enter a name for the agent policy in New agent policy name. If other agent policies already exist, you can click the Existing hosts tab and select an existing policy instead. For more details on Elastic Agent configuration settings, refer to Elastic Agent policies.
- When the configuration is complete, click Save and continue.
- To complete the integration, continue to the next section to install the Elastic Agent on your hosts.
Configure and enroll the Elastic Agentedit
To configure the Elastic Agent, Endpoint Security requires enrollment through Fleet to enable the integration.
Before you add an Elastic Agent, a Fleet Server must be running. Refer to Add a Fleet Server.
Endpoint Security cannot be integrated with an Elastic Agent in Standalone mode.
Important information about Fleet Serveredit
If you are running an Elastic Stack version earlier than 7.13.0, you can skip this section.
If you have upgraded to an Elastic Stack version that includes Fleet Server 7.13.0 or newer, you will need to redeploy your agents. Review the following scenarios to ensure you take the appropriate steps.
- If you redeploy the Elastic Agent to the same machine through the Fleet application after you upgrade, a new agent will appear.
- If you want to remove the Elastic Agent entirely without transitioning to the Fleet Server, then you will need to manually uninstall the Elastic Agent on the machine. This will also uninstall the endpoint. Refer to Uninstall Elastic Agent.
- In the rare event that the Elastic Agent fails to uninstall, you might need to manually uninstall the endpoint. Refer to Uninstall an endpoint at the end of this topic.
Add the Elastic Agentedit
Go to Fleet → Agents → Add agent.
Select an agent policy for the Elastic Agent. You can select an existing custom policy, or select Create new agent policy to create a new one. For more details on Elastic Agent configuration settings, refer to Elastic Agent policies.
The selected policy should include Endpoint Security.
- Download and extract the Elastic Agent package on your host’s machine.
- Open a command-line interface and navigate to the directory where the Elastic Agent is located. Copy and run the command from Fleet for your OS to enroll and run the agent.
- After you have enrolled the Elastic Agent on your host, select Close. The host now appears on the Endpoints page in the Elastic Security app. It may take a minute or two while the Elastic Agent starts up.
For macOS, continue with these instructions to grant Elastic Endpoint the access it needs.