diff --git a/src/content/docs/cloudflare-one/applications/scan-apps/casb-dlp.mdx b/src/content/docs/cloudflare-one/applications/scan-apps/casb-dlp.mdx index 5cff76a3514b48..2bae559081d8c8 100644 --- a/src/content/docs/cloudflare-one/applications/scan-apps/casb-dlp.mdx +++ b/src/content/docs/cloudflare-one/applications/scan-apps/casb-dlp.mdx @@ -3,21 +3,15 @@ pcx_content_type: concept title: Scan for sensitive data sidebar: order: 3 - --- -import { Render } from "~/components" +import { Render } from "~/components"; :::note - - -Requires Cloudflare CASB and Cloudflare DLP. - - +Requires Cloudflare SaaS & Cloud Security and Cloudflare DLP. ::: -You can use [Cloudflare Data Loss Prevention (DLP)](/cloudflare-one/policies/data-loss-prevention/) to discover if files stored in your SaaS application contain sensitive data. -To perform DLP scans in a SaaS app, first configure a DLP profile with the data patterns you want to detect, then enable those profiles in a CASB integration. +You can use [Cloudflare Data Loss Prevention (DLP)](/cloudflare-one/policies/data-loss-prevention/) to discover if files stored in your SaaS or cloud application contain sensitive data. To perform DLP scans in an application, first configure a DLP profile with the data patterns you want to detect, then enable those profiles in a SaaS & Cloud Security integration. ## Supported integrations @@ -31,41 +25,41 @@ You may either use DLP profiles predefined by Cloudflare, or create your own cus -Your DLP profile is now ready to use with CASB. +Your DLP profile is now ready to use with SaaS & Cloud Security. ### Build a custom profile -Your DLP profile is now ready to use with CASB. +Your DLP profile is now ready to use with SaaS & Cloud Security. For more information, refer to [Configure a DLP profile](/cloudflare-one/policies/data-loss-prevention/dlp-profiles/). -## Enable DLP scans in CASB +## Enable DLP scans in SaaS & Cloud Security ### Add a new integration -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **CASB** > **Integrations**. +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **SaaS & Cloud Security** > **Integrations**. 2. Select **Add integration** and choose a [supported integration](#supported-integrations). 3. During the setup process, you will be prompted to select DLP profiles for the integration. 4. Select **Save integration**. -CASB will scan every publicly accessible file in the integration for text that matches the DLP profile. The initial scan may take up to a few hours to complete. +SaaS & Cloud Security will scan every publicly accessible file in the integration for text that matches the DLP profile. The initial scan may take up to a few hours to complete. ### Modify an existing integration -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **CASB** > **Integrations**. +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **SaaS & Cloud Security** > **Integrations**. 2. Choose a [supported integration](#supported-integrations) and select **Configure**. 3. Under **DLP profiles**, select the profiles that you want the integration to scan for. 4. Select **Save integration**. -If you enable a DLP profile from the **Manage integrations** page, CASB will only scan publicly accessible files that have had a modification event since enabling the DLP profile. Modification events include changes to the following attributes: +If you enable a DLP profile from the **Manage integrations** page, SaaS & Cloud Security will only scan publicly accessible files that have had a modification event since enabling the DLP profile. Modification events include changes to the following attributes: -* Contents of the file -* Name of the file -* Visibility of the file (only if changed to publicly accessible) -* Owner of the file -* Location of the file (for example, moved to a different folder) +- Contents of the file +- Name of the file +- Visibility of the file (only if changed to publicly accessible) +- Owner of the file +- Location of the file (for example, moved to a different folder) In order to scan historical data, you must enable the DLP profile during the [integration setup flow](#add-a-new-integration). @@ -73,5 +67,5 @@ In order to scan historical data, you must enable the DLP profile during the [in DLP will only scan: -* [Text-based files](/cloudflare-one/policies/data-loss-prevention/#supported-file-types) such as documents, spreadsheets, and PDFs. Images are not supported. -* Files ≤ 100 MB. +- [Text-based files](/cloudflare-one/policies/data-loss-prevention/#supported-file-types) such as documents, spreadsheets, and PDFs. Images are not supported. +- Files less than or equal to 100 MB in size. diff --git a/src/content/docs/cloudflare-one/applications/scan-apps/casb-integrations/aws-s3.mdx b/src/content/docs/cloudflare-one/applications/scan-apps/casb-integrations/aws-s3.mdx index a9c2cf5502534b..77bcd9c65f4081 100644 --- a/src/content/docs/cloudflare-one/applications/scan-apps/casb-integrations/aws-s3.mdx +++ b/src/content/docs/cloudflare-one/applications/scan-apps/casb-integrations/aws-s3.mdx @@ -11,10 +11,6 @@ import { Render } from "~/components"; params={{ one: "Amazon Web Services (AWS) S3", two: "AWS account" }} /> -:::note -The CASB integration for AWS S3 only supports posture-related findings. -::: - ## Integration prerequisites - An AWS account using AWS S3 (Simple Storage Service) diff --git a/src/content/docs/cloudflare-one/applications/scan-apps/index.mdx b/src/content/docs/cloudflare-one/applications/scan-apps/index.mdx index c935c7974ec4eb..77983e13a87f0c 100644 --- a/src/content/docs/cloudflare-one/applications/scan-apps/index.mdx +++ b/src/content/docs/cloudflare-one/applications/scan-apps/index.mdx @@ -1,6 +1,6 @@ --- pcx_content_type: how-to -title: Scan SaaS applications +title: Scan SaaS and cloud applications sidebar: order: 3 --- @@ -10,11 +10,11 @@ import { GlossaryTooltip, Render } from "~/components"; :::note[Availability] Available for all Zero Trust users. -Free users can configure up to two CASB integrations. You must upgrade to an Enterprise plan to view the details of an individual finding instance. +Free users can configure up to two integrations. You must upgrade to an Enterprise plan to view the details of an individual finding instance. ::: -Cloudflare's API-driven Cloud Access Security Broker (CASB) scans SaaS applications for misconfigurations, unauthorized user activity, shadow IT, and other data security issues that can occur after a user has successfully logged in. +Cloudflare's API-driven SaaS & Cloud Security (previously Cloudflare CASB) scans SaaS and cloud applications for misconfigurations, unauthorized user activity, shadow IT, and other data security issues that can occur after a user has successfully logged in. -## Manage CASB integrations +## Manage integrations diff --git a/src/content/partials/cloudflare-one/casb/manage-integrations.mdx b/src/content/partials/cloudflare-one/casb/manage-integrations.mdx index 9c8badd91e60e6..78260fd2bc1352 100644 --- a/src/content/partials/cloudflare-one/casb/manage-integrations.mdx +++ b/src/content/partials/cloudflare-one/casb/manage-integrations.mdx @@ -1,27 +1,26 @@ --- {} - --- -When you integrate a third-party SaaS application with Cloudflare CASB, you allow CASB to make API calls to the application and read relevant data on your behalf. The CASB integration permissions are read-only and follow the least privileged model. In other words, only the minimum access required to perform a scan is granted. +When you integrate a third-party SaaS or cloud application with Cloudflare SaaS & Cloud Security, you allow Zero Trust to make API calls to the application and read relevant data on your behalf. The SaaS & Cloud Security integration permissions are read-only and follow the least privileged model. In other words, only the minimum access required to perform a scan is granted. ### Prerequisites -Before you can integrate a SaaS application with CASB, your SaaS account must meet certain requirements. To view the prerequisites and permissions for your application, refer to its [integration guide](/cloudflare-one/applications/scan-apps/casb-integrations/). +Before you can integrate an application with SaaS & Cloud Security, your account for the application must meet certain requirements. To view the prerequisites and permissions for your application, refer to its [integration guide](/cloudflare-one/applications/scan-apps/casb-integrations/). ### Add an integration -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **CASB** > **Integrations**. -2. Select **Add integration**. +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **SaaS & Cloud Security** > **Overview** or **Settings** > **Integrations**. +2. Select **Add an integration**. 3. Browse the available SaaS integrations and select the application you would like to add. 4. Follow the step-by-step integration instructions in the UI. 5. To run your first scan, select **Save integration**. You will be redirected to the [Findings page](/cloudflare-one/applications/scan-apps/manage-findings/) to see an in-depth listing of issues found. -After the first scan, CASB will automatically scan your application on a frequent basis to keep up with any changes. Due to each application having their own set of requirements, scan intervals will vary, but the frequency is typically between every 1 hour and every 24 hours. +After the first scan, SaaS & Cloud Security will automatically scan your application on a frequent basis to keep up with any changes. Due to each application having their own set of requirements, scan intervals will vary, but the frequency is typically between every 1 hour and every 24 hours. ### Pause an integration -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **CASB** > **Integrations**. +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **SaaS & Cloud Security** > **Integrations**. 2. Find the integration you would like to pause and select **Manage**. 3. To stop scanning the application, turn off **Scan findings**. @@ -30,13 +29,9 @@ You can resume application scanning at any time by turning on **Scan findings**. ### Delete an integration :::caution - - When you delete an integration, all keys and OAuth data will be deleted. This means you cannot restore a deleted integration or its scanned data. - - ::: -1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **CASB** > **Integrations**. +1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **SaaS & Cloud Security** > **Integrations**. 2. Find the integration you would like to delete and select **Manage**. 3. Select **Delete**. diff --git a/src/content/partials/cloudflare-one/data-loss-prevention/custom-profile.mdx b/src/content/partials/cloudflare-one/data-loss-prevention/custom-profile.mdx index 03caaf926a9adc..b06a061b2b6bb7 100644 --- a/src/content/partials/cloudflare-one/data-loss-prevention/custom-profile.mdx +++ b/src/content/partials/cloudflare-one/data-loss-prevention/custom-profile.mdx @@ -1,35 +1,25 @@ --- {} - --- -import { Details } from "~/components" +import { Details } from "~/components"; 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DLP** > **DLP Profiles**. - 2. Select **Create profile**. - 3. Enter a name and optional description for the profile. - 4. Add custom or existing detection entries. -
1. Select **Add custom entry** and give it a name. - 2. In **Value**, enter a regular expression (or regex) that defines the text pattern you want to detect. For example, `test\d\d` will detect the word `test` followed by two digits. - - * Regular expressions are written in Rust. We recommend validating your regex with [Rustexp](https://rustexp.lpil.uk/). - * DLP detects UTF-8 characters, which can be up to 4 bytes each. Custom text pattern detections are limited to 1024 bytes in length. - * DLP does not support regular expressions with `+` or `*` operators because they are prone to exceeding the length limit. For example, the regex pattern `a+` can detect an infinite number of `a` characters. We recommend using `a{min,max}` instead, such as `a{1,1024}`. - + - Regular expressions are written in Rust. We recommend validating your regex with [Rustexp](https://rustexp.lpil.uk/). + - DLP detects UTF-8 characters, which can be up to 4 bytes each. Custom text pattern detections are limited to 1024 bytes in length. + - DLP does not support regular expressions with `+` or `*` operators because they are prone to exceeding the length limit. For example, the regex pattern `a+` can detect an infinite number of `a` characters. We recommend using `a{min,max}` instead, such as `a{1,1024}`. 3. To save the detection entry, select **Done**. -
-
Existing entries include [predefined detection entries](/cloudflare-one/policies/data-loss-prevention/dlp-profiles/predefined-profiles/) and [DLP datasets](/cloudflare-one/policies/data-loss-prevention/datasets/). @@ -38,9 +28,7 @@ import { Details } from "~/components" 2. Choose which entries you want to add, then select **Confirm**. 3. To save the detection entry, select **Done**. -
5. (Optional) Configure [**Advanced settings**](/cloudflare-one/policies/data-loss-prevention/dlp-profiles/advanced-settings/) for the profile. - 6. Select **Save profile**. diff --git a/src/content/partials/cloudflare-one/data-loss-prevention/predefined-profile.mdx b/src/content/partials/cloudflare-one/data-loss-prevention/predefined-profile.mdx index 850bc2eb764325..a42d468f38d4d9 100644 --- a/src/content/partials/cloudflare-one/data-loss-prevention/predefined-profile.mdx +++ b/src/content/partials/cloudflare-one/data-loss-prevention/predefined-profile.mdx @@ -4,5 +4,5 @@ 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **DLP** > **DLP Profiles**. 2. Choose a [predefined profile](/cloudflare-one/policies/data-loss-prevention/dlp-profiles/predefined-profiles/) and select **Configure**. -3. Enable one or more **Detection entries** according to your preferences. The DLP Profile matches using the OR logical operator — if multiple entries are enabled, your data needs to match only one of the entries. +3. Enable one or more **Detection entries** according to your preferences. The DLP Profile matches using the OR logical operator -- if multiple entries are enabled, your data needs to match only one of the entries. 4. Select **Save profile**.