You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This daily firewall report covers the 7-day window ending 2026-05-17. A total of 38 workflow runs with firewall enabled were identified and audited. However, none of the 38 runs produced a firewall-audit-logs artifact, which is the artifact that carries Squid access logs, policy manifests, and API proxy token usage. As a result, all network-level counters are zero for this reporting period.
This is a data-availability issue rather than a security concern: the firewall was configured on all 38 runs but the audit-log upload step either did not execute (e.g. run was cancelled before that step) or the artifact has since expired.
📊 Key Metrics
Metric
Value
Workflow runs analyzed
38
🔥 Total network requests monitored
0
✅ Allowed requests
0
🚫 Blocked requests
0
Block rate
0%
Unique blocked domains
0
🚫 Top Blocked Domains
No blocked-domain data was available for this reporting period. All 38 audited runs lacked the firewall-audit-logs artifact required to extract domain-level statistics.
📋 Policy Rule Attribution
No policy rule data was available for this reporting period.
📈 30-Day Firewall Trends
View Detailed Request Patterns by Workflow
No per-workflow breakdown available — firewall-audit-logs artifact was absent from all 38 runs.
View Complete Blocked Domains List
No domain data available for this reporting period.
🔒 Security Recommendations
Investigate missing firewall-audit-logs artifacts: All 38 firewall-enabled runs are missing this artifact. Check whether the firewall upload step is correctly configured and whether runs are completing before the artifact upload step.
Verify firewall is actually intercepting traffic: The logs tool reports firewall enabled (squid) for these runs, but the absence of audit artifacts means we cannot confirm traffic was actually proxied and logged.
Check artifact retention policy: GitHub Actions artifacts expire after a configurable retention period. If the runs are older than the retention window, audit logs will no longer be available.
Add monitoring: Consider adding an alert if firewall-audit-logs is missing from firewall-enabled runs — this could indicate a silent failure in the firewall pipeline.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
🔥 Executive Summary
This daily firewall report covers the 7-day window ending 2026-05-17. A total of 38 workflow runs with firewall enabled were identified and audited. However, none of the 38 runs produced a
firewall-audit-logsartifact, which is the artifact that carries Squid access logs, policy manifests, and API proxy token usage. As a result, all network-level counters are zero for this reporting period.This is a data-availability issue rather than a security concern: the firewall was configured on all 38 runs but the audit-log upload step either did not execute (e.g. run was cancelled before that step) or the artifact has since expired.
📊 Key Metrics
🚫 Top Blocked Domains
No blocked-domain data was available for this reporting period. All 38 audited runs lacked the
firewall-audit-logsartifact required to extract domain-level statistics.📋 Policy Rule Attribution
No policy rule data was available for this reporting period.
📈 30-Day Firewall Trends
View Detailed Request Patterns by Workflow
No per-workflow breakdown available —
firewall-audit-logsartifact was absent from all 38 runs.View Complete Blocked Domains List
No domain data available for this reporting period.
🔒 Security Recommendations
firewall-audit-logsartifacts: All 38 firewall-enabled runs are missing this artifact. Check whether the firewall upload step is correctly configured and whether runs are completing before the artifact upload step.logstool reports firewall enabled (squid) for these runs, but the absence of audit artifacts means we cannot confirm traffic was actually proxied and logged.firewall-audit-logsis missing from firewall-enabled runs — this could indicate a silent failure in the firewall pipeline.View All 38 Audited Run IDs
References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
productionresultssa5.blob.core.windows.netSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions