Expand description
Security detection rules. These are distinct from generic Kibana alerting rules.
QueryRule creates KQL or Lucene rules; other rule types can use JSON with
Security::create_rule. Use RuleSelector to distinguish a saved-object
ID from the stable rule ID. Imports can succeed for rules while failing for
their dependencies; inspect RuleImportResult before treating the import
as complete.
Structs§
- Create
Alerts Index POST /api/detection_engine/index- Create
Rule POST /api/detection_engine/rules- Delete
Rule DELETE /api/detection_engine/rules- Detection
Rule - A detection rule returned by Kibana. Type-specific fields are retained in
extra. - Export
Rules POST /api/detection_engine/rules/_export- Find
Rules GET /api/detection_engine/rules/_find- GetPrivileges
GET /api/detection_engine/privileges- GetRule
GET /api/detection_engine/rules- Import
Rules POST /api/detection_engine/rules/_import- Patch
Rule PATCH /api/detection_engine/rules- Query
Rule - A KQL or Lucene query rule. Rules start disabled unless explicitly enabled.
- Risk
Score - A detection rule’s risk score, from 0 to 100.
- Rule
Execution - The latest execution health. A successful execution need not have produced alerts.
- Rule
Execution Summary - Rule
Import Result - HTTP 200 can contain failed imports.
successcovers only rules; inspect exception and connector outcomes separately. - Rule
Page - Rule
Schedule - When a rule runs and how far back each run searches.
- Security
Enums§
- Query
Language - Rule
Selector - Selects a rule by saved-object
idor by its stablerule_id. - Severity