# How to use event.category intrusion\_detection

**URL:** <https://discuss.elastic.co/t/how-to-use-event-category-intrusion-detection/327316>\
**Category:** Beats\
**Tags:** auditbeat\
**Created:** [March 9, 2023, 1:52am UTC](https://discuss.elastic.co/t/how-to-use-event-category-intrusion-detection/327316 "2023-03-09T01:52:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jjacksonrkk](https://avatars.discourse-cdn.com/v4/letter/j/e8c25b/32.png) [@jjacksonrkk](https://discuss.elastic.co/u/jjacksonrkk)\
**Post date:** [March 9, 2023, 1:52am UTC](https://discuss.elastic.co/t/how-to-use-event-category-intrusion-detection/327316/1 "2023-03-09T01:52:46Z")

</div>

How can I activate intrusion\_detection in auditbeat event.category?

When debugging, log.logger occurs as a publisher and the event.category includes intrusion\_detection, but when the daemon service is run, the intrusion\_detection is not output and only the process is output.

```auto
#### intrusion_detection[edit](https://github.com/elastic/ecs/edit/8.4/docs/fields/field-values.asciidoc)

Relating to intrusion detections from IDS/IPS systems and functions, both network and host-based. Use this category to visualize and analyze intrusion detection alerts from systems such as Snort, Suricata, and Palo Alto threat detections.

**Expected event types for category intrusion_detection:**

allowed, denied, info
https://www.elastic.co/guide/en/ecs/8.4/ecs-allowed-values-event-category.html

```

---

<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:** [April 6, 2023, 3:53am UTC](https://discuss.elastic.co/t/how-to-use-event-category-intrusion-detection/327316/2 "2023-04-06T03:53:01Z")

</div>

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