Begin Scanning a Slack for Enterprise App

Authorize SaaS Security API to connect to Slack to scan all content shared within the app.
To connect Slack Enterprise Grid to SaaS Security API and begin scanning assets, you need to:
  • Ensure that you have an Slack Enterprise Grid administrator account with Organization Owner permissions.
  • Authorize a SaaS Security API bot to enable Admin Quarantine.
  • Grant SaaS Security API access to Slack.
  • Add the Slack Enterprise app to SaaS Security API, providing SaaS Security API information about your Slack account.
For information on which automated remediation capabilities SaaS Security API supports with Slack Enterprise, refer to Supported Content, Remediation and Monitoring.

Add Slack Enterprise App

In order for SaaS Security API to scan assets, you must consent to specific permissions during the course of adding the Slack Enterprise app.
  1. (
    ) Add your Slack Enterprise Grid domain as an internal domain.
  2. Sign out of all Slack workspaces.
    Doing so ensures that you sign in under the correct account and workspace.
  3. Enable the privileges required for communication between SaaS Security API and the Slack app.
    The Organization Owner must contact and request that Slack Support enable the Slack app for DLP API access and integration with SaaS Security API. Slack Support requires over-the-phone enablement whereby you answer a serious of security questions.
    DLP API access provides visibility into the assets in Slack and allows SaaS Security API to monitor the sharing of assets.
  4. Add the Slack app.
    1. From the
      Add a Cloud App
    2. Select
      Slack Enterprise Grid
    3. Connect to Slack Account
    4. Enter your team’s Slack domain/workspace (top-level enterprise organization), then
    5. Sign in
      with an administrator account that is an Organization Owner.
    6. Review and
      the requested permissions.
      SaaS Security API requires these permissions to scan your assets on Slack Enterprise.
      After authentication, SaaS Security API adds the new Slack app to the list of Cloud Apps as Slack n, where n is the number of Slack app instances that you have connected to SaaS Security API. You’ll specify a descriptive name soon.
  5. Authorize a SaaS Security API bot to enable Admin Quarantine.
    1. Select the Slack n link on the Cloud Apps list.
    2. In
      Cloud App Detail
      , add an email address for the quarantine administrator, click
      Bot Token
      in the dropdown, then
      to reauthorize access.
  6. (
    ) Give a descriptive name to this app instance.
    1. Select the Slack n link on the Cloud Apps list.
    2. Enter a descriptive
      to differentiate this instance of Slack from other instances.
    3. Click
      to save your changes.
  7. Start scanning the new Slack app for incidents.
    1. Select
      Cloud Apps & Scan Settings
    2. In the Cloud Apps row that corresponds to the new Slack app, select
      Start Scanning
  8. During the discovery phase, as SaaS Security API scans files and matches them against enabled policy rules.
    Verify that your default policy rules are effective. If the results don’t capture all risks or you see false positives, improve your results.

Identify Risks

When you add a new cloud app, SaaS Security API automatically scans the cloud app against the default data patterns and displays the match occurrences. You can take action now to improve your scan results and identify risks.
  1. (
    ) Modify match criteria for existing policy rules.
  2. (
    ) Add new policy rules.
    Consider the business use of your app, then identify risks unique to your enterprise. As necessary, add new:
  3. (
    ) Configure or edit a data pattern.
    You can Configure Data Patterns to identify specific strings of text, characters, words, or patterns to make it possible to find all instances of text that match a data pattern you specify.

Fix Slack Enterprise App Onboarding Issues

The most common issues related to adding or accessing Slack Enterprise app are as follows:
When you attempt to log in to your admin account from SaaS Security API, SaaS Security API returns an authorization error.
You have a Slack app open in your browser for a workspace other than the workspace associated with the admin account or the admin account isn’t an Organization Owner.
Log out of all Slack workspaces and verify that the administrator account is an Organization Owner.

Fix Slack Enterprise App Quarantine Issues

If SaaS Security API is unable to quarantine the asset, quarantine status displays a summary explanation of the quarantine failure. If you need additional information, and due to the underlying differences between cloud apps, use the table below for a detailed explanation and resolution.
You’re not receiving notifications in Slack when SaaS Security API quarantines an asset and quarantine status indicates
Missing authorized bot
Admin Quarantine actions fail if you did not authorize SaaS Security API bot to enable notifications or you did not add an email address for the quarantine administrator. In these cases, SaaS Security API can neither quarantine files nor notify the quarantine administrator.
Authorize a SaaS Security API bot to enable Admin Quarantine.
When you attempt to manually quarantine a file, SaaS Security API doesn’t quarantine the file and you receive a quarantine status that indicates
Missing authorized bot
When you choose admin quarantine for automatic remediation, SaaS Security API doesn’t quarantine the file and you receive a quarantine status that indicates
Missing authorized bot

Recommended For You