# Breached Password & Blocked Account events are not visible in user logs

**URL:** <https://community.auth0.com/t/breached-password-blocked-account-events-are-not-visible-in-user-logs/94971>\
**Category:** Get Help\
**Tags:** attack-protection, brute-force-protection\
**Created:** [November 23, 2022, 8:47am UTC](https://community.auth0.com/t/breached-password-blocked-account-events-are-not-visible-in-user-logs/94971 "2022-11-23T08:47:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Artur](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/artur/32/33801_2.png) [@Artur](https://community.auth0.com/u/Artur)\
**Post date:** [November 23, 2022, 8:47am UTC](https://community.auth0.com/t/breached-password-blocked-account-events-are-not-visible-in-user-logs/94971/1 "2022-11-23T08:47:49Z")

</div>

Hello,  
I noticed that whenever we have an event of Blocked Account (limit\_wc) or Breached Password (pwd\_leak) they are not visible in the User logs in the User Management.  
I think the reason is that those events are missing `user_id` value, even though they have `user_name` which is an existing user email.

Can this be fixed?

---

<div class="post-metadata">

**Author:** ![lihua.zhang](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/lihua.zhang/32/39683_2.png) [@lihua.zhang](https://community.auth0.com/u/lihua.zhang)\
**Post date:** [November 28, 2022, 10:21pm UTC](https://community.auth0.com/t/breached-password-blocked-account-events-are-not-visible-in-user-logs/94971/4 "2022-11-28T22:21:00Z")

</div>

Hi @Artur ,

I noticed that the same query was raised in a Support ticket recently. The following is the answer provided by our Product Support Team. Hope it can be helpful to other folks in our community.

* * *

Brute Force Protection blocks are managed **independently of users** , tracked via the user-submitted identifier: email, username, or phone number.

For example, if a user fails 5 login attempts with the email address “[example@mail.com](mailto:example@mail.com)”, we store something like the below in an “Anomaly Detection” database :

```auto
{
"block_type": "limit_wc",
"identifier": "[example@email.com](mailto:example@email.com)"
}

```

All other Attack Protection features, like Breached Password (pwd\_leak), work in a similar fashion. So it is expected that there is no user\_id value in the logs, hence when you check the logs for a specific user, you won’t see the Attack Protection logs since those are filtered by user\_id, not by identifier.

* * *

If the feature of having a user\_id associated with the logs (when the user exists) so that you can also see the Attack protection logs associated with a user is important to you, please communicate with our Product team directly via the [feedback](https://auth0.com/feedback) page. Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [December 12, 2022, 10:21pm UTC](https://community.auth0.com/t/breached-password-blocked-account-events-are-not-visible-in-user-logs/94971/5 "2022-12-12T22:21:15Z")

</div>

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