LogoLogo
Knowledge BaseCommunityRelease NotesRequest Demo
  • Overview
  • Quick Start
    • Onboarding Guide
  • Data Sources & Transports
    • Supported Logs
      • 1Password Logs
      • Apache Logs
      • AppOmni Logs
      • Asana Logs
      • Atlassian Logs
      • Auditd Logs
      • Auth0 Logs
      • AWS Logs
        • AWS ALB
        • AWS Aurora
        • AWS CloudFront
        • AWS CloudTrail
        • AWS CloudWatch
        • AWS Config
        • AWS EKS
        • AWS GuardDuty
        • AWS Security Hub
        • Amazon Security Lake
        • AWS S3
        • AWS Transit Gateway
        • AWS VPC
        • AWS WAF
      • Azure Monitor Logs
      • Bitwarden Logs
      • Box Logs
      • Carbon Black Logs
      • Cisco Umbrella Logs
      • Cloudflare Logs
      • CrowdStrike Logs
        • CrowdStrike Falcon Data Replicator
        • CrowdStrike Event Streams
      • Docker Logs
      • Dropbox Logs
      • Duo Security Logs
      • Envoy Logs
      • Fastly Logs
      • Fluentd Logs
      • GCP Logs
      • GitHub Logs
      • GitLab Logs
      • Google Workspace Logs
      • Heroku Logs
      • Jamf Pro Logs
      • Juniper Logs
      • Lacework Logs
        • Lacework Alert Channel Webhook
        • Lacework Export
      • Material Security Logs
      • Microsoft 365 Logs
      • Microsoft Entra ID Audit Logs
      • Microsoft Graph Logs
      • MongoDB Atlas Logs
      • Netskope Logs
      • Nginx Logs
      • Notion Logs
      • Okta Logs
      • OneLogin Logs
      • Orca Security Logs (Beta)
      • Osquery Logs
      • OSSEC Logs
      • Proofpoint Logs
      • Push Security Logs
      • Rapid7 Logs
      • Salesforce Logs
      • SentinelOne Logs
      • Slack Logs
      • Snowflake Audit Logs (Beta)
      • Snyk Logs
      • Sophos Logs
      • Sublime Security Logs
      • Suricata Logs
      • Sysdig Logs
      • Syslog Logs
      • Tailscale Logs
      • Teleport Logs
      • Tenable Vulnerability Management Logs
      • Thinkst Canary Logs
      • Tines Logs
      • Tracebit Logs
      • Windows Event Logs
      • Wiz Logs
      • Zeek Logs
      • Zendesk Logs
      • Zoom Logs
      • Zscaler Logs
        • Zscaler ZIA
        • Zscaler ZPA
    • Custom Logs
      • Log Schema Reference
      • Transformations
      • Script Log Parser (Beta)
      • Fastmatch Log Parser
      • Regex Log Parser
      • CSV Log Parser
    • Data Transports
      • HTTP Source
      • AWS Sources
        • S3 Source
        • CloudWatch Logs Source
        • SQS Source
          • SNS Source
        • EventBridge
      • Google Cloud Sources
        • Cloud Storage (GCS) Source
        • Pub/Sub Source
      • Azure Blob Storage Source
    • Monitoring Log Sources
    • Ingestion Filters
      • Raw Event Filters
      • Normalized Event Filters (Beta)
    • Data Pipeline Tools
      • Chronosphere Onboarding Guide
      • Cribl Onboarding Guide
      • Fluent Bit Onboarding Guide
        • Fluent Bit Configuration Examples
      • Fluentd Onboarding Guide
        • General log forwarding via Fluentd
        • MacOS System Logs to S3 via Fluentd
        • Syslog to S3 via Fluentd
        • Windows Event Logs to S3 via Fluentd (Legacy)
        • GCP Audit to S3 via Fluentd
      • Observo Onboarding Guide
      • Tarsal Onboarding Guide
    • Tech Partner Log Source Integrations
  • Detections
    • Using Panther-managed Detections
      • Detection Packs
    • Rules and Scheduled Rules
      • Writing Python Detections
        • Python Rule Caching
        • Data Models
        • Global Helper Functions
      • Modifying Detections with Inline Filters (Beta)
      • Derived Detections (Beta)
        • Using Derived Detections to Avoid Merge Conflicts
      • Using the Simple Detection Builder
      • Writing Simple Detections
        • Simple Detection Match Expression Reference
        • Simple Detection Error Codes
    • Correlation Rules (Beta)
      • Correlation Rule Reference
    • PyPanther Detections (Beta)
      • Creating PyPanther Detections
      • Registering, Testing, and Uploading PyPanther Detections
      • Managing PyPanther Detections in the Panther Console
      • PyPanther Detections Style Guide
      • pypanther Library Reference
      • Using the pypanther Command Line Tool
    • Signals
    • Policies
    • Testing
      • Data Replay (Beta)
    • Framework Mapping and MITRE ATT&CK® Matrix
  • Cloud Security Scanning
    • Cloud Resource Attributes
      • AWS
        • ACM Certificate
        • CloudFormation Stack
        • CloudWatch Log Group
        • CloudTrail
        • CloudTrail Meta
        • Config Recorder
        • Config Recorder Meta
        • DynamoDB Table
        • EC2 AMI
        • EC2 Instance
        • EC2 Network ACL
        • EC2 SecurityGroup
        • EC2 Volume
        • EC2 VPC
        • ECS Cluster
        • EKS Cluster
        • ELBV2 Application Load Balancer
        • GuardDuty Detector
        • GuardDuty Detector Meta
        • IAM Group
        • IAM Policy
        • IAM Role
        • IAM Root User
        • IAM User
        • KMS Key
        • Lambda Function
        • Password Policy
        • RDS Instance
        • Redshift Cluster
        • Route 53 Domains
        • Route 53 Hosted Zone
        • S3 Bucket
        • WAF Web ACL
  • Alerts & Destinations
    • Alert Destinations
      • Amazon SNS Destination
      • Amazon SQS Destination
      • Asana Destination
      • Blink Ops Destination
      • Custom Webhook Destination
      • Discord Destination
      • GitHub Destination
      • Google Pub/Sub Destination (Beta)
      • Incident.io Destination
      • Jira Cloud Destination
      • Jira Data Center Destination (Beta)
      • Microsoft Teams Destination
      • Mindflow Destination
      • OpsGenie Destination
      • PagerDuty Destination
      • Rapid7 Destination
      • ServiceNow Destination (Custom Webhook)
      • Slack Bot Destination
      • Slack Destination (Webhook)
      • Splunk Destination (Beta)
      • Tines Destination
      • Torq Destination
    • Assigning and Managing Alerts
      • Managing Alerts in Slack
    • Alert Runbooks
      • Panther-managed Policies Runbooks
        • AWS CloudTrail Is Enabled In All Regions
        • AWS CloudTrail Sending To CloudWatch Logs
        • AWS KMS CMK Key Rotation Is Enabled
        • AWS Application Load Balancer Has Web ACL
        • AWS Access Keys Are Used Every 90 Days
        • AWS Access Keys are Rotated Every 90 Days
        • AWS ACM Certificate Is Not Expired
        • AWS Access Keys not Created During Account Creation
        • AWS CloudTrail Has Log Validation Enabled
        • AWS CloudTrail S3 Bucket Has Access Logging Enabled
        • AWS CloudTrail Logs S3 Bucket Not Publicly Accessible
        • AWS Config Is Enabled for Global Resources
        • AWS DynamoDB Table Has Autoscaling Targets Configured
        • AWS DynamoDB Table Has Autoscaling Enabled
        • AWS DynamoDB Table Has Encryption Enabled
        • AWS EC2 AMI Launched on Approved Host
        • AWS EC2 AMI Launched on Approved Instance Type
        • AWS EC2 AMI Launched With Approved Tenancy
        • AWS EC2 Instance Has Detailed Monitoring Enabled
        • AWS EC2 Instance Is EBS Optimized
        • AWS EC2 Instance Running on Approved AMI
        • AWS EC2 Instance Running on Approved Instance Type
        • AWS EC2 Instance Running in Approved VPC
        • AWS EC2 Instance Running On Approved Host
        • AWS EC2 Instance Running With Approved Tenancy
        • AWS EC2 Instance Volumes Are Encrypted
        • AWS EC2 Volume Is Encrypted
        • AWS GuardDuty is Logging to a Master Account
        • AWS GuardDuty Is Enabled
        • AWS IAM Group Has Users
        • AWS IAM Policy Blocklist Is Respected
        • AWS IAM Policy Does Not Grant Full Administrative Privileges
        • AWS IAM Policy Is Not Assigned Directly To User
        • AWS IAM Policy Role Mapping Is Respected
        • AWS IAM User Has MFA Enabled
        • AWS IAM Password Used Every 90 Days
        • AWS Password Policy Enforces Complexity Guidelines
        • AWS Password Policy Enforces Password Age Limit Of 90 Days Or Less
        • AWS Password Policy Prevents Password Reuse
        • AWS RDS Instance Is Not Publicly Accessible
        • AWS RDS Instance Snapshots Are Not Publicly Accessible
        • AWS RDS Instance Has Storage Encrypted
        • AWS RDS Instance Has Backups Enabled
        • AWS RDS Instance Has High Availability Configured
        • AWS Redshift Cluster Allows Version Upgrades
        • AWS Redshift Cluster Has Encryption Enabled
        • AWS Redshift Cluster Has Logging Enabled
        • AWS Redshift Cluster Has Correct Preferred Maintenance Window
        • AWS Redshift Cluster Has Sufficient Snapshot Retention Period
        • AWS Resource Has Minimum Number of Tags
        • AWS Resource Has Required Tags
        • AWS Root Account Has MFA Enabled
        • AWS Root Account Does Not Have Access Keys
        • AWS S3 Bucket Name Has No Periods
        • AWS S3 Bucket Not Publicly Readable
        • AWS S3 Bucket Not Publicly Writeable
        • AWS S3 Bucket Policy Does Not Use Allow With Not Principal
        • AWS S3 Bucket Policy Enforces Secure Access
        • AWS S3 Bucket Policy Restricts Allowed Actions
        • AWS S3 Bucket Policy Restricts Principal
        • AWS S3 Bucket Has Versioning Enabled
        • AWS S3 Bucket Has Encryption Enabled
        • AWS S3 Bucket Lifecycle Configuration Expires Data
        • AWS S3 Bucket Has Logging Enabled
        • AWS S3 Bucket Has MFA Delete Enabled
        • AWS S3 Bucket Has Public Access Block Enabled
        • AWS Security Group Restricts Ingress On Administrative Ports
        • AWS VPC Default Security Group Restricts All Traffic
        • AWS VPC Flow Logging Enabled
        • AWS WAF Has Correct Rule Ordering
        • AWS CloudTrail Logs Encrypted Using KMS CMK
      • Panther-managed Rules Runbooks
        • AWS CloudTrail Modified
        • AWS Config Service Modified
        • AWS Console Login Failed
        • AWS Console Login Without MFA
        • AWS EC2 Gateway Modified
        • AWS EC2 Network ACL Modified
        • AWS EC2 Route Table Modified
        • AWS EC2 SecurityGroup Modified
        • AWS EC2 VPC Modified
        • AWS IAM Policy Modified
        • AWS KMS CMK Loss
        • AWS Root Activity
        • AWS S3 Bucket Policy Modified
        • AWS Unauthorized API Call
    • Tech Partner Alert Destination Integrations
  • Investigations & Search
    • Search
      • Search Filter Operators
    • Data Explorer
      • Data Explorer SQL Search Examples
        • CloudTrail logs queries
        • GitHub Audit logs queries
        • GuardDuty logs queries
        • Nginx and ALB Access logs queries
        • Okta logs queries
        • S3 Access logs queries
        • VPC logs queries
    • Visualization and Dashboards
      • Custom Dashboards (Beta)
      • Panther-Managed Dashboards
    • Standard Fields
    • Saved and Scheduled Searches
      • Templated Searches
        • Behavioral Analytics and Anomaly Detection Template Macros (Beta)
      • Scheduled Search Examples
    • Search History
    • Data Lakes
      • Snowflake
        • Snowflake Configuration for Optimal Search Performance
      • Athena
  • PantherFlow (Beta)
    • PantherFlow Quick Reference
    • PantherFlow Statements
    • PantherFlow Operators
      • Datatable Operator
      • Extend Operator
      • Join Operator
      • Limit Operator
      • Project Operator
      • Range Operator
      • Sort Operator
      • Search Operator
      • Summarize Operator
      • Union Operator
      • Visualize Operator
      • Where Operator
    • PantherFlow Data Types
    • PantherFlow Expressions
    • PantherFlow Functions
      • Aggregation Functions
      • Date/time Functions
      • String Functions
      • Array Functions
      • Math Functions
      • Control Flow Functions
      • Regular Expression Functions
      • Snowflake Functions
      • Data Type Functions
      • Other Functions
    • PantherFlow Example Queries
      • PantherFlow Examples: Threat Hunting Scenarios
      • PantherFlow Examples: SOC Operations
      • PantherFlow Examples: Panther Audit Logs
  • Enrichment
    • Custom Lookup Tables
      • Creating a GreyNoise Lookup Table
      • Lookup Table Examples
        • Using Lookup Tables: 1Password UUIDs
      • Lookup Table Specification Reference
    • Identity Provider Profiles
      • Okta Profiles
      • Google Workspace Profiles
    • Anomali ThreatStream
    • IPinfo
    • Tor Exit Nodes
    • TrailDiscover (Beta)
  • Panther AI (Beta)
    • Managing Panther AI Response History
  • System Configuration
    • Role-Based Access Control
    • Identity & Access Integrations
      • Azure Active Directory SSO
      • Duo SSO
      • G Suite SSO
      • Okta SSO
        • Okta SCIM
      • OneLogin SSO
      • Generic SSO
    • Panther Audit Logs
      • Querying and Writing Detections for Panther Audit Logs
      • Panther Audit Log Actions
    • Notifications and Errors (Beta)
      • System Errors
    • Panther Deployment Types
      • SaaS
      • Cloud Connected
        • Configuring Snowflake for Cloud Connected
        • Configuring AWS for Cloud Connected
        • Pre-Deployment Tools
      • Legacy Configurations
        • Snowflake Connected (Legacy)
        • Customer-configured Snowflake Integration (Legacy)
        • Self-Hosted Deployments (Legacy)
          • Runtime Environment
  • Panther Developer Workflows
    • Panther Developer Workflows Overview
    • Using panther-analysis
      • Public Fork
      • Private Clone
      • Panther Analysis Tool
        • Install, Configure, and Authenticate with the Panther Analysis Tool
        • Panther Analysis Tool Commands
        • Managing Lookup Tables and Enrichment Providers with the Panther Analysis Tool
      • CI/CD for Panther Content
        • Deployment Workflows Using Panther Analysis Tool
          • Managing Panther Content via CircleCI
          • Managing Panther Content via GitHub Actions
        • Migrating to a CI/CD Workflow
    • Panther API
      • REST API (Beta)
        • Alerts
        • Alert Comments
        • API Tokens
        • Data Models
        • Globals
        • Log Sources
        • Queries
        • Roles
        • Rules
        • Scheduled Rules
        • Simple Rules
        • Policies
        • Users
      • GraphQL API
        • Alerts & Errors
        • Cloud Account Management
        • Data Lake Queries
        • Log Source Management
        • Metrics
        • Schemas
        • Token Rotation
        • User & Role Management
      • API Playground
    • Terraform
      • Managing AWS S3 Log Sources with Terraform
      • Managing HTTP Log Sources with Terraform
    • pantherlog Tool
    • Converting Sigma Rules
  • Resources
    • Help
      • Operations
      • Security and Privacy
        • Security Without AWS External ID
      • Glossary
      • Legal
    • Panther System Architecture
Powered by GitBook
On this page
  • Overview
  • Managing alerts in Slack
  • Slack Bot setup video walkthrough
  • How to set up Slack Bot alert destinations in Panther
  • Step 1: Creating your first Slack Bot alert destination in Panther
  • Step 2: Configuring the Slack Bot app in Slack
  • Step 3: Installing Slack Bot
  • Step 4: Configuring Panther Slack App
  • Step 5: Continuing configuration in Panther
  • Step 6: Invite the Panther Slack Bot to your Slack channel
  • Step 7: Finish setup in the Panther Console
  • Step 8 (Optional): Creating additional Slack Bot destinations
  • Additional Information on Destinations

Was this helpful?

  1. Alerts & Destinations
  2. Alert Destinations

Slack Bot Destination

Configuring Panther's Slack Bot as an alert destination in your Panther Console

PreviousServiceNow Destination (Custom Webhook)NextSlack Destination (Webhook)

Last updated 3 months ago

Was this helpful?

Overview

Destinations are integrations that receive alerts from rules, policies, system health notifications, and rule errors. Panther supports configuring a Panther Slack Bot as the destination where you will receive alerts.

Panther's Slack Bot is a Slack application that can send alerts to one or more Slack Channels.

Please note the following:

  • To interact with the alerts, the Slack user email address must match the email address of the user profile defined in Panther.

    • If your email addresses in Slack do not match your Panther Console email addresses, please contact Panther's support team for assistance.

Managing alerts in Slack

Interactions with the Alert within Slack, such as updating the status, setting the assignee, and sending Boomerang messages, will sync back to the Panther Console. In addition, the resolution comment when marking an alert as "Resolved" will sync to Panther's Alert Activity History. Note that this is a one-way sync; changes made to these alerts in the Panther Console will not sync back to Slack.

Slack Bot setup video walkthrough

How to set up Slack Bot alert destinations in Panther

Panther users should have the permissions View Alerts and Manage Alerts to assign alerts and change alert statuses.

Step 1: Creating your first Slack Bot alert destination in Panther

Creating your first Slack Bot alert destination requires the creation of a new Slack Application. Once the initial destination has been created, additional Slack Bot alert destinations will automatically reuse the same Slack Application and its credentials.

  1. Log in to the Panther Console.

  2. In the left sidebar, click Configure > Alert Destinations.

  3. Click +Add your first Destination.

    • If you have already created Destinations, click Create New in the upper right side of the page to add a new Destination.

  4. Click Slack Bot.

Make sure to keep this browser tab open while you begin the next steps.

Step 2: Configuring the Slack Bot app in Slack

  1. Click Next.

  2. Click Next.

    • In the "Request to install Panther" dialog, add an optional message for your Slack administrator to provide context, then click Submit Request.

    • The Basic Information page should now display Request Submitted under the "Install your app" section.

  3. Ask your Slack administrator to approve the install request, but do not install it yet.

    • Once approved, the Request Submitted button will update to Install to Workspace.

Step 3: Installing Slack Bot

Installing the Slack Bot to your Workspace

  1. Click Allow to authorize access to your new app.

    • You will be redirected back to the Basic Information page in Slack.

Installing the Slack Bot on Enterprise Grid

  1. Click Next and follow the series of on-screen prompts.

Step 4: Configuring Panther Slack App

  1. Navigate back to Settings > Basic Information in your Slack App.

    • Select the Panther App Icon you downloaded in the prior step.

Step 5: Continuing configuration in Panther

  1. Open the browser tab where you began configuring the Slack Bot alert destination in the Panther Console.

  2. From the "Create your Slack Bot app" page in the Panther Console where your manifest is displayed, click Continue.

  3. Fill out the form to configure the Destination:

    • Display Name: Enter a descriptive name for the Alert Destination.

      • Note: This is the display name of the Alert Destination in the Panther Console, not the name of the Bot in Slack.

    • Channel ID or Channel Name: Enter the Slack Channel Name (e.g. #hello-world) or Slack Channel ID where you want to receive your alerts.

    • Client ID: Enter the Client ID value from the App Credentials section of your Slack Bot app.

    • Client Secret: Enter the Client Secret value from the App Credentials section of your Slack Bot app.

    • Signing Secret: Enter the Signing Secret value from the App Credentials section of your Slack Bot app.

    • Severity: Select the severity level of alerts to send to this Destination.

    • Alert Types: Select the alert types to send to this Destination.

    • Log Types: By default, we will send alerts from all log types. Specify log types here if you want to only send alerts from specific log types.

    • Timezone: Select the timezone to use for the messages sent to this Destination.

Keep this browser tab open for the next steps.

Step 6: Invite the Panther Slack Bot to your Slack channel

  1. Open your Slack application and navigate to the channel you configured to use with Panther.

  2. In the Slack channel, type and send the following message: /invite @Panther

Step 7: Finish setup in the Panther Console

  1. Navigate back to the Panther Console.

  2. On the final page, optionally click Send Welcome Message to test the integration. This will send a message to the Slack channel you've elected to receive alerts.

  3. When you are finished, click Finish Setup.

Step 8 (Optional): Creating additional Slack Bot destinations

To create an additional Slack Bot alert destination, you don't need to create a new application in your Slack workspace.

  1. In the left sidebar, click Configure > Alert Destinations.

  2. Click Create New in the upper right side of the page to add a new Destination.

  3. Click Slack Bot.

  4. Complete the form, indicating a Display Name and Channel ID or Channel Name.

    • The Client ID, Client Secret, Signing Secret, and Bot OAuth Token are pre-filled based on your existing Slack Bot alert destination.

  5. Click Add Destination.

Additional Information on Destinations

For more information on managing alerts in Slack, see .

Click Copy to copy the Slack Manifest to your clipboard. You will need this in the next steps.

In a separate browser tab, using an administrator account.

In , click Create New App.

In the "Create an app" dialog, select the option From an app manifest.

In the "Pick a workspace to develop your app" dialog, choose the Slack Workspace to install the Slack Bot into.

If your is Enterprise Grid, select a Workspace in the Grid that you wish to have the Slack Bot available. The ability to install into other Workspaces in the Grid will come in a later step.

In the "Enter the app manifest" dialog, click YAML. Paste in the Slack Manifest from the (replacing the pre-populated Demo App example content).

In the "Review summary & create your app" dialog, click Create.

If you are logged in as a Slack administrator, skip to Step 3: . Otherwise, continue below.

On the Basic Information page, click Request to Install.

If your is Enterprise Grid, please see the Enterprise Grid tab below. For all other Slack plans, please see the Non-Enterprise Slack tab below.

On the Basic Information page in Slack, click Install to Workspace.

You will be redirected to the Slack OAuth Authorization page.

Proceed to

On the Basic information page in Slack, expand Manage Distribution and click Distribute App.

Click Opt into Org Level Apps to enable Org-Wide Installation.

Click Opt-in.

Click the checkbox, then click Yes, Opt-in.

Navigate back to Settings > Install App, then click Install to Organization.

Click Allow to authorize access to your new app.

In Slack, you will receive a message indicating the installation was successful. Click the linked text add it to some of your workspaces.

Select the Workspaces you wish to have the Slack Bot installed to. Optionally, you can also select whether you want to automatically add it to future Workspaces:

Once the installation to the Workspace(s) is complete, you will receive a confirmation message in Slack:

When you are finished, proceed to

Download the image to your computer.

Scroll down to the "Display Information" section and click +Add App Icon:

Scroll down to App Credentials section of the Basic Information page. Keep this page open, as you will need this information in the next steps when you finish the configuration in Panther:

If that tab was closed, or if you are not a Slack admin and you submitted a request to install the app, you will need to follow the to get back to the Slack Bot destination setup process in the Panther Console. You will also need to update the manifest of your Slack Bot app to match the latest version from the Panther Console.

Note: If using Slack Enterprise Grid, you must provide the Slack Channel ID. To find the Channel ID, click on the Channel Name in Slack, then scroll to the bottom of the modal:

Bot OAuth Token: Enter the Bot User OAuth Token value from the OAuth & Permissions section of your Slack Bot app:

Once the Panther Slack Bot has been invited to your Slack channel, you will see a confirmation message in Slack and can return to the Panther Console to finalize setup.

On the "Create your Slack Bot Application" page, click Add Destination.

For information on how to view or manage alerts sent to Slack by your new Slack Bot Alert Destination, see .

It's recommended to avoid a Slack Bot alert destination configuration that sends messages for any given alert to more than one channel. For more information, see .

Remember to invite the Panther Bot to the specified channel using /invite @Panther.

For more information on alert routing order, modifying or deleting destinations, and workflow automation, please see the Panther docs: .

Managing Alerts in Slack
log in to Slack
Slack - Your Apps
Slack plan
Slack plan
Panther App Icon
Triaging Alerts - Slack Bot
Destinations
Installing the Slack Bot
Step 4 - Configuring Panther Slack App.
Step 4 - Configuring Panther Slack App.
previous steps
previous steps
Video walkthrough for setting up Panther's Slack Bot alert destination integration.
Managing Alerts in Slack