New Apps Supported by CASB API

  • 13 May 2022
  • 0 replies

Badge +8

In case you didn't see the blog article published on May 10, here's some information on the new applications Netskope has added support for in our CASB API product.

We started rolling out support for these new applications at the end of April:

  • Workday
  • Yammer
  • Citrix ShareFile
  • Okta

With the addition of these four new applications, Netskope now supports a total of 23 applications in our CASB API product.

If you're not familiar with, or not using our CASB API product (and only using CASB Inline as part of NG-SWG and/or Cloud Inline), there are significant additional benefits that an API based product delivers, both standalone and in conjunction with an inline solution.

If you have only an inline deployment for CASB, or you’re just starting to look at CASB solutions, you may be wondering why you’d want or need a CASB API deployment. With API, CASB takes advantage of existing APIs in SaaS and IaaS applications to provide full granular context on data exposure and controls. Because of the requirement to give API access, CASB API is used for managed applications, where access can be granted to the CASB solution.  

Here are six example use cases where API enabled protection provides needed security, and also where it can complement inline protections:

  • Data-at-rest classification
  • Managing sensitive data exposure
  • Protecting against malware spreading via SaaS apps
  • Visibility & protection related to risky users, compromised accounts
  • Protection against risky misconfigurations
  • Visibility & protection related to connected apps, plug-ins

Data at rest classification can be used to identify sensitive data that predates inline controls or is added by unmanaged users, or to reassess data as compliance requirements evolve or threat intelligence is updated. CASB API protection can integrate with classification tools like Microsoft Information Protection and enable higher fidelity and adaptive inline policies by incorporating context from API.

0 replies

Be the first to reply!