elastic / elastic/detection-rules
[New Rule] An anomaly was detected with a Slack user
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 696
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 87
Description
### Description
Slack has built-in anomaly detection for various suspicious events occurring around user accounts or the application. This detects the occurrence of the most concerning anomalous events.
### Target Ruleset
other
### Target Rule Type
ES|QL
### Tested ECS Version
_No response_
### Query
```sql
from logs-slack.audit*
| where event.action == "anomaly" and not slack.audit.details.reason == "ip_address"
| eval rule_name = concat("Slack Anomaly Detected: ", slack.audit.details.reason)
```
The rule name override would then need to be set for `rule_name`. This is immensely helpful in managing and triaging this alert.
### New fields required in ECS/data sources for this rule?
`slack.*`
### Related issues or PRs
_No response_
### References
* https://api.slack.com/admins/audit-logs-call#app
* https://api.slack.com/admins/audit-logs-anomaly
### Redacted Example Data
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.