# Enterprise+

### **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
3. Your Teleskope user has the *Admin* role

{% stepper %}
{% step %}

### **Install the Teleskope Data Security app**

* Navigate to Settings → Connectors → Slack

* Click **Enroll+**

* Select the **Full access** radio button

* Click the **Add to Slack** button<br>

  <div align="left"><figure><img src="https://2383928706-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgO8NOoWqwRd6MduHoEy7%2Fuploads%2FLMUG6BsxXTsV8ytnOgD9%2Fimage.png?alt=media&#x26;token=3e856a12-69f4-4731-8a79-c6f5f4282f28" alt="" width="208"><figcaption></figcaption></figure></div>

* 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

* Teleskope will automatically begin scanning
  {% endstep %}

{% step %}

### 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

{% hint style="info" %}
If the app doesn't appear and was installed as a connector, contact a Workspace owner.
{% endhint %}
{% endstep %}

{% step %}

### 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&#x20;
    * Optionally message the end user for self-reporting
      {% endstep %}
      {% endstepper %}

## 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](https://en.wikipedia.org/wiki/Luhn_algorithm) checks.

### Social Security Numbers&#x20;

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.

{% hint style="info" %}

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

* `WEBSITE`
* `FIRST_NAME`
* `LAST_NAME`
* `MIDDLE_NAME`
* `USER_IDENTIFIER`
* `LANGUAGE`
* `ORGANIZATION`
  {% endhint %}