Skip to content

Commit 4b30c45

Browse files
Update account takeover detections documentation (#26516)
* Update account takeover detections documentation Added note about endpoint labels for Account Takeover Detections Ids. * Update src/content/docs/bots/additional-configurations/detection-ids/account-takeover-detections.mdx --------- Co-authored-by: Patricia Santa Ana <[email protected]>
1 parent e5c3371 commit 4b30c45

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/content/docs/bots/additional-configurations/detection-ids/account-takeover-detections.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,10 @@ Using the detection IDs below, you can detect and mitigate account takeover atta
1515
| `201326593` | Observes all login traffic to the zone. |
1616
| `201326598` | Sets a dynamic threshold based on the normal traffic that is unique to the zone.<br /><br /> When the ID matches a login failure, Bot Management sets the [bot score](/bots/concepts/bot-score/) to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
1717

18+
:::note
19+
Not all login endpoints are automatically detected. However, endpoints [labeled](/api-shield/management-and-monitoring/endpoint-labels/#categories) as `cf-log-in` will be evaluated for account takeover detection IDs.
20+
:::
21+
1822
## Challenges for account takeover detections
1923

2024
Cloudflare's [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge-recommended) can limit brute-force attacks on your login endpoints.

0 commit comments

Comments
 (0)