Published: 12 March 2015
Summary
Cloud security leaders evaluating CASB functionality must consider the nuances of how the technology is deployed to secure SaaS applications, and the implications on the end-user platforms that use it. We describe what must be considered for successful CASB selection.
Included in Full Research
- Start With a SaaS Application Discovery Phase Before Undertaking a CASB Deployment
- Make IAM Integration a Foundational Capability of Your CASB Evaluation
- Decide or Pragmatically Settle on the Deployment Mode That Works Best for Your Range of Applications and Types of End-User Access Methods
- Mode 1: Reverse Proxy Mode
- Mode 2: Forward Proxy Mode
- Mode 3: API Mode
- Consider the Implications of the End-User Computing Options Supported in the Organization When Judging How the CASB Provider Delivers Against the Four Pillars of CASB Functionality
- Ensure That the Implications of a CASB's Encryption and Tokenization Features of the Organization's Data in a SaaS Application Are Understood
- Use CASBs to Extend the Organization's DLP Strategy to Data Deployed in the Cloud
- Ensure That the CASB's Threat Prevention Features Are Given Appropriate Weighting
- Define the Requirements for CASB Integration With Your Existing Security Tool Chain