SMB login attempt - server initiated

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

SMB login attempt - server initiated

L4 Transporter

Is it normal for DC trying o reach systems on 445 and 139

I get bruteforce alerts for only 1 system, even though DC is trying to reach almost every system in that zone on 445/smb

 image.png

 

1 accepted solution

Accepted Solutions

If you disable user identification on the public wifi zone you will lose User-ID visibility within that zone but that won't necessarily stop the agent from attempting to enumerate systems within that zone.  You can either implement a security policy rule to deny/drop User-ID agent traffic to this zone or you could simply exempt the IP address for this system within the IP exemption list within the User-ID agent as seen here.

 

https://live.paloaltonetworks.com/t5/Management-Articles/How-the-User-ID-Agent-Include-Exclude-List-...

View solution in original post

5 REPLIES 5

L5 Sessionator

The PA UserAgent (user-id agent I assume) appears to be running on this DC.  Is the agent performing enumeration of user to IP mappings from this DC?  Do you have WMI probing enabled?  That could explain the behavior you are seeing.

Yes PA user agent is installed

WMI probes not enabled.

Is the "victim" host a domain controller or other Windows server which the Agent would attempt to access to enumerate users?  I suspect this is normal behavior yet there could be underlying login issues between the DC and 10.4.190.66 (victim).  If 10.4.190.66 is not needed for enumeration purposes you could add it to the IP exemption list within the Agent.

Victim system is in publicly accessible wifi, and most likely seems to be windows.

Would disabling user identification on this zone stop this, or should i disable this traffic from DC's into this zone.

If you disable user identification on the public wifi zone you will lose User-ID visibility within that zone but that won't necessarily stop the agent from attempting to enumerate systems within that zone.  You can either implement a security policy rule to deny/drop User-ID agent traffic to this zone or you could simply exempt the IP address for this system within the IP exemption list within the User-ID agent as seen here.

 

https://live.paloaltonetworks.com/t5/Management-Articles/How-the-User-ID-Agent-Include-Exclude-List-...

  • 1 accepted solution
  • 11162 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!