Applies to: Microsoft Cloud App Security
App connectors use the APIs of app providers to enable greater visibility and control by Microsoft Cloud App Security over the apps you connect to.
Microsoft Cloud App Security leverages the APIs provided by the cloud provider. Each service has its own framework and API limitations such as throttling, API limits, dynamic time-shifting API windows, and others. Microsoft Cloud App Security worked with the services to optimize the usage of the APIs and to provide the best performance. Taking into account different limitations services impose on the APIs, the Cloud App Security engines use the allowed capacity. Some operations, such as scanning all files in the tenant, require numerous APIs so they're spread over a longer period. Expect some policies to run for several hours or several days.
Cloud App Security supports multiple instances of the same connected app. For example, if you have more than one instance of Salesforce (one for sales, one for marketing) you can connect both to Cloud App Security. You can manage the different instances from the same console to create granular policies and deeper investigation. This support applies only to API connected apps, not to Cloud Discovered apps or Proxy connected apps.
Multi-instance is not supported for Office 365 and Azure.
How it works
Cloud App Security is deployed with system admin privileges to allow full access to all objects in your environment.
The App Connector flow is as follows:
- Cloud App Security scans and saves authentication permissions.
- Cloud App Security requests the user list. The first time the request is done, it may take some time until the scan completes. After the user scan is over, Cloud App Security moves on to activities and files. As soon as the scan starts, some activities will be available in Cloud App Security.
- After completion of the user request, Cloud App Security periodically scans users, groups, activities, and files. All activities will be available after the first full scan.
This connection may take some time depending on the size of the tenant, the number of users, and the size and number of files that need to be scanned.
Depending on the app to which you're connecting, API connection enables the following items:
Account information - Visibility into users, accounts, profile information, status (suspended, active, disabled) groups, and privileges.
Audit trail - Visibility into user activities, admin activities, sign in activity.
Data scan - Scanning of unstructured data using two processes -periodically (every 12 hours) and in real-time scan (triggered each time a change is detected).
App permissions - Visibility into issued tokens and their permissions.
Account governance - Ability to suspend users, revoke passwords, etc.
Data Governance - Ability to quarantine files, including files in trash, and overwrite files.
App permission governance - Ability to remove tokens.
The following table lists, per cloud app, which abilities are supported with App connectors:
|AWS||Box||Dropbox||GCP||G Suite||Office 365||Okta||Service Now||Salesforce||Webex||Workday|
|List accounts||✔||✔||✔||Subject G Suite connection||✔||✔||✔||✔||✔||✔||✔|
|List groups||✔||✔||✔||Subject G Suite connection||✔||✔||✔||✔||✔||Not supported by provider|
|List privileges||✔||✔||Subject G Suite connection||✔||✔||Not supported by provider||✔||✔||✔||Not pported by provider|
|User governance||✔||Coming soon||Subject G Suite connection||✔||✔||Coming soon||✔||Coming soon||t supported by provider|
|Log on activity||✔||✔||✔||Subject G Suite connection||✔||✔||✔||✔||✔||✔||✔|
|User activity||Not applicable||✔||✔||✔||✔ - requires Google Business or Enterprise||✔||✔||Partial||Supported with lesforce Shield||✔||✔|
|Administrative activity||✔||✔||✔||✔||✔||✔||✔||Partial||✔||✔||Not supported by provider|
|DLP - Periodic scan||✔||Coming soon||Not applicable||✔||✔||Not applicable||Not supported by ovider|
|DLP - Near-real-time scan||✔||✔||Not applicable||✔ - requires Google Business Enterprise||✔||Not applicable||✔||✔||✔||Not supported by provider|
|Sharing control||✔||✔||✔||Not applicable||✔||✔||Not applicable||Not applicable||✔||Not supported by ovider|
|File governance||✔||✔||✔||Not applicable||✔||✔||Not applicable||✔||Not supported by provider|
|View app permissions||Not applicable||Not supported by provider||Coming on||Not applicable||✔||✔||Not applicable||✔||Not applicable||Not applicable|
|Revoke app permissions||Not applicable||Not supported by provider||ming soon||Not applicable||✔||✔||Not applicable||✔||Not applicable||Not applicable|
|Apply Azure Information Protection labels||Not applicable||✔||Not applicable||✔||✔||Not applicable||Not applicable||Not applicable|
For some apps, it may be necessary to white list IP addresses to enable Cloud App Security to collect logs and provide access for the Cloud App Security console. For more information, see Network requirements.
For each app that you want to connect with the Cloud App Security API integration, we recommend creating an admin service account dedicated to Cloud App Security.
To get updates when URLs and IP addresses are changed, subscribe to the RSS as explained in: Office 365 URLs and IP address ranges.
To use App Connectors, you need to make sure you have the following things for each specific app:
|AWS||Newly created user|
|Box||Enterprise||It's strongly recommended that you connect to Box as an Admin. Connecting as a Coadmin will result in only partial data visibility. If you connect as a Coadmin, make sure to select all permissions.|
|GCP||See the connect GCP prerequisites|
|G Suite||G Suite Business or Enterprise preferred
G Suite Enterprise (minimally)
|Office 365||Global Admin|
|Okta||Enterprise (not trial)||Admin|
|ServiceNow||Eureka and up||Admin + RestAPI role|
|Webex||Admin + Compliance Admin|
|Workday||See the connect Workday prerequisites|
Cloud App Security is deployed in Azure and fully integrated with ExpressRoute. All interactions with the Cloud App Security apps and traffic sent to Cloud App Security, including upload of discovery logs, is routed via ExpressRoute public peering for improved latency, performance, and security. There are no configuration steps required from the customer side. For more information about Public Peering, see ExpressRoute circuits and routing domains.
Check out this video!