|
| 1 | +--- |
| 2 | +title: New API Posture Management for API Shield |
| 3 | +description: Monitor for API-specific threats and risks with Posture Management for API Shield |
| 4 | +date: 2025-03-18T11:00:00Z |
| 5 | +--- |
| 6 | + |
| 7 | +Now, API Shield **automatically** labels your API inventory with API-specific risks so that you can track and manage risks to your APIs. |
| 8 | + |
| 9 | +View these risks in [Endpoint Management](/api-shield/management-and-monitoring/) by label: |
| 10 | + |
| 11 | + |
| 12 | + |
| 13 | + ...or in [Security Center Insights](/security-center/security-insights/): |
| 14 | + |
| 15 | + |
| 16 | + |
| 17 | +API Shield will scan for risks on your API inventory daily. Here are the new risks we're scanning for and automatically labelling: |
| 18 | + |
| 19 | +- **cf-risk-sensitive**: applied if the customer is subscribed to the [sensitive data detection ruleset](/waf/managed-rules/reference/sensitive-data-detection/) and the WAF detects sensitive data returned on an endpoint in the last seven days. |
| 20 | +- **cf-risk-missing-auth**: applied if the customer has configured a session ID and no successful requests to the endpoint contain the session ID. |
| 21 | +- **cf-risk-mixed-auth**: applied if the customer has configured a session ID and some successful requests to the endpoint contain the session ID while some lack the session ID. |
| 22 | +- **cf-risk-missing-schema**: added when a learned schema is available for an endpoint that has no active schema. |
| 23 | +- **cf-risk-error-anomaly**: added when an endpoint experiences a recent increase in response errors over the last 24 hours. |
| 24 | +- **cf-risk-latency-anomaly**: added when an endpoint experiences a recent increase in response latency over the last 24 hours. |
| 25 | +- **cf-risk-size-anomaly**: added when an endpoint experiences a spike in response body size over the last 24 hours. |
| 26 | + |
| 27 | +In addition, API Shield has two new 'beta' scans for **Broken Object Level Authorization (BOLA) attacks**. If you're in the beta, you will see the following two labels when API Shield suspects an endpoint is suffering from a BOLA vulnerability: |
| 28 | + |
| 29 | + - **cf-risk-bola-enumeration**: added when an endpoint experiences successful responses with drastic differences in the number of unique elements requested by different user sessions. |
| 30 | + - **cf-risk-bola-pollution**: added when an endpoint experiences successful responses where parameters are found in multiple places in the request. |
| 31 | + |
| 32 | +We are currently accepting more customers into our beta. Contact your account team if you are interested in BOLA attack detection for your API. |
| 33 | + |
| 34 | +Refer to the [blog post](https://blog.cloudflare.com/cloudflare-security-posture-management/) for more information about Cloudflare's expanded posture management capabilities. |
0 commit comments