Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A cloud access security broker sits between users and SaaS applications to enforce policy: discovering shadow IT, controlling sharing, preventing data loss, and spotting account misuse.

What Is a CASB?
A cloud access security broker, usually shortened to CASB, is a control point between the people in your organisation and the software-as-a-service applications they use. It answers questions that neither the endpoint nor the firewall can: which cloud applications are actually in use, what data has been uploaded to them, who it has been shared with, and whether a given session looks like the account owner or someone who bought their password. Gartner coined the term in 2012, and the market has since been absorbed into broader security service edge platforms, but the capability remains distinct.
Most products are described in terms of four pillars, and they are a fair summary of the value.
How a CASB connects determines what it can see and what it can stop.
API mode connects to the application’s management APIs. It scans data already in the tenant, reads the audit log, and can retroactively unshare a file or revoke an OAuth grant. It covers managed and unmanaged devices equally because it never sits in the traffic path, but it is out-of-band: action follows the event by seconds or minutes rather than preventing it.
Forward proxy routes user traffic through the broker, usually via an agent or a PAC file. It can block an upload in real time and covers unsanctioned applications, but only for devices you control.
Reverse proxy integrates with the identity provider so that sessions to a sanctioned application are redirected through the broker after authentication. It reaches unmanaged and personal devices, which is its main attraction, at the cost of breaking occasionally when a vendor changes their front end.
Serious deployments combine at least two modes: API coverage for everything, with inline control for the handful of applications and actions where prevention genuinely matters.
Few organisations buy a standalone CASB today. The function ships inside security service edge platforms from Microsoft, Netskope, Zscaler, Palo Alto Networks, and others, alongside secure web gateway, zero trust network access, and private application access. If you are already running one of those, you probably own CASB capability and may simply not have switched it on. Check before you buy anything: a licence you already hold, properly configured, usually beats a new product.
A CASB enforces policy on traffic and data it can observe. It does not fix a SaaS tenant that was configured badly in the first place, it cannot see server-to-server integrations that never touch a user session, and it depends entirely on the quality of your classification rules. Over-aggressive blocking also teaches people to route around it, which is how a shadow IT problem becomes a shadow IT problem with personal devices attached.
Start in monitor-only mode and publish the discovery report to the business; the list of unsanctioned applications is usually persuasive on its own. Pick the two or three data types that would genuinely hurt if they left—customer records, payroll, source code—and write narrow rules for those rather than broad ones for everything. Tune for a month before you enable blocking. Connect the alerts to your security operations centre rather than a mailbox nobody reads, and review OAuth application consents regularly, since a malicious third-party app is one of the quietest ways data leaves a tenant.
Under UK GDPR, personal data in an unsanctioned SaaS tool is still your responsibility, and the ICO expects you to know where it is. Discovery is the first honest answer to that question.
At Privia Security, we review SaaS tenant configuration and data flows as part of our cloud security solutions.
No. A secure web gateway filters outbound web traffic by category, reputation, and content, and is largely blind to what happens inside a SaaS tenant. A CASB understands the application: it knows the difference between viewing a document and sharing it externally, and it can read the tenant’s own audit log through an API. Modern platforms sell both together, but the capabilities are distinct.
Yes, in API mode. Connecting to the application’s management API gives you data scanning, configuration checks, audit log analysis, and retroactive remediation with nothing installed on the endpoint. You lose real-time blocking of uploads and coverage of unsanctioned applications. Many organisations run API mode everywhere and add inline control only for the specific applications where prevention is worth the operational cost.
It is usually the quickest way to measure it. Discovery builds an inventory from existing firewall, proxy, or endpoint logs and ranks services by users, traffic volume, and risk. That inventory lets you sanction what the business genuinely needs, consolidate duplicates, and block the rest. Treat the output as a conversation with department heads rather than a blocking list issued without warning.
You still need the capability, and in a Microsoft-only estate you most likely already own it. Defender for Cloud Apps provides discovery, session control, and data policies for Microsoft 365 and third-party services. The question is whether it is configured, monitored, and tuned. An unconfigured licence provides no protection, and single-vendor estates tend to assume coverage that nobody has verified.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.