<img src="//pixel.quantserve.com/pixel/p-_JKXxuL8SR7wu.gif?labels=_fp.event.Default" style="display: none;" border="0" height="1" width="1" alt="Quantcast">
blog-banner.jpg

Next-Gen CASB Blog

Private App Cloud Migration Requires CASB

By Rich Campagna | December 8, 2017 at 4:37 AM

cloud migration.pngCloud Access Security Brokers (CASB) have gotten a lot of adoption over the past couple of years, with Gartner recently publishing their first Magic Quadrant for CASBs.

Since Cloud is in the name, most organizations think of CASB when trying to achieve their security and compliance goals for public SaaS applications like Office 365, Salesforce and Box. Provided you pick the right CASB vendor, however, and your CASB can provide data & threat protection not just for public cloud apps, but for private cloud apps as you migrate them to the public cloud. 

As you move a private application (whether it's a custom developed app or packaged software) to a public cloud platform like AWS, Azure, or GCP, these applications start to feel more and more like a public SaaS applications. External availability from any device, and from anywhere on the internet, backend APIs, etc. Your data moves beyond the firewall.

This increased availability can mean wonders for productivity and mobility, but the shared security responsibility in the cloud needs to be kept in mind here as much as with SaaS applications.

Keep private app migration in mind when making a decision on which CASB vendor to select, paying careful attention to whether the vendor can support applications that don't exist in a fixed catalog. The Bitglass Zero-day Core was designed with exactly this use case in mind - any app beyond the firewall. 

Request a Demo