Skip to content

Commit d7e6772

Browse files
authored
[CF1] ELI5 on CASB docs (#29703)
* [CF1] Fix CASB docs: grammar, navigation path, and terminology inconsistencies - Fix subject-verb agreement in casb-dlp.mdx ('contains' -> 'contain') - Align troubleshoot navigation path to canonical 'Cloud & SaaS findings > Integrations' - Align toggle label to 'Scan for findings' per manage-integrations partial - Replace undocumented 'Suppress' action with cross-link to ignore/hide workflow - Apply same fixes to duplicate troubleshoot file in integrations folder * [CF1] Improve CASB docs clarity from ELI5 review - Split long CASB intro sentence and explain 'API-driven' inline (index.mdx) - Add DLP profile parenthetical definition (casb-dlp.mdx) - Add caution callout for full-scan vs incremental-scan distinction (casb-dlp.mdx) - Rephrase ambiguous Java/R minimum size limitation (casb-dlp.mdx) - Add OCR cross-link to clarify that CASB does not scan images but DLP does via Gateway (casb-dlp.mdx) - Add parenthetical for 'data at rest' (manage-findings.mdx) - Add ignore vs hide comparison before procedures (manage-findings.mdx) - Clarify Failed vs Rejected remediation statuses (manage-findings.mdx) - Rewrite Gateway policy intro to bridge CASB-to-Gateway concept (manage-findings.mdx) - Add finding ID location hint (troubleshoot-casb.mdx) * Removing outdated limitation
1 parent 221200e commit d7e6772

5 files changed

Lines changed: 25 additions & 23 deletions

File tree

src/content/docs/cloudflare-one/cloud-and-saas-findings/casb-dlp.mdx

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import { Render } from "~/components";
1111
Requires Cloudflare CASB and Cloudflare DLP.
1212
:::
1313

14-
You can use [Cloudflare Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/) to discover if files stored in a SaaS application contains sensitive data. To perform DLP scans in a SaaS app, first configure a [DLP profile](#configure-a-dlp-profile) with the data patterns you want to detect, then [add the profile](#enable-dlp-scans-in-casb) to a CASB integration.
14+
You can use [Cloudflare Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/) to discover if files stored in a SaaS application contain sensitive data. To perform DLP scans in a SaaS app, first configure a [DLP profile](#configure-a-dlp-profile) (a set of patterns that define what counts as sensitive data) with the data patterns you want to detect, then [add the profile](#enable-dlp-scans-in-casb) to a CASB integration.
1515

1616
## Supported integrations
1717

@@ -64,12 +64,13 @@ If you enable a DLP profile from the **Manage integrations** page, CASB will onl
6464
- Owner of the file
6565
- Location of the file (for example, moved to a different folder)
6666

67-
In order to scan historical data, you must enable the DLP profile during the [integration setup flow](#add-a-new-integration).
67+
:::caution
68+
If you add a DLP profile to an existing integration, CASB only scans files modified after you enabled the profile. To scan all files, you must enable the DLP profile during the [integration setup flow](#add-a-new-integration).
69+
:::
6870

6971
## Limitations
7072

7173
DLP in CASB will only scan:
7274

73-
- [Text-based files](/cloudflare-one/data-loss-prevention/#supported-file-types) such as documents, spreadsheets, and PDFs. Images are not supported.
74-
- Files less than or equal 100 MB in size.
75-
- Source code with a minimum size of 5 KB for Java and R.
75+
- Files less than or equal to 100 MB in size.
76+
- Java and R source code files that are at least 5 KB. Smaller files in these languages are skipped.

src/content/docs/cloudflare-one/cloud-and-saas-findings/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Available for all Zero Trust users.
1616
Free users can configure up to two CASB integrations. You must upgrade to an Enterprise plan to view the details of a finding instance.
1717
:::
1818

19-
Cloudflare's API-driven [Cloud Access Security Broker](https://www.cloudflare.com/learning/access-management/what-is-a-casb/) (CASB) integrates with SaaS applications and cloud environments to scan for misconfigurations, unauthorized user activity, <GlossaryTooltip term="shadow IT" link="https://www.cloudflare.com/learning/access-management/what-is-shadow-it/">shadow IT</GlossaryTooltip>, and other data security issues that can occur after a user has successfully logged in.
19+
Cloudflare's [Cloud Access Security Broker](https://www.cloudflare.com/learning/access-management/what-is-a-casb/) (CASB) connects to SaaS application and cloud environment APIs to scan for security issues that can occur after a user has successfully logged in. These include misconfigurations (such as overly permissive sharing settings), unauthorized user activity, <GlossaryTooltip term="shadow IT" link="https://www.cloudflare.com/learning/access-management/what-is-shadow-it/">shadow IT</GlossaryTooltip>, and other data security issues.
2020

2121
For a list of available findings, refer to [Cloud and SaaS integrations](/cloudflare-one/integrations/cloud-and-saas/). You can also send posture finding instances to external systems with [CASB webhooks](/cloudflare-one/integrations/cloud-and-saas/webhooks/).
2222

src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ head:
1010

1111
import { TabItem, Tabs, Details } from "~/components";
1212

13-
Findings are security issues detected within SaaS and cloud applications that involve users, data at rest, and other configuration settings. With Cloudflare CASB, you can review a comprehensive list of findings in Cloudflare One and immediately start taking action on the issues found.
13+
Findings are security issues detected within SaaS and cloud applications that involve users, data at rest (files stored in your apps), and other configuration settings. With Cloudflare CASB, you can review a comprehensive list of findings in Cloudflare One and take action on the issues found.
1414

1515
## Prerequisites
1616

@@ -93,6 +93,9 @@ File findings for some integrations (such as [Microsoft 365](/cloudflare-one/int
9393

9494
After reviewing your findings, you may decide that certain posture findings are not applicable to your organization. Cloudflare CASB allows you to remove findings or individual instances of findings from your list of active issues. CASB will continue to scan for these issues, but any detections will appear in a separate tab.
9595

96+
- **Ignore a finding** — Moves the entire finding type from **Active** to **Ignored**. New detections of this finding type still appear, but in the **Ignored** tab.
97+
- **Hide an instance** — Moves a single occurrence from **Active** to **Hidden**. Future occurrences for the same user or file go to the **Hidden** tab automatically.
98+
9699
### Ignore a finding
97100

98101
1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Posture Findings**.
@@ -169,13 +172,13 @@ Remediated findings will appear in **Cloud & SaaS findings** > **Posture Finding
169172
| Failed | CASB unsuccessfully remediated the finding. |
170173
| Rejected | CASB does not have the correct permissions to remediate the finding. |
171174

172-
If the status is **Completed**, remediation succeeded. If the status is **Failed** or **Rejected**, remediation failed, and you can select the finding to take action again.
175+
If the status is **Completed**, remediation succeeded. If the status is **Failed** or **Rejected**, remediation failed, and you can select the finding to take action again. A **Rejected** status indicates that CASB does not have the correct permissions to remediate the finding.
173176

174177
CASB will log remediation actions in **Logs** > **Admin**. For more information, refer to [Cloudflare One Logs](/cloudflare-one/insights/logs/).
175178

176179
## Resolve finding with a Gateway policy
177180

178-
Using the security findings from CASB allows for fine-grained Gateway policies which prevent future unwanted behavior while still allowing usage that aligns to your organization's security policy. You can view a CASB finding, like the use of an unapproved application, then immediately prevent or control access with Gateway.
181+
CASB detects security issues that already exist in your SaaS environment. To prevent the same issues from recurring, you can create a [Gateway HTTP policy](/cloudflare-one/traffic-policies/http-policies/) directly from a CASB finding. For example, you can block users from sharing files publicly or accessing unsanctioned applications.
179182

180183
CASB supports creating a Gateway policy for findings from the [Google Workspace integration](/cloudflare-one/integrations/cloud-and-saas/google-workspace/):
181184

src/content/docs/cloudflare-one/cloud-and-saas-findings/troubleshoot-casb.mdx

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ pcx_content_type: troubleshooting
44
sidebar:
55
order: 4
66
tags:
7-
- Debugging
7+
- Debugging
88
---
99

1010
Use this guide to troubleshoot common issues with Cloud Access Security Broker (CASB).
@@ -45,11 +45,10 @@ CASB integrations do not provide real-time updates. Scans are performed periodic
4545

4646
To trigger a new scan:
4747

48-
1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Cloud & SaaS integrations**.
48+
1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**.
4949
2. Find your integration and select **Configure**.
50-
3. Go to **CASB**.
51-
4. Turn off **Findings scanning**.
52-
5. After a few minutes, turn on **Findings scanning** again.
50+
3. Turn off **Scan for findings**.
51+
4. After a few minutes, turn on **Scan for findings** again.
5352

5453
This action will queue a fresh scan of your integration. Allow several hours for your findings to reflect the new results.
5554

@@ -91,8 +90,8 @@ Carefully examine the evidence provided in the finding. An object's status in th
9190

9291
### Report the issue
9392

94-
If you confirm the finding is a false positive, report the behavior to Cloudflare Support. Provide the finding ID and as much detail as possible. This helps the Support team refine the detection logic for all customers.
93+
If you confirm the finding is a false positive, report the behavior to Cloudflare Support. Provide the finding ID (visible in the finding's detail view) and as much detail as possible. This helps the Support team refine the detection logic for all customers.
9594

96-
### Ignore or hide the finding
95+
### Hide the finding
9796

98-
While Cloudflare investigates the issue, you can use **Move to ignore** on the finding or **Move to hidden** on an individual instance to remove it from your active list and reduce noise.
97+
While Cloudflare investigates the issue, you can [ignore the finding or hide individual instances](/cloudflare-one/cloud-and-saas-findings/manage-findings/#hide-findings) to remove it from your active list and reduce noise.

src/content/docs/cloudflare-one/integrations/cloud-and-saas/troubleshooting/casb.mdx

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -48,11 +48,10 @@ CASB integrations do not provide real-time updates. Scans are performed periodic
4848

4949
To trigger a new scan:
5050

51-
1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Cloud & SaaS integrations**.
51+
1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** > **Integrations**.
5252
2. Find your integration and select **Configure**.
53-
3. Go to **CASB**.
54-
4. Turn off **Findings scanning**.
55-
5. After a few minutes, turn on **Findings scanning** again.
53+
3. Turn off **Scan for findings**.
54+
4. After a few minutes, turn on **Scan for findings** again.
5655

5756
This action will queue a fresh scan of your integration. Allow several hours for your findings to reflect the new results.
5857

@@ -96,6 +95,6 @@ Carefully examine the evidence provided in the finding. An object's status in th
9695

9796
If you confirm the finding is a false positive, report the behavior to Cloudflare Support. Provide the finding ID and as much detail as possible. This helps the Support team refine the detection logic for all customers.
9897

99-
### Ignore or hide the finding
98+
### Hide the finding
10099

101-
While Cloudflare investigates the issue, you can use **Move to ignore** on the finding or **Move to hidden** on an individual instance to remove it from your active list and reduce noise.
100+
While Cloudflare investigates the issue, you can [ignore the finding or hide individual instances](/cloudflare-one/cloud-and-saas-findings/manage-findings/#hide-findings) to remove it from your active list and reduce noise.

0 commit comments

Comments
 (0)