Tying SaaS discovery to enforcement
Shadow IT and controlling access to sanctioned versus unsanctioned SaaS applications are among the more persistent problems IT administrators face in cloud environments. Cloudflare's Secure Web Gateway and its new API-driven Cloud Access Security Broker (CASB) are designed to work together, moving teams from discovering Shadow IT to acting on it in minutes.
What the CASB surfaces
The API-driven CASB begins with visibility into SaaS applications, aimed at preventing data leaks and compliance violations. Integration with services such as Google Workspace and Microsoft 365 takes a few clicks; from there, IT and security teams can see which applications and services users sign into and how company data is being shared.
From findings to Gateway policy
Beta feedback from the API-driven CASB followed a consistent theme: setup and detection were easy, but customers were left asking how to fix what had been found. In practice, the urge to act arrives almost immediately after investigating the most critical issues — whether an unknown application used for Shadow IT, or a known but unapproved application whose functionality, access or behaviors need limiting. Without a path to remediation, teams were left with useful data and no clear starting point.
The cross-product integration addresses this by letting administrators create Gateway policies directly from CASB security findings. Findings are issues detected within SaaS applications involving users, data at rest, and settings, each assigned a Low, Medium, High or Critical severity per integration. Basing Gateway policies on these findings allows fine-grained control that blocks unwanted behavior while still permitting usage that matches company security policy. The workflow — from viewing an issue such as an unapproved SaaS application to preventing or controlling access — takes minutes and runs on a single, unified platform.
Consider the CASB Google Workspace security finding around third-party apps, which detects sign-ins or other permission sharing from a user's account. In a few clicks, an administrator can create a Gateway policy blocking some or all activity, such as uploads or downloads, to the detected SaaS application. The policy can cover some or all users, depending on what access has been granted to the user's account. Because CASB surfaces the exact behavior, Gateway can be used for swift, targeted action.
Availability
The Secure Web Gateway can be adopted now by signing up here. The API-driven CASB is in closed beta, with new customers onboarded each week; access can be requested here to try the cross-product feature. A whitepaper covers further detail on simplifying SaaS application protection.



