Why has the CASB become essential?

 

Ten years ago, most of a company’s data travelled across its own network, behind its own firewall. Today, much of that data lives in cloud applications that the company does not control technically – it merely uses them. This shift creates two problems:

Shadow IT

employees adopt cloud tools (file sharing, messaging, storage) without the CIO’s approval, often simply for convenience. The company then loses visibility over where its data is going.

Loss of control

a traditional firewall protects the internal network, but sees nothing of what an employee does once connected to a cloud application from their personal computer, a café or their phone.

The 4 pillars of CASB

Visibility
Compliance
Data protection
Threat protection

Identify all cloud applications used within the company, including those not approved by the CIO (Shadow IT). You cannot secure what you cannot see.

Ensure that cloud usage complies with current regulations (notably GDPR) and the company's internal policies, for example by prohibiting the hosting of sensitive data on a non-compliant cloud service.

Data protection (DLP)

Prevent a confidential file from being shared publicly, downloaded to an unmanaged device, or sent to a risky destination. This is often the most tangible function for security teams.

Detect abnormal behaviour : logins from an unusual country, mass file downloads within a few minutes, a probably compromised account.

API CASB vs Proxy CASB : an important technical distinction

API mode

the CASB connects directly to the cloud application’s API (Microsoft 365, Google Workspace…) to analyse data already present, after the fact. Advantage : no impact on performance, rapid deployment. Limitation : analysis happens retrospectively, not in real time at the moment of the action.

Proxy mode

Traffic physically passes through the CASB before reaching the cloud application, enabling real-time control (blocking an action before it happens). More comprehensive, but more complex to deploy across all applications.

CASB, Firewall, SWG, ZTNA : what are the differences ?

 

These security components are complementary, not competing, which is precisely why they are brought together in a SASE architecture :

  Protected scope Details
Firewall The network perimeter filters incoming/outgoing traffic
SWG Web browsing : filters visited sites, blocks web threats
ZTNA Access to internal applications : verifies every connection, with no default trust
CASB Use of cloud applications : visibility and control over what happens within them

CASB in a SASE architecture

The CASB is one of the founding components of the SASE (Secure Access Service Edge) model, alongside SD-WAN, ZTNA and SWG. The aim of SASE is to bring all these functions together in a single platform rather than stacking different security tools, often from different vendors – which, in practice, complicates day-to-day management and creates blind spots between solutions.

With a unified SASE platform, the security policy defined for a user is applied consistently, whether they are accessing the internal network, the Internet or a cloud application.

Customer case studies

Discover how our solution
is implemented in the field.

PARIS BAR ASSOCIATION

“Our mission demands an absolute standard of service continuity and confidentiality: legal ...

COURSIER.FR

“We needed an infrastructure able to keep pace and secure our traffic. Today, all our ...

Fondation Perce-Neige

With a limited budget, we needed to upgrade an IT network that was ageing and, above all, too ...

UCPA

We needed to move away from a rigid and costly MPLS. With SAYSE, we have gained agility, resilience ...

Cités Caritas non-profit

Cités Caritas has modernised its network across more than 120 sites thanks to SAYSE’s ...

CRH

Moving to SD-WAN with SAYSE was a turning point: lower costs, greater control and a network finally ...

CCCA BTP

We were looking for greater flexibility and security and, above all, a less costly infrastructure, ...

Watèa by Michelin.

SAYSE began by equipping our Clermont-Ferrand site, followed by our Boulogne-Billancourt site. From ...