[daily-firewall-report] Daily Firewall Report - 2026-04-03 #24286
Closed
Replies: 2 comments 1 reply
-
|
/plan in a single issue |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This discussion has been marked as outdated by Daily Firewall Logs Collector and Reporter. A newer discussion is available at Discussion #24474. |
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.
-
Executive Summary
This daily firewall report covers all agentic workflow runs on 2026-04-03 with the Squid proxy firewall enabled. The firewall processed 1,329 total network requests across 54 runs (out of 72 firewall-enabled runs), with a 2.1% block rate (28 blocked requests). Most blocked traffic came from smoke/test workflows probing external AI services (
chatgpt.com) and two legitimate dependency workflows that need allowlist updates (proxy.golang.orgfor Dependabot,nodejs.orgfor Glossary Maintainer).The firewall ran on awf v0.25.13 with a 7-rule policy (4 deny rules + 2 allow rules + 1 default deny) across all workflows using
allowed_domains: [defaults].Key Metrics
📈 Firewall Activity Trends
Request Patterns
Firewall activity peaked between 04:45–05:30 UTC (smoke test suite) and 09:00–10:30 UTC (daily scheduled workflows). The blocking spike in the early morning correlates with the smoke test batch that runs Codex engine validation. All blocked requests were hard denials (403) with no retries recorded, indicating agents properly handled network failures.
Top Blocked Domains
chatgpt.comaccounts for the majority of blocked traffic (10/28 = 36%), all originating from smoke test workflows validating firewall behavior. The Go ecosystem (proxy.golang.org,pkg.go.dev) is the second-largest block category at 6 hits, all from Dependabot — a legitimate gap in the allowlist.Top Blocked Domains
Policy Rule Attribution
Policy Configuration
All analyzed runs used an identical 7-rule policy (awf v0.25.13):
📋 Policy: 7 rules, SSL Bump disabled, DLP disabled
Policy Rule Hit Table
Denied Requests Attribution
All 28 blocked requests matched the
deny-defaultrule (no explicit deny rule targeted them — they simply weren't in the allowlist)..github.combut not rootRule Effectiveness Summary
*.jsr.ioisn't being used; it could be removed if unused.github.com(subdomain wildcard) being allowed is an edge case: the default policy matches*.github.combut notgithub.comitself; workflows using the bare hostname are hitting this gapView Detailed Request Patterns by Workflow
Changeset Generator (2 runs: 23934285733, 23934614472)
Each run blocked 3 requests. This workflow uses a specialized allowlist (bun.sh, CDN, npm) that does not include
github.comorapi.github.com.Cause: The Changeset Generator's custom allowlist covers CDN/package managers but excludes raw GitHub API access. The
chatgpt.comprobe is a smoke-test artifact.Smoke Agent Variants (5 runs)
Runs: 23934694441, 23934694455, 23934694462, 23934694474, 23934694481
Each Smoke Agent run blocked exactly 1 request:
chatgpt.com. These appear to be deliberate escape probes validating the firewall is working.Dependabot Dependency Checker (run 23941823622)
6 blocked requests — highest among non-smoke workflows.
Cause: The Dependabot workflow tries to resolve Go dependencies but
proxy.golang.organdpkg.go.devare not in the default allowlist. This likely causes silent failures in Go dependency resolution.AI Moderator (run 23938244785)
3 blocked requests — same pattern as Changeset Generator (restricted allowlist).
Glossary Maintainer (run 23942998940)
1 blocked request:
nodejs.org. The workflow may have been trying to fetch the latest Node.js release metadata.GPL Dependency Cleaner (run 23934389762)
1 blocked request:
storage.googleapis.com. Google Cloud Storage is used as a distribution endpoint for some tools/packages.jsweep & The Great Escapi
Both appear to be security-aware workflows that include deliberate escape probes:
invalid.example.invalid— synthetic domain testexample.com— reserved test domainThese blocks are expected and correct firewall behavior confirming containment is working.
View Complete Blocked Domains List
All unique blocked domains (alphabetical), 2026-04-03:
Security Recommendations
🔧 Fix: Add Go Ecosystem to Dependabot Allowlist
Priority: High —
proxy.golang.org(5 blocks) andpkg.go.dev(1 block) are causing silent failures in Go dependency resolution. Add to the Dependabot workflow's network allowlist:🔧 Fix: Add nodejs.org for Glossary Maintainer
Priority: Medium — The Glossary Maintainer was blocked from
nodejs.org(1 block). If the workflow needs Node.js release metadata, add it to the allowlist or use an alternative source.🔧 Fix: storage.googleapis.com for GPL Dependency Cleaner
Priority: Medium — The GPL Dependency Cleaner was blocked from
storage.googleapis.com(1 block). If this is needed for downloading tools, add it to the workflow's allowlist.🔍 Investigate: github.com vs .github.com policy gap
Priority: Medium — 4 blocks on bare
github.com+ 4 onapi.github.comin workflows that should have GitHub access. The default policy uses.github.com(subdomain wildcard) but the Changeset Generator and AI Moderator use a restricted custom allowlist. Verify these workflows don't need directgithub.comaccess, or add explicit entries.✅ Expected: Smoke Test Probes
The
chatgpt.com,invalid.example.invalid, andexample.comblocks are deliberate firewall escape probes from smoke/security test workflows. These are working as intended — the firewall is correctly containing access.🗑️ Cleanup: Unused Regex Rule
The
allow-both-regexrule (currently only*.jsr.io) had 0 hits today. Ifjsr.iois not actively used, consider removing this rule to simplify the policy.References:
Beta Was this translation helpful? Give feedback.
All reactions