Slack

Prerequisites:

1. Your Slack User has the Org Owner role

   1. Ideally this User is a Service Account

2. Your Slack tenant has the Discovery API enabled and available

1

Install the Teleskope Data Security app

• Navigate to Settings → Connectors → Slack in Teleskope

• Click Enroll New User → Add to Slack button

  
• Ensure you have the correct tenant selected and displayed in the upper right hand of the Authentication page

• Click Allow at the bottom of the page

• Return to Teleskope to begin scanning and creating DLP policies

2

Enable Notifications

1. Add the App to your Workspaces

   1. In your App Admin page, add the Teleskope app to any workspaces you would target for notifications.

2. Invite the App (/add) to target notification channels

If the app doesn't appear and was installed as a connector, contact a Workspace owner.

3

Create a DLP policy in Policy Maker

• Click Create Policy +

• Define your trigger conditions

• Restrict your policies to specific channels during testing

• Add automated actions

  • Use the Quarantine action to temporarily tombstone sensitive content

    • Determine an Admin channel for notifications and action options within slack

    • Optionally message the end user for self-reporting

Classifications & Filtering Behavior

We handle certain elements in different ways. Below is a summary of our filtering logic as well as elements that we do not detect for storage and filtering reasons.

Credit Card Numbers

Credit card numbers must pass our post-validation rules, meaning they must pass Luhn Algorithm checks.

Social Security Numbers

While certain SSNs such as 123-45-6789 are structurally valid under SSA assignment rules, we proactively filter out common test patterns or sequences that are far more likely to be false positives (FPs). This helps reduce noise in results and minimizes the likelihood of inaccurate detections during scanning.

Email Addresses

We filter out internal and company-specific email addresses during scans. This is primarily to reduce noise and manage storage effectively, particularly in the context of historical scanning, where repeated detection of internal contacts can become very storage-intensive.

The following elements are also skipped for similar storage and filtering reasons:

• WEBSITE

• FIRST_NAME

• LAST_NAME

• MIDDLE_NAME

• USER_IDENTIFIER

• LANGUAGE

• ORGANIZATION