stack kb security-attack-discovery-api post-attack-discovery-generate cli command
Auth required
elastic stack kb security-attack-discovery-api post-attack-discovery-generate \
--alerts-index-pattern <alerts-index-pattern> \
--anonymization-fields <anonymization-fields> \
--api-config <api-config> \
--size <size> \
--sub-action <sub-action> \
[options]
Generate attack discoveries from alerts
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--alerts-index-patternstringrequired- The (space specific) index pattern that contains the alerts to use as context for the attack discovery. Example: .alerts-security.alerts-default
--anonymization-fieldsstring[]required-
The list of fields, and whether or not they are anonymized, allowed to be sent to LLMs. Consider using the output of the
/api/security_ai_assistant/anonymization_fields/_findAPI (for a specific Kibana space) to provide this value.Repeatable: pass
--anonymization-fieldsmultiple times to supply more than one value --api-configstringrequired- LLM API configuration.
--sizenumberrequired--sub-actionenumrequired-
Values: invokeAI, invokeStream
--connector-namestring--endstring--filterstring-
An Elasticsearch-style query DSL object used to filter alerts. For example:
} ```
--modelstring--replacementsstring--startstring--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)
--json-
output as JSON