Move one Cloud Detection Server from one Enforce Server to another
search cancel

Move one Cloud Detection Server from one Enforce Server to another

book

Article ID: 184777

calendar_today

Updated On:

Products

Data Loss Prevention Cloud Detection Service Data Loss Prevention Cloud Detection Service for ICAP Data Loss Prevention Cloud Detection Service for REST Data Loss Prevention Cloud Service for Email

Issue/Introduction

  • Cloud Detection Servers are dedicated to per Enforce, this is why there is no procedure for such action. 
  • If there is a need to move one server to another, open a case with support. 

Resolution

Cloud Detection Servers are dedicated to per Enforce, this is why there is no procedure for such action. 
However, if there is a need to move one server to another please follow the steps below: 

  1. Because incidents created for one Enforce cannot be shipped to a different Enforce Server, before migrating you should first stop all traffic from being sent to the Detector.
  2. Depending on the type of Cloud Detector, do one of the following:
    • CloudSOC
      • De-activate the Enforce Managed DLP instance in the CloudSOC (note: do not Remove, just De-Activate) Portal+
      • Document/Backup(screenshot, or print to pdf) Existing Cloud applications from Enforce associated with the cloud detector.
      • Delete the cloud applications, this is a necessary step to deleted the detector from Enforce
    • WSS
      • Disable the Scanning of All Traffic in WSS
    • O365
      • Disable DLP transport rule in O365 / Gmail to stop sending messages through the service
  3. Remove the CDS from old Enforce server.
  4. Open a case with support to unbind specific Detector ID from original Enforce Server. 
  5. The Cloud Support team will:
    • unbind specific detector ID from Enforce
    • generate and provide new Enrollment Bundle which can be used to connect to the new Enforce Server
  6. After the detector has been rebound.
    • Ensure the newly re-added detector shows as 'connected' in the Enforce Console 
    • CloudSOC
      • Re-create applications removed in step 2.
      • Re-activeate the Enforce Managed DLP instance in the CloudSOC Portal 
      • Re-sync cloud applications from Enforce.
    • WSS
      • Re-Enable the Scanning of All Traffic in WSS
    • O365
      • Re-Enable the DLP Transport rule in O3654 / Gmail to resume sending messages through the service. 

 

Additional Information

For more detailed steps on migration, please see You need to migrate your Cloud Service Detector to a new Enforce Server (broadcom.com).