security - How to defend excessive login requests? -
Our team has created a web application using rubies on Rails, it is not currently restricted to users due to excessive login requests Does. We want to ignore the user's login requests for some time after several unsuccessful attempts to automatically protect the robots.
These are my questions:
-
How can one write a program or script that can make excessive requests on our website? I need this because it will help me test our web application.
-
What is the method of restricting a user who made some unsuccessful login attempts within a period? Are there underlying solutions to identify Ruby on request of a requestor and to make a request to him recently? If not, is there a common way of identifying a requestor (not specific to the Ruby on Rail) and keep track of the requester's activities? Can I identify the user with IP address or cookies or any other information that I can collect from his machine? We also expect that we can distinguish between normal users (who make a singular request) from automated robots (which often request).
Thank you!
# 1, there are several automation tools that can simulate large amounts of posting in a given URL Are there. Depending on your platform, something as simple as wget may be; Or a complex (relatively speaking) script that asks the user to post a request multiple times in succession (again, depending on the platform, it can be easy, this work can be 1 May also be based on the language of choice).
In relation to # 2, manually firing several attempts in view of the low number of the first person; In such instances, usually a session is shared (on actual Web server sessions); You should be able to track the failed login based on these session IDs, if the volume of any unsuccessful attempts breaks some thresholds. I do not know any plug-ins or gems which are special, but even if there is not one, then this solution should be simple enough to make it.
If session ID does not work, then a combination of IP and useragent is also a very safe tool, though such people who use a proxy, do not know how to do this kind of practice (Whether it is an issue or not dependent on the needs of your business).
If the attacker is malicious, you may need to block their access when using firewall rules, because they are probably going: a) use a proxy (such as IP rotation ), B) Do not use cookies during testing, and c) Play Good with No UserAgent String.
Comments
Post a Comment