Elastic Defend integration on Windows Servers influences results from system.process dataset

I have added the Elastic Defend integration to Policies for Windows and Linux Servers today.

After activation, the system.process dataset on the Windows servers doesn't report elastic-agent.exe as a running process any longer, while this is still OK on the Linux servers.

As soon as I remove the integration from the Windows servers, elastic-agent.exe is reported as a running process again.

The Elastic Agent is version 8.6.2 and the Elastic Defend integration is version 8.6.1.

Is there a configuration setting necessary, which I haven't seen so far, or could this be a bug in the integration?

Kind regards,

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.