# Excessive 4673 events due to chromium

**URL:** <https://discuss.elastic.co/t/excessive-4673-events-due-to-chromium/340643>\
**Category:** Elastic Agent\
**Tags:** elastic-stack-alerting\
**Created:** [August 11, 2023, 2:20pm UTC](https://discuss.elastic.co/t/excessive-4673-events-due-to-chromium/340643 "2023-08-11T14:20:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nightingale\_John](https://avatars.discourse-cdn.com/v4/letter/n/ecccb3/32.png) [@Nightingale\_John](https://discuss.elastic.co/u/Nightingale_John)\
**Post date:** [August 11, 2023, 2:20pm UTC](https://discuss.elastic.co/t/excessive-4673-events-due-to-chromium/340643/1 "2023-08-11T14:20:45Z")

</div>

Hi All,

We're seeing excessive 4673 events which appear to be linked to the chromium issue causing failures against SeProfileSingleProcessPrivilege; this appears to be well know by Microsoft.

Ideally we would like to exclude these specific events from being ingested by the ElasticAgent; specifically:  
event.code: 4673  
winlog.event\_data.PrivilegeList: SeProfileSingleProcessPrivilege  
event.outcome: failure

Has anyone else done this, or can anyone suggest the best approach?

Thanks  
J

---

<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:** [September 8, 2023, 2:21pm UTC](https://discuss.elastic.co/t/excessive-4673-events-due-to-chromium/340643/2 "2023-09-08T14:21:24Z")

</div>

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