
Summary
Detects when a GitHub Actions workflow run is deleted within 30 minutes of its creation by correlating workflows.created_workflow_run and workflows.delete_workflow_run events for the same organization, repository, and workflow_id. Since GitHub does not always emit a separate event for log deletion, the rule treats the actual run deletion as a reliable cover-up signal. The ES|QL query aggregates creations and deletions by github.org, github.repo, and github.data.workflow_id, recording created_at and deleted_at and computing time_diff_seconds (time between creation and deletion). It flags cases where a run is created and deleted within 0–1800 seconds and where the deletion occurs within 10 minutes of ingestion. This behavior is mapped to MITRE ATT&CK TA0005 (Defense Evasion) and T1070 (Indicator Removal). The rule surfaces actors and context (user.name, github.actor_ip, github.user_agent, github.data.workflow_run_id, workflow_id, etc.) for investigation and supports incident triage with correlated timestamps and host/service indicators. False positives include legitimate admin pruning of CI history or automated cleanup of runs. Recommended responses include disabling the suspect workflow, rotating secrets used by Actions, reviewing commits to .github/workflows, restricting GITHUB_TOKEN permissions, and preserving remaining logs and audit events for incident response.
Categories
- Cloud
- Web
- Application
Data Sources
- Cloud Service
- Application Log
ATT&CK Techniques
- T1070
Created: 2026-11-17