Type to search.

Schedule runs from the Attacks view

Serverless Security

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Stack GA 9.5+ …

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available since 9.5

    This functionality is generally available and ready for production usage.

  • Preview in 9.4

    This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Create a schedule so Attack Discovery runs automatically at intervals you choose. From the Attacks view, define how often analysis runs, which alerts to include, and optionally notify your team when discoveries are found.

Important

After you turn on securitySolution:enableAttackDiscoveryWorkflows, existing schedules keep their previous configuration until you edit and save them. Each scheduled run also opens a new Elastic Agent Builder conversation you can view later from Workflow execution details.

To create a schedule:

  1. Go to Detections → Views → Attacks, then select Schedule → Create new schedule.
  2. Name the schedule and choose an LLM connector for generation. If you don't already have one, refer to Configure access to LLMs.
  3. Configure which alerts to analyze. For example, keep skill retrieval on and add an ES|QL query to focus on high-severity alerts.
  4. Set how often the schedule runs, such as every 24 hours.
  5. (Optional) Add notification connectors and actions, then select Create & enable schedule. Supported notification connectors include Slack, ServiceNow, Jira, PagerDuty, Cases, Email, and Webhook.

To create a schedule:

  1. Go to Detections → Views → Attacks, then select Schedule → Create new schedule.
  2. Name the schedule and choose an LLM connector for generation. If you don't already have one, refer to Configure access to LLMs.
  3. Configure which alerts to analyze.
  4. Set how often the schedule runs, such as every 24 hours.
  5. (Optional) Add notification connectors and actions, then select Create & enable schedule. For example, send a Slack or email notification when discoveries are found.

After creating a schedule, you can edit, enable, disable, or delete it. To change several at once, select them in the table and use Bulk actions. To manage schedules programmatically, use the Attack discovery API.

Scheduled discoveries show a calendar icon. For how to recognize scheduled versus manually generated attacks, refer to Recognize manually generated and scheduled attacks.