How many REST Detectors can we have in a single Enforce Server console?

Products

• Data Loss Prevention Cloud Detection Service
• Data Loss Prevention Cloud Detection Service for REST

Issue/Introduction

You have already configured a REST Cloud Detection Server in your Enforce Server console, but you've also purchased a REST Detector to integrate with your REST API and want to add it to Enforce.

Is there a limit on the number of Cloud Detectors you can have in a single console?

Environment

Cloud Detection Service for REST

DLP 15.8 or earlier

Cause

For DLP 15.8 and prior, there can only be one REST Detector enrolled per Enforce Console - this is by design.

Having 2 of them creates conflicts as the Cloud Service Gateway cannot distinguish between 2 REST Detectors when both are installed in the same Enforce server - so the filters which are responsible for detection will fail to load properly.

1. The DLP Cloud Detection Service which integrates with a customer's Custom REST API Client, is one type of REST Detector.
2. The DLP Cloud Detection Service which integrates with the CASB solution (aka the CloudSOC, formerly known as Elastica) is another type of REST Detector.

Resolution

If you purchased 2 separate "REST" Cloud Detectors confirm with Technical Support whether both are required:

• While a single Cloud Detector can handle requests from BOTH types of client simultaneously, and will auto-scale to meet demands on the service.
• In some cases it makes more sense to have 2 REST Cloud Detectors, which will require 2 separate Enforce Servers to manage them.

Additional Information

Having 2 REST Detectors enrolled in the same Enforce Server will cause problems as per this article: CloudSoc Securlets show Sync Failure in DLP when 2 REST Detectors are present (broadcom.com)