# Preventing/identifying credit card breach in elastic using SIEM

**URL:** <https://discuss.elastic.co/t/preventing-identifying-credit-card-breach-in-elastic-using-siem/337014>\
**Category:** SIEM\
**Created:** [June 27, 2023, 3:45pm UTC](https://discuss.elastic.co/t/preventing-identifying-credit-card-breach-in-elastic-using-siem/337014 "2023-06-27T15:45:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![searchwithme](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/searchwithme/32/137075_2.png) [@searchwithme](https://discuss.elastic.co/u/searchwithme)\
**Post date:** [June 27, 2023, 3:45pm UTC](https://discuss.elastic.co/t/preventing-identifying-credit-card-breach-in-elastic-using-siem/337014/1 "2023-06-27T15:45:09Z")

</div>

Hi!

I see elastic has a rich array of security features (SIEM, security analytics, endpoint detection, etc).

Is there a way to identify/detect if credit card details were crawled by hackers for online transactions?

Given that all logs are ingested into elasticsearch, how can this "malicious event" be identified as a threat by elastic?

Could someone please share insights?

---

<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:** [July 25, 2023, 3:46pm UTC](https://discuss.elastic.co/t/preventing-identifying-credit-card-breach-in-elastic-using-siem/337014/2 "2023-07-25T15:46:08Z")

</div>

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