# Elastic Defend Degraded - Configure Network Events

**URL:** <https://discuss.elastic.co/t/elastic-defend-degraded-configure-network-events/344297>\
**Category:** Elastic Security\
**Created:** [October 3, 2023, 8:49am UTC](https://discuss.elastic.co/t/elastic-defend-degraded-configure-network-events/344297 "2023-10-03T08:49:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![GKre](https://avatars.discourse-cdn.com/v4/letter/g/ecae2f/32.png) [@GKre](https://discuss.elastic.co/u/GKre)\
**Post date:** [October 3, 2023, 8:49am UTC](https://discuss.elastic.co/t/elastic-defend-degraded-configure-network-events/344297/1 "2023-10-03T08:49:29Z")

</div>

Hi there,  
i rolled out elastic defend to my kali linux vm. On this machine the Agend is degraded with Elastic Defend showing a problem "configure network events".

> {"@timestamp":"2023-09-30T10:41:44.190134275Z","agent":{"id":"8a32fc53-b229-46ea-9418-7e877894bdb0","type":"endpoint"},"ecs":{"version":"1.11.0"},"log":{"level":"info","origin":{"file":{"line":639,"name":"Response.cpp"}}},"message":"Response.cpp:639 Setting behavior\_protection to failure because of configure\_network\_events status","process":{"pid":614291,"thread":{"id":614300}}}  
> Guess there's a problem to attach to the relevant sources?

---

<div class="post-metadata">

**Author:** ![Norrie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/norrie/32/122814_2.png) [@Norrie](https://discuss.elastic.co/u/Norrie)\
**Post date:** [October 3, 2023, 7:29pm UTC](https://discuss.elastic.co/t/elastic-defend-degraded-configure-network-events/344297/2 "2023-10-03T19:29:43Z")

</div>

@GKre thanks for reaching out and sharing the issue you are seeing. Are you able to supply some more details about the Kali VM you are running? The output of the following would provide us with a good starting point.

```auto
# uname -a 

```

Can you also share the version of the Elastic stack you are running as well as the version of Elastic Defend?

---

<div class="post-metadata">

**Author:** ![GKre](https://avatars.discourse-cdn.com/v4/letter/g/ecae2f/32.png) [@GKre](https://discuss.elastic.co/u/GKre)\
**Post date:** [October 3, 2023, 11:56pm UTC](https://discuss.elastic.co/t/elastic-defend-degraded-configure-network-events/344297/3 "2023-10-03T23:56:33Z")

</div>

yes of course - i also have log files but i do not know how to share them with this community.

uname -a  
Linux kali 6.5.0-kali1-amd64 #1 SMP PREEMPT\_DYNAMIC Debian 6.5.3-1kali1 (2023-09-19) x86\_64 GNU/Linux

I am running 8.10.1 and Defend is on 8.10.2

---

<div class="post-metadata">

**Author:** ![Michal\_Stanek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michal_stanek/32/77245_2.png) [@Michal\_Stanek](https://discuss.elastic.co/u/Michal_Stanek)\
**Post date:** [October 4, 2023, 12:39am UTC](https://discuss.elastic.co/t/elastic-defend-degraded-configure-network-events/344297/4 "2023-10-04T00:39:24Z")

</div>

Hi,

This is related to changes in the network stack in the latest Linux kernel (6.5 and onward) which some of our probes were incompatible with. This issue is fixed now and will roll out in the new 8.11 and also 8.10.3 I believe.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 1, 2023, 12:39am UTC](https://discuss.elastic.co/t/elastic-defend-degraded-configure-network-events/344297/5 "2023-11-01T00:39:53Z")

</div>

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