2 ms·
1) Increase delays between failed login attempts. Not sure if by rate limiting it's limiting # of attempts per second alone. 2) Consider (if possible) assign
by j45 8y ago
1) Increase delays between failed login attempts. Not sure if by rate limiting it's limiting # of attempts per second alone.
2) Consider (if possible) assigning unique login urls for each user, company, group, etc so not all users access login from same URL.
3) Implement 2 factor authentication
4) To attempt chipping away at their install base, log the IP's of failed login attempts, identify top offenders and report to a few places:
- look up IP addresses on ARIN.net, and an automated email sent to the abuse contact email on file for each IP address with supporting proof. A similar approach is likely used for reaching torrent downloaders.
For botnet/hijacked devices this may cause some issues for the end user but maybe it's good for them to know their device may be compromised. If you're being hit with some VPN/TOR IP's..
https://whois.arin.net/ui/advanced.jsp https://whois.arin.net/ui/advanced.jsp
- Submit IP's to blacklists if not already there.
5) There should be a service that helps identify if you are being visited via VPN service/TOR IP, perhaps that could be a flag for you as well, or deny outright.