Spyderbat
Book a DemoStart FreeContact Us
  • Spyderbat Product Docs
  • Getting Started
    • Create an Organization
    • Install the Nano Agent
    • Three Things to Try with Spyderbat Community Edition
    • Manage Users and Roles
  • Installation
    • Spyderbat Nano Agent
      • Kubernetes
        • Pre Deployment Environment Data Collection Script
      • Linux Standalone
      • AWS Unattended Install
        • Secure your Registration Code with AWS Secrets Manager
      • Create a Golden Image with the Nano Agent Pre-Installed
    • Spyderbat AWS Agent
      • AWS Linux VM
      • Kubernetes
      • Configuration Guide - AWS Linux VM
      • Configuration Guide - Kubernetes
    • Install Spyctl CLI
      • Initial Configuration
    • Install Spydertop CLI
    • Install the Spyderbat Event Forwarder
      • Helm Chart
      • Traditional Installer
  • Concepts
    • Guardian & Interceptor
      • Ruleset Policies
      • Workload Policies
    • Flashback (Go Back In Time)
      • Investigations
    • Search
      • Saved Searches
    • Summarize
      • Spydertrace Summarize
    • Dashboards
      • Dashboard Categories
    • Reports
    • Notifications
      • Notification Targets
      • Notification Templates
    • Actions
    • Integrations
      • AWS Integration
      • Spyderbat Event Forwarder
    • Suppression & Tuning
    • Scout (Detections)
      • Custom Flags
  • Tutorials
    • Flashback
      • How to Use the Investigations Feature in Spyderbat
    • Guardian
      • How to Lock Down Your Workloads With Guardian Policies Using Spyctl
      • How to Put Guardrails Around Your K8s Clusters Using Spyctl
    • Integrations
      • How to Configure Event Forwarder Webhook for Panther
      • How to Set Up Spyderbat to Ingest Falco Alerts
      • How to Create and Use a Spyderbat API Key
    • Notifications
      • How to Set Up Notifications Using Spyctl
      • How to Set up Agent-Health Notifications Using Spyctl
    • Dashboards
    • Miscellaneous
      • How to Set Up Spyderbat to Monitor Systems From vulnhub.com
    • Scout (Detections)
      • How to Set Up Custom Flags Using Spyctl CLI
  • Reference
    • Policies
      • Response Actions
    • Rulesets
    • Selectors
    • Notifications
    • Spyctl CLI
      • Spyctl Commands
      • Guardian Policy Management using Spyctl
      • Notification Template Management using Spyctl
      • Notification Target Management using Spyctl
    • Search
      • All Operators
      • All Fields
      • All Related Objects
  • Quick Links
    • Contact Us
    • Try Spyderbat for Free
    • Book a Demo
Powered by GitBook

© SPYDERBAT, Inc., All Rights Reserved

On this page
  • Panther schema configuration
  • Panther log source configuration
  • Event forwarder configuration
  • Configure your API key and org UUID
  • Add a filter expression such as the one below to capture relevant data
  • Add a webhook configuration

Was this helpful?

Export as PDF
  1. Tutorials
  2. Integrations

How to Configure Event Forwarder Webhook for Panther

Last updated 1 year ago

Was this helpful?

This is not meant to be a comprehensive guide to use the event forwarder with Panther.

Panther schema configuration

Panther requires an ingestion schema to ingest log data. An example schema is provided

Download the example schema. In the Panther console, under Configure / Schemas, click "Create New" and give the schema a name, such as SpyderbatR0.

Paste the contents of the example schema in the text box. Validate the schema, then save it.

Panther log source configuration

Configure a log source in Panther. In the Panther console, under Configure / Log Sources, click "Create New" and select "custom log formats."

Next, click "Start" under the category for HTTP logs.

Give the source a name, e.g. Spyderbat Forwarder on HOST_NAME (32 chars max)

Select the Custom.SpyderbatR0 schema created in the previous step.

Set the auth method to Bearer and click the refresh button to generate a bearer secret. Then copy the secret.

NOTE: Once you leave this screen, the secret cannot be retrieved again; It must be replaced.

Click the "Setup" button.

The bearer secret must be converted to base64. An easy way to do this with the Unix shell is to type:

echo -n YOUR_SECRET | base64

Keep this base64 secret handy for the webhook configuration step.

Event forwarder configuration

Edit the /opt/spyderbat-events/etc/config.yaml configuration file.

Configure your API key and org UUID

spyderbat_org_uid and spyderbat_secret_api_key must be valid. Note that API keys are scoped to a user and not an org; It is recommended to create a service user in the Spyderbat UI, grant it access to the appropriate org, and generate the API key for the service user. API keys expire after 1 year; Plan ahead to keep the key updated.

Add a filter expression such as the one below to capture relevant data

expr: |
    schema startsWith "model_spydertrace:"
    and suppressed == false
    and (
        (score ?? 0) > 50
        or len(policy_name ?? "") > 0
    )

Add a webhook configuration

Your panther source will have an HTTP Ingest URL associated with it. Retrieve it and the secret you created earlier on, and add the webhook configuration:

webhook:
  endpoint_url: PANTHER_INGEST_URL
  compression_algo: zstd
  max_payload_bytes: 500000
  authentication:
    method: bearer
    parameters:
      secret_key: YOUR_BASE64_SECRET

Save config.yaml file and restart the event forwarder:

sudo sytemctl restart spyderbat-event-forwarder.service

Tail the logs to check for errors:

sudo journalctl -fu spyderbat-event-forwarder.service

Here