stack kb security-detections-api find-rules cli command
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability 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. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability 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.
Serverless
Preview
Preview
Stack
Preview
Preview
elastic stack kb security-detections-api find-rules [options]
List all detection rules
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--fieldsstring[]-
List of
alert.attributesfield names to return for each rule (for examplename,enabled). If omitted, the default field set is returned. Repeat the parameter to pass multiple field names, or use comma-separated values when supported by your client.Repeatable: pass
--fieldsmultiple times to supply more than one value --filterstring-
Search query Filters the returned results according to the value of the specified field, using the alert.attributes.<field name>:<field value> syntax, where <field name> can be:
- name
- enabled
- tags
- createdBy
- interval
- updatedBy
info Even though the JSON rule object uses created_by and updated_by fields, you must use createdBy and updatedBy fields in the filter.
--sort-fieldenum-
Field to sort by
Values: created_at, createdAt, enabled, execution_summary.last_execution.date, execution_summary.last_execution.metrics.execution_gap_duration_s, execution_summary.last_execution.metrics.total_indexing_duration_ms, execution_summary.last_execution.metrics.total_search_duration_ms, execution_summary.last_execution.status, name, risk_score, riskScore, severity, updated_at, updatedAt
--sort-orderenum-
Sort order
Values: asc, desc
--pagenumber- Page number
--per-pagenumber- Rules per page
--gaps-range-startstring- Gaps range start
--gaps-range-endstring- Gaps range end
--gap-fill-statusesstring[]-
Gap fill statuses
Repeatable: pass
--gap-fill-statusesmultiple times to supply more than one value --gap-auto-fill-scheduler-idstring- Gap auto fill scheduler ID used to determine gap fill status for rules
--input-filestring- path to a JSON file to use as command input
--dry-run- validate all inputs and exit without performing any action (preview changes without applying them)
--no-validate- skip input validation and send the request as-is
--output-fieldsstring- comma-separated list of fields to include in output (dot-notation supported)
--output-templatestring- Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json-
output as JSON