# Elastic security time zone issue

**URL:** <https://discuss.elastic.co/t/elastic-security-time-zone-issue/325915>\
**Category:** Elastic Security\
**Created:** [February 19, 2023, 2:38pm UTC](https://discuss.elastic.co/t/elastic-security-time-zone-issue/325915 "2023-02-19T14:38:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![frank\_rib](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frank_rib/32/104372_2.png) [@frank\_rib](https://discuss.elastic.co/u/frank_rib)\
**Post date:** [February 19, 2023, 2:38pm UTC](https://discuss.elastic.co/t/elastic-security-time-zone-issue/325915/1 "2023-02-19T14:38:51Z")

</div>

Hello Community,

I have an issue with the TIMEZONE in the SECURITY – ALERTS section, the logs are received in UTC+1 in Discovery and in UTC+3 in SECURITY – ALERTS.

Knowning that the timezone configured at the kibana is in UTC+1.

- Timezone Discovery (UTC)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/6/b6e4a3b5d591f0278648e1c15683b58a6efe9022.png)

- Timezone Security Alerts (UTC+3)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/e/4e58a3045640955299fababdc5294d23272b6750.png)

Please help me resolve this issue and make the time zone in UTC + 1 in the Security Alerts.

Best regards,

---

<div class="post-metadata">

**Author:** ![frank\_rib](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frank_rib/32/104372_2.png) [@frank\_rib](https://discuss.elastic.co/u/frank_rib)\
**Post date:** [February 21, 2023, 8:57am UTC](https://discuss.elastic.co/t/elastic-security-time-zone-issue/325915/2 "2023-02-21T08:57:32Z")

</div>

Hello,  
Can i find any expert to help me to resolve this issue?  
Best regards,

---

<div class="post-metadata">

**Author:** ![frank\_rib](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frank_rib/32/104372_2.png) [@frank\_rib](https://discuss.elastic.co/u/frank_rib)\
**Post date:** [February 23, 2023, 9:57pm UTC](https://discuss.elastic.co/t/elastic-security-time-zone-issue/325915/3 "2023-02-23T21:57:39Z")

</div>

Hello,

Does anyone have any idea about this issue?

Regards,

---

<div class="post-metadata">

**Author:** ![frank\_rib](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frank_rib/32/104372_2.png) [@frank\_rib](https://discuss.elastic.co/u/frank_rib)\
**Post date:** [February 27, 2023, 11:35am UTC](https://discuss.elastic.co/t/elastic-security-time-zone-issue/325915/4 "2023-02-27T11:35:28Z")

</div>

Hello Community,

Has anyone encountered the same problem before?

Regards,

---

<div class="post-metadata">

**Author:** ![wsouza](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wsouza/32/92547_2.png) [@wsouza](https://discuss.elastic.co/u/wsouza)\
**Post date:** [February 27, 2023, 12:43pm UTC](https://discuss.elastic.co/t/elastic-security-time-zone-issue/325915/5 "2023-02-27T12:43:34Z")

</div>

Take a look at the docs and check the "event created" and "event.ingest" fields. May be some data source is coming with different timezone.

Check in Kibana under Stack management \> Advanced settings how your time zone shown in the figure is configured.

 ![print](https://us1.discourse-cdn.com/elastic/original/3X/a/5/a5a7937081983ac862537778dbf713389b2dac8b.png)

---

<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:** [March 27, 2023, 12:44pm UTC](https://discuss.elastic.co/t/elastic-security-time-zone-issue/325915/6 "2023-03-27T12:44:12Z")

</div>

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