After a new Cloud Detector is added to the Enforce as a Detection Server, no incidents are being created, and it doesn't seem possible to view all configuration options as expected (e.g., incidents specific to "cloud" should be listed separately as an incident category).
Yet it is confirmed that content is successfully being uploaded - via the Elastica CloudSOC, for example
Newly added DLP Cloud Detector that has been successfully registered and enrolled with Elastica CASB CloudSOC.
The Cloud Detection Service covers all associated components such as CDS for CASB, CDS for Email, and CDS for WSS (aka Cloud SWG)
In the Enforce Server there are certain Role-Based Access Controls (RBAC) for managing the configuration of a Cloud Detection Server (CDS).
There are also new controls required for viewing cloud incidents.
Also, Cloud Detectors have additional configuration options to ensure that existing Policy Groups are assigned to Cloud Detectors for inspection of content that is being pushed to the CASB CloudSOC.
Login to the Enforce Server as Administrator, go to Login Management > Roles
*The application detection configuration is required for CDS for CASB to receive policies: