Migrate Slack Enterprise from Classic to Next Generation API Data Protection

The article provides guidance for customers currently using the Classic API Data Protection for Slack Enterprise. It outlines a clear process for migrating to the enhanced Next Generation API Data Protection, which offers improved performance and functionality. The migration involves key steps, including preparation, configuration updates, and verification, ensuring a smooth transition to the more advanced platform.

Slack Teams Integration on Non-Enterprise Plans

In the Classic platform, Netskope offered API-based integration with Slack Teams. With the Next Generation platform, Slack integration requires the Slack Enterprise Grid plan, as Slack now mandates the use of Discovery APIs for compliance and security.

Customers on Slack Pro or Business+ (a.k.a Slack Teams) will no longer be able to use API-based integration after migrating.

What You Need to Do?

• Already on Enterprise Grid? If your organization is already subscribed to the Enterprise Grid plan and has our Next Generation API integration deployed, no action is required.

• Planning to upgrade? If you are considering or in the process of upgrading to the Enterprise Grid plan, please work with the slack account team. Once your license is upgraded, you can proceed and follow the migration steps for Slack Enterprise.

• Not on Enterprise Grid? If you are not on Enterprise Grid today, review your Slack licensing strategy before migrating to ensure continued API integration support. The Next Generation API Data Protection integration for Slack is exclusive to the Enterprise Grid plan.

API-Enriched Controls in CASB Inline

For customers using the Slack Enterprise in the Classic platform, Netskope supported API-enriched controls, where CASB Inline policies could take action based on additional exposure context provided by the API, such as sensitive data indicators.

This feature is not available in Next Generation API Data Protection. When migrating from Classic to Next Generation, any policies that rely on this feature must be reviewed and adapted using the alternative enforcement options provided in the Next Generation platform. 

To learn more about the technical details, talk to your Netskope sales representative or customer support.

Migration Steps

Here are the broad steps to migrate your classic Slack Enterprise instance to Next Generation.

1. Create a new Next Generation API Data Protection Slack Enterprise instance. To learn more: see sample video.

2. Disable the existing classic API Data Protection policies from Policies > API Data Protection > SAAS > Classic.

   

3. Create new policies on Next Generation API Data Protection from Policies > API Data Protection > SAAS > Next Gen. To learn more: see sample video.

4. Delete the existing classic API Data Protection policies from Policies > API Data Protection > SAAS > Classic.

   

   Running Classic and Next Generation policies simultaneously can lead to unexpected behavior if legal hold or quarantine profiles exist on both platforms. Additionally, this setup risks upstream throttling due to rate limits, potentially interrupting all protections. Therefore, Netskope strongly discourages running Classic and Next Generation policies and legal hold/quarantine profiles concurrently.

5. Go to Settings > Configure App Access > Classic. Select the Slack Enterprise app, click the instance and uncheck CASB API. This prevents further upstream API calls without removing the instance. This allows you to continue to view relevant alerts and quarantine files.

   

6. Wait for six months or the duration of your incident retention period. Consult your Netskope sales representative to confirm the exact retention period. During this time, you can manage incidents and work with quarantined files.

7. Delete the classic Slack Enterprise instance. To do so, navigate to Settings > Configure App Access > Classic, select the Slack Enterprise app, then click the Remove Instance icon to delete the app instance.

   

To learn more about the Next Generation API Data Protection feature matrix per cloud app, see Next Generation API Data Protection Feature Matrix per Cloud App.