From 833a13fef4009f6a18b522a55f0c215f972ef823 Mon Sep 17 00:00:00 2001 From: zeinjaber <69680657+zeinjaber@users.noreply.github.com> Date: Tue, 24 Sep 2024 19:11:17 +0300 Subject: [PATCH] Update detection-ids.mdx Removing extra * --- src/content/docs/bots/concepts/detection-ids.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/bots/concepts/detection-ids.mdx b/src/content/docs/bots/concepts/detection-ids.mdx index 88743d3c5e46c3..c4946d5de4c810 100644 --- a/src/content/docs/bots/concepts/detection-ids.mdx +++ b/src/content/docs/bots/concepts/detection-ids.mdx @@ -92,7 +92,7 @@ Cloudflare's [Managed Challenge](/waf/reference/cloudflare-challenges/) can limi To access account takeover detections: 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain. -2. Go to ***Security** > **WAF**. +2. Go to **Security** > **WAF**. 3. Under **Custom Rules**, select **Create rule**. 4. Fill out the form using **Bot Detection IDs** along with other necessary information. 5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule. @@ -117,4 +117,4 @@ To use rate limiting rules with account takeover detections: :::note The rule can be enhanced with Leaked Credential Checks. Refer to the [WAF documentation](/waf/detections/leaked-credentials/) for more information on how to include leaked credentials and account takeover detections in a rate limiting rule. -::: \ No newline at end of file +:::