cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Who Me Too'd this topic

HELP - I have a hacker trying to use SPECIFIC users to get into my VPN service

L0 Member

The pattern is they try nonsense users such as "cisco" and I block their IP they come from, but they always come back. I am getting frequent attempts with various other users, but they seem to come back within an hour of me blocking their IPs.

I need a rule that immediately blocks the user, potentially one that could add to a dynamic IP list discouraging return visits, BUT I'd be HAPPY if the user tries with "cisco" is rejected and the connection dropped. My Policy contains the users, but I'm afraid the timing is off since this isn't a "Connection" policy, but a reaction policy. 

Who Me Too'd this topic