Destinations

Destinations are used to deliver alerts to your team.

When a policy fails or a rule triggers, an alert is generated with basic context and sent to the configured destination.

Alerts are routed based on severity and a single alert can dispatch to multiple destinations simultaneously, such as creating a Jira ticket, sending an email, and creating a PagerDuty Incident.

Destinations can also be overridden on a per-rule or per-policy basis.

AWS destinations require IAM configurations to grant permissions for Panther to publish notifications

Supported Destinations

Creating a New Destination

To create a destination, navigate to Settings > Destinations and select Add Destination.

You will then be prompted to select a destination type.

Multiple destinations of the same type may be configured, such as several Slack channels or email addresses. This allows for fine grained control of destination routing.

Next, add a Display Name to distinguish the destination from others in the Panther UI and select the associated severities for this destination.

Each destination type will have specific configuration options based on the system's API. See the destination specific setup instructions in the following pages for more details.

Finally, click the Add Destination button to save the configuration. You are now ready to receive alerts!

Modifying or Deleting Destinations

An existing destination may be modified or deleted by selecting the triple dot button. From here, you can modify the display name, the severities, and the specific configurations. Alternatively, you can also delete the destination.