<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GitHub Forensics — Blog</title>
    <link>https://www.githubforensics.com/en/blog</link>
    <description>Latest from Blog</description>
    <language>en</language>
    <lastBuildDate>Sun, 27 Sep 2026 20:41:49 GMT</lastBuildDate>
    <atom:link href="https://www.githubforensics.com/en/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>GitHub audit log limitations: retention, gaps, plans</title>
      <link>https://www.githubforensics.com/en/blog/github-audit-log-limitations</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/github-audit-log-limitations</guid>
      <description>What the GitHub audit log does not record: 180-day and 7-day retention, plan limits for API and Git events, hidden IPs, no file contents or secret reads.</description>
      <author>Florian Amette</author>
      <pubDate>Sun, 27 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GitHub supply chain attack investigation: a walkthrough</title>
      <link>https://www.githubforensics.com/en/blog/github-supply-chain-attack-investigation</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/github-supply-chain-attack-investigation</guid>
      <description>A fictional GitHub supply chain attack investigated end to end: stolen PAT, 38 repos cloned, AWS keys printed by a workflow, branch protection removed.</description>
      <author>Florian Amette</author>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Leaked cloud keys in GitHub Actions: the cloud pivot</title>
      <link>https://www.githubforensics.com/en/blog/leaked-cloud-keys-github-actions</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/leaked-cloud-keys-github-actions</guid>
      <description>AWS, Google Cloud or Azure keys leaked from GitHub Actions or a repo: contain the key, trace its use in the cloud audit logs, then replace keys with OIDC.</description>
      <author>Florian Amette</author>
      <pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Branch protection disabled? Auditing GitHub rulesets</title>
      <link>https://www.githubforensics.com/en/blog/branch-protection-ruleset-tampering</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/branch-protection-ruleset-tampering</guid>
      <description>Investigate GitHub branch protection or ruleset tampering: protected_branch.destroy, ruleset changes, admin overrides, environments, and what landed meanwhile.</description>
      <author>Florian Amette</author>
      <pubDate>Sat, 19 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GitHub org takeover: owners, 2FA, SSO and IP allow list</title>
      <link>https://www.githubforensics.com/en/blog/github-organization-takeover</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/github-organization-takeover</guid>
      <description>GitHub organization takeover indicators in the audit log: new owners, 2FA requirement off, SAML SSO changed, IP allow list off, audit streaming removed.</description>
      <author>Florian Amette</author>
      <pubDate>Thu, 17 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Self-hosted runner security: GitHub Actions forensics</title>
      <link>https://www.githubforensics.com/en/blog/self-hosted-runner-security</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/self-hosted-runner-security</guid>
      <description>Rogue or compromised GitHub self-hosted runners: the audit log events to check, host evidence in _diag, and how to scope and rebuild after an incident.</description>
      <author>Florian Amette</author>
      <pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GitHub Actions secrets leak: investigating exfiltration</title>
      <link>https://www.githubforensics.com/en/blog/github-actions-secrets-leak</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/github-actions-secrets-leak</guid>
      <description>How GitHub Actions secrets leak despite *** masking: poisoned workflows, new branches, encoded output and third-party actions. The evidence to collect and read.</description>
      <author>Florian Amette</author>
      <pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Detecting GitHub repo exfiltration and mass cloning</title>
      <link>https://www.githubforensics.com/en/blog/github-repository-exfiltration</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/github-repository-exfiltration</guid>
      <description>Find source code theft in the GitHub audit log: git.clone bursts, ZIP archive downloads, repos made public or transferred, forks, and what each leaves behind.</description>
      <author>Florian Amette</author>
      <pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Leaked GitHub token: what to do and how to investigate</title>
      <link>https://www.githubforensics.com/en/blog/leaked-github-token</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/leaked-github-token</guid>
      <description>A GitHub PAT or OAuth token leaked? Revoke it, find its hashed_token in the audit log, check new IPs, countries and clones, then scope what the token reached.</description>
      <author>Florian Amette</author>
      <pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GitHub audit log analysis: step-by-step in your browser</title>
      <link>https://www.githubforensics.com/en/blog/github-audit-log-analysis</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/github-audit-log-analysis</guid>
      <description>Analyze GitHub audit log exports offline: drop JSON, Git events and Actions logs, read the verdict, triage findings, pivot on tokens and IPs, export a report.</description>
      <author>Florian Amette</author>
      <pubDate>Sat, 05 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to export the GitHub audit log (UI, API, streaming)</title>
      <link>https://www.githubforensics.com/en/blog/export-github-audit-log</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/export-github-audit-log</guid>
      <description>Export the GitHub audit log for forensics: UI JSON/CSV, REST API with include=all, streaming files, Git events and Actions logs, with the limits of each source.</description>
      <author>Florian Amette</author>
      <pubDate>Thu, 03 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GitHub organization compromised? Incident response guide</title>
      <link>https://www.githubforensics.com/en/blog/github-organization-compromised</link>
      <guid isPermaLink="true">https://www.githubforensics.com/en/blog/github-organization-compromised</guid>
      <description>What to do when your GitHub organization is compromised: preserve the audit log, contain tokens and workflows, scope with Git events, then pivot to the cloud.</description>
      <author>Florian Amette</author>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>