Skip to content

Commit 4c55057

Browse files
committed
Rest of initial entries for backfilling
1 parent 9561615 commit 4c55057

File tree

13 files changed

+168
-63
lines changed

13 files changed

+168
-63
lines changed
94.9 KB
Loading
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
title: Generate customized terrform files for building cloud network on-ramps
3+
description: Download cloud onramp terraform
4+
date: 2024-12-05T11:00:00Z
5+
---
6+
7+
import { Render } from "~/components";
8+
9+
You can now generate customized terraform files for building cloud network on-ramps to [Magic WAN](/magic-wan/).
10+
11+
[Magic Cloud](/magic-cloud-networking/) can scan and discover existing network resources and generate the required terraform files to automate cloud resource deployment using their existing infrastructure-as-code workflows for cloud automation.
12+
13+
<Render file="terraform-setup-scenarios" product="magic-cloud-networking" />
14+
15+
For more details, refer to [Set up with Terraform](/magic-cloud-networking/cloud-on-ramps/#set-up-with-terraform).
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: Search for custom rules using rule name and/or ID
3+
description: New UI improvements for Magic Firewall
4+
date: 2024-10-02T11:00:00Z
5+
---
6+
7+
The Magic Firewall dashboard now allows you to search custom rules using the rule name and/or ID.
8+
9+
1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
10+
2. Go to **Analytics & Logs** > **Network Analytics**.
11+
3. Select **Magic Firewall**.
12+
4. Find **Packet sample log**.
13+
5. Search for **Rule ID**.
14+
15+
{/* Insert screenshot here */}
16+
17+
Additionally, the rule ID URL link has been added to Network Analytics.
18+
19+
For more details, refer to [Add rules](/magic-firewall/how-to/add-rules/).
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Try out Magic Network Monitoring
3+
description: The free version of Magic Network Monitoring is available to all customers
4+
date: 2024-09-24T11:00:00Z
5+
---
6+
7+
The free version of Magic Network Monitoring (MNM) is now available to everyone with a Cloudflare account by default.
8+
9+
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com), and select your account.
10+
2. Go to **Analytics & Logs** > **Magic Monitoring**.
11+
12+
![Try out the free version of Magic Network Monitoring](~/assets/images/changelog/magic-network-monitoring/get-started.png)
13+
14+
For more details, refer to the [Get started guide](/magic-network-monitoring/get-started/).
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: Configure your Magic WAN Connector to connect via static IP assigment
3+
description: Local console access for bootstrapping Magic WAN Connector
4+
date: 2025-02-14T11:00:00Z
5+
---
6+
7+
You can now locally configure your [Magic WAN Connector](/magic-wan/configuration/connector/) to work in a static IP configuration.
8+
9+
This local method does not require having access to a DHCP Internet connection. However, it does require being comfortable with using tools to access the serial port on Magic WAN Connector as well as using a serial terminal client to access the Connector's environment.
10+
11+
For more details, refer to [WAN with a static IP address](/magic-wan/configuration/connector/configure-hardware-connector/#bootstrap-via-serial-console).
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Establish BGP peering over Direct CNI circuits
3+
description: BGP support for Cloudflare Network Interconnect (CNI)
4+
date: 2024-12-17T11:00:00Z
5+
products:
6+
- magic-transit
7+
- magic-wan
8+
---
9+
10+
import { Render } from "~/components";
11+
12+
<Render file="bgp-peering-overview" product="network-interconnect" />
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: Exchange user risk scores with Okta
3+
description: Okta risk exchange
4+
date: 2024-06-17T11:00:00Z
5+
---
6+
7+
import { Render } from "~/components";
8+
9+
Beyond the controls in [Zero Trust](/cloudflare-one/), you can now [exchange user risk scores](/cloudflare-one/insights/risk-score/#send-risk-score-to-okta) with Okta to inform SSO-level policies.
10+
11+
<Render file="send-risk-scores-okta" product="cloudflare-one" />

src/content/docs/cloudflare-one/insights/risk-score.mdx

Lines changed: 3 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ head:
88
content: User risk score
99
---
1010

11+
import { Render } from "~/components";
12+
1113
:::note
1214

1315
Only available on Enterprise plans.
@@ -38,22 +40,7 @@ If required, you can reset risk scores for specific users. Once reset, users wil
3840

3941
In addition to controls in Zero Trust, Okta users can send risk scores to Okta to apply SSO-level policies.
4042

41-
First, configure Zero Trust to send user risk scores to Okta.
42-
43-
1. Set up the [Okta SSO integration](/cloudflare-one/identity/idp-integration/okta/).
44-
2. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Authentication**.
45-
3. In **Login methods**, locate your Okta integration and select **Edit**.
46-
4. Turn on **Send risk score to Okta**.
47-
5. Select **Save**.
48-
6. Upon saving, Zero Trust will display the well-known URL for your organization. Copy the value.
49-
50-
Next, configure Okta to receive your risk scores.
51-
52-
1. On your Okta admin dashboard, go to **Security** > **Device Integrations**.
53-
2. Go to **Receive shared signals**, then select **Create stream**.
54-
3. Name your integration. In **Set up integration with**, choose _Well-known URL_.
55-
4. In **Well-known URL**, enter the well-known URL value provided by Zero Trust.
56-
5. Select **Create**.
43+
<Render file="send-risk-scores-okta" />
5744

5845
For more information on configuring user risk score within Okta, refer to the [Okta documentation](https://help.okta.com/oie/en-us/content/topics/itp/overview.htm).
5946

src/content/docs/network-interconnect/express-cni/bgp-peering.mdx

Lines changed: 2 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,6 @@ sidebar:
55
title: BGP peering
66
---
77

8-
Magic WAN and Magic Transit customers can use the Cloudflare dashboard to configure and manage BGP peering between their networks and their Magic routing table when using a Direct CNI on-ramp.
8+
import { Render } from "~/components";
99

10-
Using BGP peering with a CNI allows customers to:
11-
- Automate the process of adding or removing networks and subnets.
12-
- Take advantage of failure detection and session recovery features.
13-
14-
With this functionality, customers can:
15-
- Establish an eBGP session between their devices and the Magic WAN / Magic Transit service when connected via CNI.
16-
- Secure the session by MD5 authentication to prevent misconfigurations.
17-
- Exchange routes dynamically between their devices and their Magic routing table.
18-
19-
Refer to [Magic WAN BGP peering](/magic-wan/configuration/manually/how-to/bgp-peering/) or [Magic Transit BGP peering](/magic-transit/how-to/bgp-peering/) to learn more about this feature and how to set it up.
10+
<Render file="bgp-peering-overview" />
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
{}
3+
---
4+
5+
First, configure Zero Trust to send user risk scores to Okta.
6+
7+
1. Set up the [Okta SSO integration](/cloudflare-one/identity/idp-integration/okta/).
8+
2. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Authentication**.
9+
3. In **Login methods**, locate your Okta integration and select **Edit**.
10+
4. Turn on **Send risk score to Okta**.
11+
5. Select **Save**.
12+
6. Upon saving, Zero Trust will display the well-known URL for your organization. Copy the value.
13+
14+
Next, configure Okta to receive your risk scores.
15+
16+
1. On your Okta admin dashboard, go to **Security** > **Device Integrations**.
17+
2. Go to **Receive shared signals**, then select **Create stream**.
18+
3. Name your integration. In **Set up integration with**, choose _Well-known URL_.
19+
4. In **Well-known URL**, enter the well-known URL value provided by Zero Trust.
20+
5. Select **Create**.

0 commit comments

Comments
 (0)