GitHub Audit Log: Self-Hosted Runner Configuration Changes

Alerts on GitHub audit log events indicating self-hosted runner registration and runner group configuration changes.

FreeReviewedSigma · Low · v5

Product: github
Service: audit
Author: Muhammad Faisal (@faisalusuf) (SigmaHQ), DRL 1.1
Published: 2023-01-27
Updated: 2026-07-31

ATT&CK techniques

Initial Access → Collection

Recon
Resource Dev
Initial Access
- T1078.004Cloud Accounts
Execution
Persistence
- T1078.004Cloud Accounts
Priv Esc
- T1078.004Cloud Accounts
Defense Evasion
- T1078.004Cloud Accounts
Cred Access
Discovery
- T1526Cloud Service Discovery
Lateral Movement
Collection
- T1213.003Code Repositories
C2
Exfiltration
Impact

What it detects

This rule identifies events in the GitHub audit log related to registering/removing self-hosted runners and creating/updating/removing runner groups, including changes to runners within those groups. Such changes matter because they can alter which systems execute GitHub Actions jobs and may be used to establish persistence or privilege-related impact via runner access. It relies on audit-log telemetry capturing the specific organization and repository actions listed by the rule.

Reporting behind it

Related detections9 linkedT1078.004 — drag to rearrange

Suspicious Azure OpenAI Model Enumeration and Deployment Creation (via azure)

Suspicious S3 Access from Desktop File Transfer Clients by Bling Libra

Malicious AWS Cross-Account AssumeRole With Suspicious Session Names via CloudTrail (via aws)

Suspicious Okta SSO Access to Many Applications in Short Window

Suspicious Microsoft Entra Device Code Authentication Flow

Suspicious M365 Password Spraying via Azure PowerShell AppId from Quad7 Botnet

Suspicious AWS Instance Access or Export via SSH Key or Export Task

Suspicious Azure Cognitive Services Account Key Enumeration via ListKeys (via azure)

Malicious Business Email Compromise OAuth Application Sign-In via Entra ID Service Principal (via azure)

GitHub Audit Log: Self-Hosted Runner Configuration Changes

Pivot detection · T1078.004 · 9 related

Changelog

v5
Candidate ingested via manual entry.2026-07-31
v4
Candidate ingested via manual entry.2026-07-31
v3
Candidate ingested via manual entry.2026-07-31
v2
Candidate ingested via manual entry.2026-07-31
v1
No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.

github-audit-log-self-hosted-runner-configuration-change-alerts-f8ed0e8f

title: "GitHub Audit Log: Self-Hosted Runner Configuration Changes"
id: ef1d7694-a36d-409f-9215-89abca6e3790
status: test
description: This rule identifies events in the GitHub audit log related to registering/removing self-hosted runners and creating/updating/removing runner groups, including changes to runners within those groups. Such changes matter because they can alter which systems execute GitHub Actions jobs and may be used to establish persistence or privilege-related impact via runner access. It relies on audit-log telemetry capturing the specific organization and repository actions listed by the rule.
author: Muhammad Faisal (@faisalusuf), Huntrule Team
date: 2023-01-27
references:
  - https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners
  - https://docs.github.com/en/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#search-based-on-operation
  - https://github.com/SigmaHQ/sigma/blob/master/rules/application/github/audit/github_self_hosted_runner_changes_detected.yml
tags:
  - attack.impact
  - attack.discovery
  - attack.collection
  - attack.persistence
  - attack.privilege-escalation
  - attack.initial-access
  - attack.stealth
  - attack.t1526
  - attack.t1213.003
  - attack.t1078.004
logsource:
  product: github
  service: audit
  definition: "Requirements: The audit log streaming feature must be enabled to be able to receive such logs. You can enable following the documentation here: https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise#setting-up-audit-log-streaming"
detection:
  selection:
    action:
      - org.remove_self_hosted_runner
      - org.runner_group_created
      - org.runner_group_removed
      - org.runner_group_runner_removed
      - org.runner_group_runners_added
      - org.runner_group_runners_updated
      - org.runner_group_updated
      - repo.register_self_hosted_runner
      - repo.remove_self_hosted_runner
  condition: selection
falsepositives:
  - Allowed self-hosted runners changes in the environment.
  - A self-hosted runner is automatically removed from GitHub if it has not connected to GitHub Actions for more than 14 days.
  - An ephemeral self-hosted runner is automatically removed from GitHub if it has not connected to GitHub Actions for more than 1 day.
level: low
license: DRL-1.1
related:
  - id: f8ed0e8f-7438-4b79-85eb-f358ef2fbebd
    type: derived

Convert

This rule as a query you can run. Uses no unlock credit.

SplunkSPL