Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Bot management means telling apart improper machine access and blocking it. A bot is a program that accesses a site automatically in place of a person. Some are useful, like the crawlers of search engines, while others are used for brute-force login attempts or for buying up popular products.
How does bot management work?
Picture a person at the door of a popular shop who checks whether the people lined up are separate customers or one person queuing many times. Bot management uses clues such as how often access happens, how fast, the traits of the browser, and habits in operation to judge how human the access is.
OWASP's Automated Threats to Web Applications classifies automated threats to web apps by purpose. It lists brute-force attempts against logins, tries with stolen IDs and passwords (credential stuffing), buying up popular products, and collecting page content in bulk.
The means are a combination of limits on the number of accesses (rate limiting), screens that check for a human (CAPTCHA), features of a WAF, and dedicated services. Depending on how suspicious the access is, you assign responses of different strength, such as blocking, slowing down, or asking for confirmation. Login attacks are also explained on the brute-force attack page. The free URL check looks only at what an outside visitor can see on a public page, so how bot traffic is actually handled is a matter for a consultation.
Why does bot management matter?
A bot can try faster than a person and without rest. If a login screen is targeted, guessing at passwords and tries with combinations leaked from other sites continue, which leads to account takeover.
The harm is not only takeover. It also shows up as a site that slows down when access concentrates, or as a flood of unwanted submissions to an inquiry form.
On the other hand, if you stop even the crawlers of search engines, your pages may no longer appear in search results. The center of this measure is not shutting out every bot but telling apart suspicious access whose purpose is unclear.
Related terms
- CAPTCHA: a screen that checks whether the other party is a person
- Rate limiting: a mechanism that limits how many requests are accepted in a given time
- Credential stuffing: an attack that tries leaked combinations on other sites
- WAF: a wall that stops improper traffic at the entrance
Next step
First look at your access records for the login screen and the inquiry form, and see whether many attempts happen in a short time. A limit on the number of attempts is a place to begin. The free URL check shows only what is visible from outside. If you are unsure how to build the measures, contact us.
Frequently asked questions
Should I stop every bot?
It can be better not to stop all of them. Some bots, such as search engine crawlers, help your pages appear and bring visitors. Tell apart only the suspicious access whose purpose is unclear, and subject that to limits or checks.
Does a small site need bot management?
How likely a site is to be targeted is not decided by its size alone. If you have a login screen or an inquiry form, you can start with a limit on the number of attempts and, where needed, a confirmation screen. First check your access records for suspicious activity.
Frequently asked questions
Should I stop every bot?
It can be better not to stop all of them. Some bots, such as search engine crawlers, help your pages appear and bring visitors. Tell apart only the suspicious access whose purpose is unclear, and subject that to limits or checks.
Does a small site need bot management?
How likely a site is to be targeted is not decided by its size alone. If you have a login screen or an inquiry form, you can start with a limit on the number of attempts and, where needed, a confirmation screen. First check your access records for suspicious activity.