[security-observability] Daily Security Observability Report — 2026-09-01 #57736
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Daily Security Observability Report. A newer discussion is available at Discussion #57991. |
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
Over the past 7 days, 93 of 100 firewall-enabled workflow runs generated network telemetry, totaling 5,106 monitored requests with a 4.39% block rate (224 blocked / 4,882 allowed). Blocking was concentrated on a small set of domains — most notably
proxy.golang.org:443(136 blocks, entirely from CI Optimization Coach) andab.chatgpt.com:443(37 blocks across multiple workflows), suggesting a handful of workflows may need network permission or allowlist updates rather than a widespread security incident.Separately, the DIFC integrity-filtering layer blocked 354 tool calls across 8 workflow runs, concentrated almost entirely on a single day (Sep 1) and dominated by
list_issues(236) andsearch_issues(111) calls in the Workflow Normalizer and Smoke Agent: public/approved workflows. All filtered events shared the same root cause — the agent attempting to read GitHub issues taggedunapproved:public, which fall below the agent's required integrity threshold. This is expected DIFC behavior protecting against untrusted issue content, not an anomaly.No workflow appeared in both the top firewall-blocked list and the top DIFC-filtered list, indicating these two protection layers are currently addressing distinct risk surfaces (outbound network egress vs. inbound untrusted GitHub content).
🔥 Firewall Analysis
Key Firewall Metrics
📈 Firewall Request Trends
All firewall telemetry collected in this window falls on a single reporting day (Sep 1), reflecting the audit tool's per-run created_at granularity rather than an actual traffic spike. Allowed traffic (4,882 requests) vastly outweighs blocked traffic (224), consistent with a healthy baseline where most outbound calls target approved endpoints like
api.githubcopilot.comand telemetry backends.Top Blocked Domains
proxy.golang.org:443accounts for 61% of all blocked requests, exclusively from CI Optimization Coach — this is likely a Go module proxy dependency that should be allowlisted if the workflow legitimately needs it.ab.chatgpt.com:443blocks span multiple unrelated workflows (AI Moderator, Daily Credit Limit Test, Feature Grower), suggesting a shared base image or MCP client attempting an unintended outbound call.Most Frequently Blocked Domains
[When policy_analysis is available:]
Policy Rule Attribution
📋 Policy: 11 rules, SSL Bump disabled, DLP disabled
No per-rule hit counts were reported by the audit tool for these runs (rule_hits arrays were empty across all sampled runs), so rule-level attribution is not available this cycle.
View Detailed Request Patterns by Workflow (Top 15 by blocked requests)
View Complete Blocked Domains List
🔒 Firewall Security Recommendations
proxy.golang.org:443for CI Optimization Coach if the workflow legitimately builds/tests Go modules — this single domain accounts for the majority of all blocks this week.ab.chatgpt.com:443across the AI Moderator, Daily Credit Limit Test, and Feature Grower workflows — this domain is not an expected GitHub/Copilot infrastructure endpoint and its recurring appearance across unrelated workflows warrants a source check (e.g., a shared engine/runtime dependency making an unintended telemetry call).github.com:443blocks in Daily Malicious Code Scan Agent and PR Sous Chef — if these workflows need direct git/web access beyondapi.github.com, add an explicit allow rule; otherwise this may indicate an unintended redirect or scraping attempt worth auditing.rule_hitsare empty) to support future per-rule attribution and tuning.🔒 DIFC Integrity Analysis
Key DIFC Metrics
📈 DIFC Events Over Time
All 354 filtered events cluster on the most recent reporting day, driven by two smoke-test workflows exercising the GitHub MCP server's
list_issues/search_issuestools against the full issue corpus (including many public, unapproved issues). This is expected exercise traffic from smoke/validation workflows rather than a genuine anomaly.🔧 Top Filtered Tools
list_issues(236 events) andsearch_issues(111 events) together account for 98% of all DIFC filtering, both blocked for the same reason: results included issues taggedunapproved:public, which fall below the agent's configured integrity floor.search_repositories(6) andsearch_code(1) contributed marginally.🏷️ Filter Reasons and Tags
100% of filtered events were attributed to "insufficient integrity level" — no secrecy-tag violations occurred this week. Integrity tag
none:publicappeared on all 354 events, withunapproved:public(252) as the dominant sub-tag andapproved:public(7) appearing on a small minority that were nonetheless filtered (likely due to combined result sets containing both approved and unapproved issues).📋 Per-Workflow DIFC Breakdown
📋 Per-Server DIFC Breakdown
👤 Per-User DIFC Breakdown
💡 DIFC Tuning Recommendations
list_issues/search_issuescalls. Consider scoping their queries withstate/labelfilters to reduce noise if the filtering volume impacts token/latency budgets.author_login: unknown); consider enriching gateway logging to capture the triggering actor for audit-trail completeness, especially for non-smoke workflows.Generated by the Daily Security Observability workflow (consolidated from Daily Firewall Reporter + Daily DIFC Analyzer)
Analysis window: Last 7 days | Repository: github/gh-aw
Run: https://github.com/github/gh-aw/actions/runs/33530583409
All reactions