Skip to content

Commit 83dd909

Browse files
authentication posture
1 parent 341e423 commit 83dd909

File tree

1 file changed

+22
-9
lines changed

1 file changed

+22
-9
lines changed

src/content/docs/api-shield/security/authentication-posture.mdx

Lines changed: 22 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,13 @@ sidebar:
77

88
---
99

10-
import { GlossaryTooltip, Render, Steps } from "~/components"
10+
import { GlossaryTooltip, Render, Steps, Tabs, TabItem } from "~/components"
1111

1212
Authentication Posture helps users identify authentication misconfigurations for APIs and alerts of their presence.
1313

1414
For example, a security team member may believe that their API hosted at `/api/v1/users` and `/api/v1/orders` are guarded by the fact that only authenticated users can interact with the endpoints. However, bugs in origin API authentication policies may lead to broken authentication vulnerabilities. Authentication Posture with API Shield details the authentication status of successful requests to your API endpoints, alerting to potential misconfigurations.
1515

16-
Consider a typical e-commerce application. Users can browse items and prices without being logged in. However, to retrieve order details with the `GET /api/v1/orders/{order_id}` endpoint, this example application requires users to log in to their account and pass the subsequent Authorization HTTP header in all requests. Cloudflare will alert via [Security Center Insights](/security-center/security-insights/) and [Endpoint Management labels](/api-shield/management-and-monitoring/endpoint-labels/) if successful requests are sent to the `GET /api/v1/orders/{order_id}` endpoint or any other endpoint without authentication when <GlossaryTooltip term="session identifier">session identifiers</GlossaryTooltip> are configured.
16+
Consider a typical e-commerce application. Users can browse items and prices without being logged in. However, to retrieve order details with the `GET /api/v1/orders/{order_id}` endpoint, this example application requires users to log in to their account and pass the subsequent Authorization HTTP header in all requests. Cloudflare will alert via [Security Center Insights](/security-center/security-insights/) and [Endpoint labels](/api-shield/management-and-monitoring/endpoint-labels/) if successful requests are sent to the `GET /api/v1/orders/{order_id}` endpoint or any other endpoint without authentication when <GlossaryTooltip term="session identifier">session identifiers</GlossaryTooltip> are configured.
1717

1818
## Process
1919

@@ -23,13 +23,26 @@ After configuring [session identifiers](/api-shield/get-started/#session-identif
2323

2424
### Examine an endpoint's authentication details
2525

26-
<Steps>
27-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
28-
2. Go to **Security** > **API Shield** > **Endpoint Management**.
29-
3. Filter Endpoint Management by the `cf-risk-missing-auth` or `cf-risk-mixed-auth` labels.
30-
4. Select an endpoint to see its authentication posture details on the endpoint details page.
31-
5. Choose between the 24-hour and 7-day view options, and note any authentication changes over time.
32-
</Steps>
26+
<Tabs syncKey="dashNewNav">
27+
<TabItem label="Old dashboard">
28+
<Steps>
29+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
30+
2. Go to **Security** > **API Shield** > **Endpoint Management**.
31+
3. Filter Endpoint Management by the `cf-risk-missing-auth` or `cf-risk-mixed-auth` labels.
32+
4. Select an endpoint to see its authentication posture details on the endpoint details page.
33+
5. Choose between the 24-hour and 7-day view options, and note any authentication changes over time.
34+
</Steps>
35+
</TabItem>
36+
<TabItem label="New dashboard" icon="rocket">
37+
<Steps>
38+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
39+
2. Go to **Security** > **Web assets** > **Endpoints**.
40+
3. Filter your endpoints by the `cf-risk-missing-auth` or `cf-risk-mixed-auth` labels.
41+
4. Select an endpoint to see its authentication posture details on the endpoint details page.
42+
5. Choose between the 24-hour and 7-day view options, and note any authentication changes over time.
43+
</Steps>
44+
</TabItem>
45+
</Tabs>
3346

3447
The main authentication widget displays how many successful requests over the last seven days had session identifiers included with them, and which identifiers were included with the traffic.
3548

0 commit comments

Comments
 (0)