Daily Firewall Report - 2026-03-26 #23106
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Daily Firewall Logs Collector and Reporter. A newer discussion is available at Discussion #23226. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🔥 Daily Firewall Activity Report for March 26, 2026
This report covers all agentic workflow runs with the network firewall enabled over the past 7 days. Today's analysis detected 170 blocked requests across 4 affected workflows — with one workflow (Changeset Generator) responsible for 87.6% of all blocked traffic, largely due to legitimate GitHub domains being denied. All blocked traffic originated from the Codex engine.
Key Metrics
Top Blocked Domains
raw.githubusercontent.com:443ab.chatgpt.com:443github.com:443codeload.github.com:443release-assets.githubusercontent.com:443📈 Firewall Activity Trends
Request Patterns by Workflow
The chart reveals that most workflows operate cleanly with zero blocked requests. The Changeset Generator stands out significantly — it generated 149 of 170 total blocked requests (87.6%), indicating a specific allowlist misconfiguration. All blocked traffic is concentrated in Codex-engine workflows.
Top Blocked Domains
raw.githubusercontent.comdominates with 115 blocks — a GitHub-owned CDN that should be permitted. Theab.chatgpt.comdomain is an OpenAI telemetry endpoint consistently called by Codex-engine workflows; blocking it is appropriate and expected security behavior.Policy Rule Attribution
📋 Policy: 7 rules, SSL Bump disabled, DLP disabled
deny-unsafe-portsdeny-connect-unsafe-portsdeny-raw-ipv4deny-raw-ipv6allow-both-plain.anthropic.com,.github.com,.githubusercontent.com(regex),.pypi.org,.registry.npmjs.org, etc.allow-both-regex^[a-zA-Z0-9.-]*\.githubusercontent\.com$deny-defaultRoot cause analysis for GitHub domain blocks:
The
allow-both-plainrule includes.github.com(with leading dot). In Squid'sdstdomainACL, a leading dot matches subdomains only — it does not match the apex domaingithub.comitself. This means:raw.githubusercontent.com→ should match the regex rule but may be failing due to port suffix (raw.githubusercontent.com:443) being included in ACL matchinggithub.com→ does not match.github.com(apex domain exclusion)codeload.github.com→ should match.github.combut apparently does not in this contextView Detailed Request Patterns by Workflow
Changeset Generator (1 run —
23581097995)Engine: Codex | Total: 64 allowed, 149 blocked (70% block rate)
raw.githubusercontent.com:443github.com:443ab.chatgpt.com:443codeload.github.com:443This workflow is trying to fetch content from
raw.githubusercontent.com(likely reading raw files) andgithub.comdirectly. With 149 blocks out of 213 total attempted connections, the workflow may be degraded — it should be completing with partial data or retrying.AI Moderator (5 runs — Codex engine)
Total across 5 runs: 58 allowed, 15 blocked
ab.chatgpt.com:443The consistent pattern of exactly 3 blocks per run on
ab.chatgpt.comsuggests this is a fixed initialization/telemetry call pattern from the Codex engine at startup. This is expected and benign blocking.Smoke Codex (1 run —
23581098000)Engine: Codex | Total: 23 allowed, 5 blocked
ab.chatgpt.com:443Similar pattern to AI Moderator — Codex engine telemetry calls being correctly blocked.
CI Cleaner (1 run —
23580490576)Engine: Copilot | Total: 99 allowed, 1 blocked
release-assets.githubusercontent.com:443Single block on a GitHub release assets domain. May be a one-time request for a release artifact that isn't in the default allowlist.
View Complete Blocked Domains List
raw.githubusercontent.com:443ab.chatgpt.com:443github.com:443codeload.github.com:443release-assets.githubusercontent.com:443Security Recommendations
🚨 High Priority
Fix Changeset Generator allowlist — The workflow is blocking legitimate GitHub domains. Add explicit entries to the workflow's
network.allowedconfiguration:With 149 blocks per run, this workflow is operating in a significantly degraded state.
Investigate
raw.githubusercontent.comregex match failure — The policy includes a regex rule^[a-zA-Z0-9.-]*\.githubusercontent\.com$intended to match all*.githubusercontent.comdomains. If this regex is failing for HTTPS CONNECT requests, it may be because Squid is matchingraw.githubusercontent.com:443(with port) against the pattern. Verify Squid regex ACL behavior for CONNECT tunnels.ℹ️ Informational
ab.chatgpt.comblocking is correct — The OpenAI Codex engine attempts to call this telemetry endpoint on initialization. This is correctly blocked by the default firewall policy. No action needed — this is a desirable security outcome.Add
github.comapex to default allowlist — The defaultallow-both-plainrule includes.github.combut Squid's dstdomain ACL with a leading dot only matches subdomains, not the apex. Consider addinggithub.com(no leading dot) to the default allowlist to cover direct connections togithub.com.All blocked traffic is Codex-engine — 100% of blocked requests came from workflows using the
codexengine, with one exception (1 request from CI Cleaner usingcopilot). This may indicate that Codex-based workflows have different network access patterns or use more raw GitHub API endpoints than Claude/Copilot-based workflows.References:
Beta Was this translation helpful? Give feedback.
All reactions