You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/changelog/casb/2024-11-22-cloud-data-extraction-aws.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,6 @@ import { Render } from "~/components";
8
8
9
9
You can now use CASB to find security misconfigurations in your AWS cloud environment using [Data Loss Prevention](/cloudflare-one/data-loss-prevention/).
10
10
11
-
You can also [connect your AWS compute account](/cloudflare-one/applications/casb/casb-integrations/aws-s3/#compute-account) to extract and scan your S3 buckets for sensitive data while avoiding egress fees. CASB will scan any objects that exist in the bucket at the time of configuration.
11
+
You can also [connect your AWS compute account](/cloudflare-one/integrations/cloud-and-saas/aws-s3/#compute-account) to extract and scan your S3 buckets for sensitive data while avoiding egress fees. CASB will scan any objects that exist in the bucket at the time of configuration.
Copy file name to clipboardExpand all lines: src/content/changelog/casb/2025-08-26-casb-ai-integrations.mdx
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,15 +11,16 @@ date: 2025-08-26 16:00:00 UTC
11
11
12
12
13
13
### Key capabilities
14
-
-**Agentless connections** — connect ChatGPT, Claude, and Gemini tenants via API; no endpoint software required
15
-
-**Posture management** — detect insecure settings and misconfigurations that could lead to data exposure
16
-
-**DLP detection** — identify sensitive data in uploaded chat attachments or files
17
-
-**GenAI-specific insights** — surface risks unique to each provider’s capabilities
14
+
15
+
-**Agentless connections** — connect ChatGPT, Claude, and Gemini tenants via API; no endpoint software required
16
+
-**Posture management** — detect insecure settings and misconfigurations that could lead to data exposure
17
+
-**DLP detection** — identify sensitive data in uploaded chat attachments or files
18
+
-**GenAI-specific insights** — surface risks unique to each provider’s capabilities
Copy file name to clipboardExpand all lines: src/content/changelog/email-security-cf1/2025-04-01-casb-email-security.mdx
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,17 +4,17 @@ description: Get two free CASB integrations with your Email Security subscriptio
4
4
date: 2025-04-01T23:22:49Z
5
5
---
6
6
7
-
With Email Security, you get two free CASB integrations.
7
+
With Email Security, you get two free CASB integrations.
8
8
9
-
Use one SaaS integration for Email Security to sync with your directory of users, take actions on delivered emails, automatically provide EMLs for reclassification requests for clean emails, discover CASB findings and more.
9
+
Use one SaaS integration for Email Security to sync with your directory of users, take actions on delivered emails, automatically provide EMLs for reclassification requests for clean emails, discover CASB findings and more.
10
10
11
-
With the other integration, you can have a separate SaaS integration for CASB findings for another SaaS provider.
11
+
With the other integration, you can have a separate SaaS integration for CASB findings for another SaaS provider.
12
12
13
-
Refer to [Add an integration](/cloudflare-one/applications/casb/#add-an-integration) to learn more about this feature.
13
+
Refer to [Add an integration](/cloudflare-one/integrations/cloud-and-saas/#add-an-integration) to learn more about this feature.
Copy file name to clipboardExpand all lines: src/content/docs/analytics/analytics-integrations/sentinel.mdx
+286-5Lines changed: 286 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,294 @@ sidebar:
6
6
7
7
---
8
8
9
-
Microsoft has developed a Cloudflare connector that allows their customers to integrate [Cloudflare Logs](/logs/) with Microsoft Sentinel.
9
+
import { Details } from"~/components";
10
10
11
-
## How it works
11
+
Cloudflare has integrations with Microsoft Sentinel to make analyzing your Cloudflare data easier and in a centralized space. Cloudflare has two versions of this connector available. We recommend utilizing the latest Codeless Connector integration as it provides easier setup, cost management, and integrates with [Sentinel Data Lake](https://learn.microsoft.com/en-us/azure/sentinel/datalake/sentinel-lake-overview).
12
12
13
-
[Logpush](/logs/logpush/logpush-job/enable-destinations/azure/) sends logs from Cloudflare to Azure Blob Storage. From there, the Cloudflare connector, a Microsoft function, ingests these logs into Azure Log Analytics Workspace, making them available for monitoring and analysis in Microsoft Sentinel.
13
+
**[Sentinel CCF Solution](https://marketplace.microsoft.com/en-us/product/azure-application/cloudflare.azure-sentinel-solution-cloudflare-ccf?tab=Overview)** (recommended): The Codeless Connector Framework (CCF) provides partners, advanced users, and developers the ability to create custom connectors for ingesting data to Microsoft Sentinel.
**[Sentinel Function Based Connector](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/cloudflare.cloudflare_sentinel?tab=Overview)**: The Cloudflare connector for Microsoft Sentinel uses [Azure Functions](https://azure.microsoft.com/en-us/products/functions) to process security logs from Cloudflare's Logpush service and ingest them directly into the SIEM platform.
16
+
17
+
This guide provides clear, step-by-step instructions for integrating Cloudflare logs with the new CCF connector for Microsoft Sentinel using Azure Blob Storage. By following these steps, you will be able to securely collect, store, and analyse your Cloudflare logs within Microsoft Sentinel, enhancing your organisation's security monitoring and incident response capabilities.
18
+
19
+
## Step 1: Prerequisites
20
+
21
+
- Azure Subscription with permission to create and manage resources (Contributor/Owner role recommended).
22
+
- Microsoft Sentinel Workspace already set up in your Azure environment.
23
+
- Azure Storage Account with a Blob container for storing Cloudflare logs.
24
+
- Cloudflare Account with access to the domain whose logs you wish to export, and permission to configure Logpush jobs.
25
+
26
+
## Step 2: Set up a logpush job
27
+
28
+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
29
+
2. Go to **Analytics** > **Logs** and select **Logpush**.
30
+
3. Select **Create Logpush Job**. Choose the log type you want to export (for example, **HTTP requests**).
31
+
4. For the destination, select **Azure Blob Storage**.
32
+
5. Enter your Azure Blob Storage details:
33
+
- SAS Token (Shared Access Signature)
34
+
35
+
To generate a SAS token from the Azure portal, first navigate to your storage account. Under the **Data Storage** section, select **Containers** and choose the relevant container. Within the settings, locate and select **Shared access signature**. Configure the required permissions, such as `write` and `create`, and specify the start and expiration dates for the token. Once configured, generate the SAS token accordingly.
36
+
6. Save and activate the Logpush job.
37
+
38
+
For complete details, refer to the [Cloudflare Logpush to Azure documentation](/logs/logpush/logpush-job/enable-destinations/azure/).
39
+
40
+
## Step 3: Configure Azure and deploy the Data Connector in Microsoft Sentinel
41
+
42
+
1. Log in to the Azure Portal and go to your **Microsoft Sentinel** workspace.
43
+
2. Select **Content Hub** in the navigation bar and search for **Cloudflare**.
44
+
3. Select the **Cloudflare** solution from the results.
45
+
4. Select **Install** in the right pane.
46
+
5. In your **Sentinel workspace**, go to **Data connectors**.
47
+
6. Search for the **Cloudflare connector** (may appear as **Cloudflare (using Azure Blob Storage)**).
When configuring the Cloudflare data connector, you will need to provide the following information:
55
+
56
+
- Blob container URL
57
+
58
+
To obtain the container URL within your Azure storage account, access the Azure Portal and navigate to your storage account. Under **Data Storage**, select **Containers**, then choose the relevant container receiving logs from Cloudflare. The container properties section will display the URL link.
59
+
60
+
- Resource group name for the storage account
61
+
- Storage account location
62
+
- Subscription ID
63
+
- Event grid topic name (only if reconfiguring; not needed for initial setup)
64
+
65
+
After entering all information, select **Connect**.
66
+
67
+
Ensure all fields are correctly filled to enable seamless log ingestion.
By following these steps, you have successfully integrated Cloudflare logs with Microsoft Sentinel using Azure Blob Storage. This integration enables advanced security analytics and incident response capabilities for your Cloudflare-protected environments. If you encounter issues, review each configuration step, check permissions, and review Microsoft's official documentation.
We support the following fields to be utilized within the Sentinel Connectors (CCF & Function based). You can push all log fields to Azure using our logpush function as described in [Enable Microsoft Azure](/logs/logpush/logpush-job/enable-destinations/azure/) documentation.
[Microsoft Data Lake Overview](https://learn.microsoft.com/en-us/azure/sentinel/datalake/sentinel-lake-overview)<br />
297
+
[About the CCF Platform](https://learn.microsoft.com/en-us/azure/sentinel/create-codeless-connector)
16
298
17
-
For more details, refer to the Microsoft documentation [Cloudflare connector for Microsoft Sentinel](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/cloudflare.cloudflare_sentinel).
Copy file name to clipboardExpand all lines: src/content/docs/china-network/faq.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,14 +52,14 @@ The JD Cloud network is proxying content inside of China for customers who have
52
52
53
53
## Products and features
54
54
55
-
### How does IPv6 work on the Cloudflare China Network?
55
+
### How does IPv6 work on China Network?
56
56
57
-
All sites hosted in Mainland China must have IPv6 enabled. The Cloudflare China Network feature automatically enables IPv6 for domains to fulfill this requirement and it is not possible to disable it. According to internal testing, IPv6 connections in Mainland China are more reliable and offer better latency.
57
+
All sites hosted in Mainland China must have IPv6 enabled. China Network automatically enables IPv6 for domains to fulfill this requirement and it is not possible to disable it. According to internal testing, IPv6 connections in Mainland China are more reliable and offer better latency.
58
58
59
59
### Is Turnstile available in Mainland China?
60
60
61
61
[Turnstile](/turnstile/) is not supported in Mainland China. Therefore, both China Network zones and [global zones](/fundamentals/concepts/accounts-and-zones/#zones) with users visiting your content from Mainland China may experience issues with Turnstile.
62
62
63
-
## Is Cloudflare Pages available in Mainland China?
63
+
###Is Pages available in Mainland China?
64
64
65
-
[Cloudflare Pages](/pages/) is not available in Mainland China due to pages.dev certificate not residing within Mainland China. However, Pages from a global zone may potentially be extended into Mainland China.
65
+
[Pages](/pages/) is not available in Mainland China due to pages.dev certificate not residing within Mainland China. However, Pages from a global zone may potentially be extended into Mainland China.
0 commit comments