Skip to content

Commit 51008d4

Browse files
feedback
1 parent 5ec1b6b commit 51008d4

File tree

2 files changed

+8
-10
lines changed

2 files changed

+8
-10
lines changed

src/content/docs/api-shield/management-and-monitoring/endpoint-labels.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ Cloudflare automatically runs risk scans every 24 hours on your saved endpoints.
7171

7272
`cf-risk-bola-enumeration`: Automatically added when an endpoint experiences successful responses with drastic differences in the number of unique elements requested by different user sessions.
7373

74-
`cf-risk-bola-pollution`: Automatically added when an endpoint experiences successful responses where parameters are found in multiple places in the request.
74+
`cf-risk-bola-pollution`: Automatically added when an endpoint experiences successful responses where parameters are found in multiple places in the request, as opposed to what is expected from the API's schema.
7575

7676
:::note
7777
Cloudflare will only add authentication labels to endpoints with successful response codes. Refer to the below table for more details.

src/content/docs/api-shield/security/bola-attack-detection.mdx

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ import { Badge } from "~/components";
1313

1414
A Broken Object Level Authorization (BOLA) attack is where an application or API fails to properly verify if a user has permission to access specific private data.
1515

16-
Bugs in the application or API allow attackers to bypass authorization checks and access sensitive information by manipulating and iterating through object identifiers
16+
Bugs in the application or API allow attackers to bypass authorization checks and access sensitive information by manipulating and iterating through object identifiers.
1717

1818
Vulnerabilities can occur at any time, including in the original application's deployment. However, changes or upgrades to authentication and authorization policies can also introduce these bugs.
1919

@@ -25,10 +25,12 @@ Cloudflare labels endpoints with BOLA risk when we detect two distinct signals c
2525

2626
This behavior may be indicative of attackers trying to confuse the API’s authorization system and bypass security controls.
2727

28-
- **Enumeration**: Cloudflare detects anomalies where one or more sessions makes successful requests to any one API endpoint changing variable values out of the norm, trying to get information from the API.
28+
- **Enumeration**: Cloudflare detects anomalies where one or more sessions makes successful requests to any one API endpoint that changes variable values trying to get information from the API.
2929

3030
:::note
3131
Sessions that have more random behavior or repetition have a higher chance of triggering an alert.
32+
33+
The BOLA enumeration label requires an endpoint to have seen at least 10,000 sessions before being eligible for outlier detection.
3234
:::
3335

3436
## Examples
@@ -49,18 +51,14 @@ Sessions that have more random behavior or repetition have a higher chance of tr
4951

5052
## Process
5153

52-
For beta customers, API Shield searches for and highlights BOLA attacks on your APIs. Cloudflare learns visitor traffic patterns over time to know when API access to specific objects is likely a Broken Object Level Authorization enumeration attack. We inform you what API endpoints are being targeted by automatically labeling them using the following risk labels:
54+
For beta customers, API Shield searches for and highlights BOLA attacks on your APIs. Cloudflare learns visitor traffic patterns over time to know when API access to specific objects is likely a BOLA enumeration attack. We inform you what API endpoints are being targeted by automatically labeling them using the following risk labels:
5355

5456
`cf-risk-bola-enumeration`: Automatically added when an endpoint experiences successful responses with drastic differences in the number of unique elements requested by different user sessions.
5557

56-
`cf-risk-bola-pollution`: Automatically added when an endpoint experiences successful responses where parameters are found in multiple places in the request.
58+
`cf-risk-bola-pollution`: Automatically added when an endpoint experiences successful responses where parameters are found in multiple places in the request, as opposed to what is expected from the API's schema.
5759

5860
If you see one of these labels on your API endpoints, check its authorization policy with your developer team to find any authorization bugs. Additionally, you can reach out to Cloudflare for a customized report about the behavior, including attacker identifiers that you can use to confirm attack reach and impact.
5961

6062
## Availability
6163

62-
BOLA attack detection is available in a closed beta. Contact your account team if you are interested in BOLA attack detection for your API.
63-
64-
## Limitations
65-
66-
The BOLA enumeration label requires an endpoint to have seen at least 10,000 sessions before being eligible for outlier detection.
64+
BOLA attack detection is available in a closed beta. Contact your account team if you are interested in BOLA attack detection for your API.

0 commit comments

Comments
 (0)