1. Resources
  2. Detection rules
  3. GitHub Audit Log Streaming Deleted or Paused

GitHub Audit Log Streaming Deleted or Paused detection rules

An enterprise owner deletes, pauses or redirects the enterprise audit log stream, cutting the SIEM off from GitHub activity so later actions go unseen or arrive too late to act on.

Platform
GitHub
Severity
High
Log source
GitHub audit log
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
Control of an enterprise owner account on GitHub Enterprise Cloud, the role that can pause, reconfigure or delete the audit log stream.
Impact
Loss or delay of the audit trail for every organization in the enterprise, which hides follow-on actions and weakens incident response.
Response
Restore the stream to the correct destination, resuming a paused stream within seven days, and secure the enterprise owner account that made the change.
Mitigation
Collect GitHub audit events through a second path such as the audit log API, or alert when no GitHub events arrive within an expected interval.
Audit actions
business.disable_source_ip_disclosureaudit_log_streaming.destroyaudit_log_streaming.update
Threat groups
APT29

How the attack works

GitHub Enterprise Cloud can stream audit and Git events for every organization in an enterprise to a SIEM or storage endpoint such as Splunk, Azure Event Hubs, Amazon S3, Google Cloud Storage or Datadog. Enterprise owners can set up, pause, reconfigure or delete the stream at any time. A paused stream buffers events for seven days; a deleted stream exports nothing until it is set up again.

An attacker who controls an enterprise owner account can delete the stream before acting, pause it to delay detection, or point it at a destination they control. If the stream is the SIEM's only GitHub feed, the deletion event itself may never arrive, so this rule works best with logs collected through the audit log API (as the Microsoft Sentinel GitHub Enterprise Audit Log connector built on the Codeless Connector Framework does) or alongside a "no GitHub events received" health alert. A smaller change reduces what the events say instead of where they go: an enterprise owner can switch off the display of source IP addresses in the audit log, which GitHub records as business.disable_source_ip_disclosure.

What an attacker needs

  • Control of an enterprise owner account on GitHub Enterprise Cloud.

Impact

Loss or delay of the audit trail for every organization in the enterprise, which hides follow-on actions such as owner changes, token approvals, branch protection removal and repository exposure, and weakens incident response.

Detection rules

GitHub Audit Log Source IP Disclosure Disabled

Detects the display of IP addresses in the enterprise audit log being switched off (business.disable_source_ip_disclosure, which GitHub describes as the display of IP addresses within audit log events for the enterprise that was disabled). GitHub does not show source IP addresses in the audit log by default, and an enterprise enables the display to respond to threats. Switching it off leaves the events in place but takes the address of the actor out of them, in the enterprise audit log and in the audit log of every organization the enterprise owns, so later activity cannot be tied to a network location.

LevelMediumStatusExperimentalLog sourceGitHub audit log
title: GitHub Audit Log Source IP Disclosure Disabled
id: f174f2cf-104c-44be-8abb-0b85e810eb93
status: experimental
description: >-
  Detects the display of IP addresses in the enterprise audit log being
  switched off (business.disable_source_ip_disclosure, which GitHub
  describes as the display of IP addresses within audit log events for the
  enterprise that was disabled). GitHub does not show source IP addresses
  in the audit log by default, and an enterprise enables the display to
  respond to threats. Switching it off leaves the events in place but takes
  the address of the actor out of them, in the enterprise audit log and in
  the audit log of every organization the enterprise owns, so later
  activity cannot be tied to a network location.
references:
  - https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise
  - https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise
  - https://attack.mitre.org/techniques/T1685/002/
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.t1685.002
logsource:
  product: github
  service: audit
detection:
  selection:
    action: business.disable_source_ip_disclosure
  condition: selection
falsepositives:
  - An enterprise that stops displaying IP addresses for a legal or privacy reason. GitHub notes that the enterprise is responsible for the legal obligations that come with viewing or storing them, so confirm the decision with the security and privacy owners.
level: medium

False positives

  • An enterprise that stops displaying IP addresses for a legal or privacy reason. GitHub notes that the enterprise is responsible for the legal obligations that come with viewing or storing them, so confirm the decision with the security and privacy owners.

GitHub Audit Log Streaming Endpoint Deleted

Detects an enterprise owner deleting an audit log streaming endpoint, which stops audit and Git events for every organization in the enterprise from reaching that destination.

LevelHighStatusExperimentalLog sourceGitHub audit log
title: GitHub Audit Log Streaming Endpoint Deleted
id: 950e39c9-d903-419a-9e86-d5ec29f23925
status: experimental
description: >-
  Detects an enterprise owner deleting an audit log streaming endpoint, which
  stops audit and Git events for every organization in the enterprise from
  reaching that destination.
references:
  - https://attack.mitre.org/techniques/T1685/002/
  - https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise
author: Forestall
date: 2026-11-10
tags:
  - attack.defense-impairment
  - attack.t1685.002
logsource:
  product: github
  service: audit
detection:
  selection:
    action: audit_log_streaming.destroy
  condition: selection
falsepositives:
  - Planned migration to a new SIEM or storage destination; a matching audit_log_streaming.create event for the new endpoint usually follows.
level: high

False positives

  • Planned migration to a new SIEM or storage destination; a matching audit_log_streaming.create event for the new endpoint usually follows.

GitHub Audit Log Streaming Configuration Changed

Detects a change to an audit log streaming endpoint, such as the stream being paused or disabled or its destination being changed. A paused stream delays delivery; a changed destination can send the enterprise's audit events somewhere the defenders do not watch.

LevelMediumStatusExperimentalLog sourceGitHub audit log
title: GitHub Audit Log Streaming Configuration Changed
id: 111aa598-0ef4-4059-b1e0-20f7d0615931
status: experimental
description: >-
  Detects a change to an audit log streaming endpoint, such as the stream
  being paused or disabled or its destination being changed. A paused stream
  delays delivery; a changed destination can send the enterprise's audit
  events somewhere the defenders do not watch.
references:
  - https://attack.mitre.org/techniques/T1685/002/
  - https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise
  - 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
author: Forestall
date: 2026-11-10
tags:
  - attack.defense-impairment
  - attack.t1685.002
logsource:
  product: github
  service: audit
detection:
  selection:
    action: audit_log_streaming.update
  condition: selection
falsepositives:
  - Maintenance on the receiving system (pause and resume) or credential rotation for the destination; confirm with the team that owns the SIEM pipeline.
level: medium

False positives

  • Maintenance on the receiving system (pause and resume) or credential rotation for the destination; confirm with the team that owns the SIEM pipeline.

Detection logic

Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.

Stream delivers fewer events than the audit log API returns for the same hours

Detection hypothesisJoins two logsNeeds a baseline

A deleted or redirected stream can also stop the event that records the change, so a rule that reads the stream alone may stay silent. GitHub keeps the enterprise audit log for 180 days and serves it through the REST API whatever happens to the stream. Comparing what the API returns with what the stream delivered for the same hours shows a stream that stopped or was thinned out, even when no change event ever arrives.

  1. Collect the enterprise audit log a second time through the REST API endpoint for the enterprise audit log, which returns web events by default and Git events only when asked for them.
  2. For each closed hour, count the events of the API copy and of the stream, separately for web and Git events.
  3. Alert when the API copy holds events for an hour in which the stream delivered none, or clearly fewer than its usual share.
  4. Search the API copy around the start of the gap for audit_log_streaming.destroy, audit_log_streaming.update and business.disable_source_ip_disclosure, and read the actor.

Eventsaudit_log_streaming.destroyaudit_log_streaming.updatebusiness.disable_source_ip_disclosure

LimitsStreams deliver with a delay, and a paused stream sends its buffered events when it is resumed, so compare hours only after a margin. A small enterprise has quiet hours on both paths. GitHub keeps Git events for seven days only, so the Git comparison has to run within that time. The margin and the share are starting points.

Triage

  • Identify the enterprise owner who made the change (actor) and the stream and destination involved (audit_log_stream_sink, audit_log_stream_sink_details).
  • For updates, compare the old and new destination fields to spot a redirected stream.
  • If unexplained, restore the stream, review the actor's activity in the GitHub audit log for the gap, and reset that owner's credentials.

Response

Once the attack is confirmed:

  1. Restore the stream to the correct destination. Resume a paused stream within seven days, because GitHub buffers its events only for that long.
  2. Secure the enterprise owner account that made the change. Reset its password and second factor, end its sessions and revoke its tokens and SSH keys.
  3. Fill the gap in the SIEM from GitHub itself by exporting the enterprise audit log for the period through the audit log API or the web interface. Do it early, because GitHub lists audit events for the last 180 days and keeps Git events for seven days.
  4. Go through the exported events for what the gap was meant to hide, in particular owner changes, token approvals, app installations, branch protection removal and repository visibility changes, and respond to each.
  5. If the destination was changed, treat the events that were sent to the foreign endpoint as disclosed, and find out who controls it.

Mitigation

  • Keep the number of enterprise owners small and require phishing-resistant two-factor authentication for them.
  • Collect GitHub audit events through a second path (the audit log API) or alert when no GitHub events arrive within an expected interval.
  • Alert on every change to audit log streaming and confirm it with the enterprise's security owners.

Frequently asked questions

Why did the alert for the deleted stream never arrive in our SIEM?

If the stream is the SIEM's only GitHub feed, deleting it stops delivery, and the event that records the deletion may never be exported. The rule works best when GitHub audit events are also collected through the audit log API, or next to a health alert that fires when no GitHub events have arrived within an expected interval.

What is lost when a stream is paused, compared with deleted?

A paused stream keeps a buffer for seven days and exports the stored events when it is resumed, so a short pause delays detection without losing events. A deleted stream exports nothing until a new one is set up. In both cases the events can still be searched in GitHub's own audit log, which lists the last 180 days.

Who can change the audit log stream, and how far does one change reach?

Enterprise owners on GitHub Enterprise Cloud can set up, pause, reconfigure or delete the stream at any time. One stream carries the audit and Git events of every organization in the enterprise, so a single change by one enterprise owner affects the visibility of all of them.

Is a redirected stream more serious than a deleted one?

It can be. A deleted stream cuts the SIEM off. A stream that is pointed at a destination the attacker controls cuts the SIEM off as well and also hands the enterprise's audit events to whoever runs that destination. Compare the old and new destination fields of every `audit_log_streaming.update` event.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.