[security-observability] Daily Security Observability Report — 2026-06-29

[github-actions[bot]]

Executive Summary

Today's unified security observability report covers 118 firewall-enabled agentic workflow runs from 2026-06-29 (the available analysis window). The firewall monitored 8,648 total network requests with a 99.5% allow rate — the infrastructure remains largely healthy and well-configured. Four blocked domain categories were identified, the most notable being awmg-mcpg (the internal MCP gateway), which was attempted 34 times by 3 workflows operating inside sandboxed containers where the gateway is inaccessible. This represents a misconfiguration to remediate rather than a security threat.

On the DIFC (Data Integrity and Flow Control) front, the integrity-filtering subsystem returned zero filtered events in the last 7 days, indicating no MCP tool calls were blocked for integrity or secrecy violations. This is a positive signal, either reflecting clean data flow or a period of reduced DIFC-tagged traffic. Both signals together paint a stable security posture with targeted remediation needed for a small set of network allowlist gaps.

---

🔥 Firewall Analysis

Key Firewall Metrics

Metric	Value
Workflows analyzed (firewall-enabled)	118
Total network requests monitored	8,648
✅ Allowed requests	8,608
🚫 Blocked requests	40
Block rate	0.46%
Total unique blocked domains	4

📈 Firewall Request Trends

Network traffic peaked at the 15:00 UTC hour with 2,111 allowed requests across 26 concurrent runs, and dipped at 13:00 UTC (902 requests, 12 runs). The 12:00 UTC hour recorded the highest block count (23), driven primarily by awmg-mcpg attempts and proxy.golang.org blocks. Overall, the traffic pattern is consistent with scheduled workflow activity, with no anomalous spikes.

Top Blocked Domains

The awmg-mcpg internal hostname dominates the blocked list (34 requests, 3 workflows). This indicates those agents are attempting to reach the MCP gateway directly from inside their sandbox, which is architecturally incorrect. The remaining blocks (proxy.golang.org ×4, storage.googleapis.com ×1, release-assets.githubusercontent.com ×1) represent missing allowlist entries for Go toolchain and release-asset workflows.

Most Frequently Blocked Domains

Domain	Times Blocked	Workflows Affected	Category
awmg-mcpg	34	3	Internal MCP gateway (not sandbox-accessible)
proxy.golang.org	4	3	Go module proxy (missing from allowlist)
storage.googleapis.com	1	4	Google Cloud Storage (missing from allowlist)
release-assets.githubusercontent.com	1	1	GitHub release assets (missing from allowlist)

📋 Policy Rule Configuration (Active Firewall Policy)

Policy version: 1 | Firewall: v0.27.13 | Generated: 2026-06-29T15:23:07.908Z

Rule	Action	Description
deny-unsafe-ports	🔴 DENY	Deny requests to ports not in Safe_ports ACL (80, 443 only)
deny-connect-unsafe-ports	🔴 DENY	Deny CONNECT to non-Safe_ports
allow-api-proxy-ip	🟢 ALLOW	Allow api-proxy sidecar IP (172.30.0.30)
allow-from-api-proxy	🟢 ALLOW	Unrestricted outbound from api-proxy sidecar
deny-raw-ipv4	🔴 DENY	Deny raw IPv4 address connections
deny-raw-ipv6	🔴 DENY	Deny raw IPv6 address connections
allow-both-plain	🟢 ALLOW	Allow HTTP/HTTPS to configured domain allowlist
allow-both-regex	🟢 ALLOW	Allow HTTP/HTTPS matching wildcard patterns (*.grafana.net, *.sentry.io)
deny-default	🔴 DENY	Default deny — all other traffic blocked

📋 Top Allowed Domains by Request Volume

Domain	Allowed Requests	Workflows	Notes
api.githubcopilot.com	3,730	45	Primary AI model endpoint (Copilot)
o205451.ingest.us.sentry.io	1,810	50	Error telemetry (*.sentry.io)
otlp-gateway-prod-eu-west-2.grafana.net	1,607	50	OTLP tracing (*.grafana.net)
api.anthropic.com	915	11	Claude direct API
github.com	396	6	GitHub main domain
registry.npmjs.org	41	2	npm package registry
proxy.golang.org	22	3	Go module proxy (allowed when on allowlist)
api.openai.com	21	1	OpenAI API
api.github.com	17	3	GitHub REST API
raw.githubusercontent.com	5	1	GitHub raw content
storage.googleapis.com	4	4	Google Cloud Storage
pypi.org	3	2	Python package index
sum.golang.org	3	3	Go checksum database
chatgpt.com	1	1	ChatGPT web

🔒 Firewall Security Recommendations

1. Add proxy.golang.org and sum.golang.org to the global Go workflow allowlist — Three workflows (PR Code Quality Reviewer, Impeccable Skills Reviewer, Package Specification Enforcer) are failing Go dependency resolution. Add proxy.golang.org and sum.golang.org to .github/aw/network.md for Go-toolchain workflows.

2. Add storage.googleapis.com for download-heavy workflows — Four workflows are intermittently blocked from Google Cloud Storage. Consider adding this to the allowlist for workflows that pull pre-built binaries or model assets.

3. Add release-assets.githubusercontent.com for CLI Consistency Checker — This workflow attempts to download GitHub release assets via a redirect-resolved URL not covered by the base github.com/raw.githubusercontent.com allowlist.

4. Investigate awmg-mcpg access attempts — Workflows GitHub API Consumption Report Agent, Daily Max AI Credits Test, and Constraint Solving — Problem of the Day are trying to reach the internal awmg-mcpg:8080 MCP gateway directly from within the sandbox. This should be impossible by design; these agents should be using the pre-configured tool path. Review their workflow configuration to ensure they're not attempting to self-spawn tool calls to the gateway. The "Daily Max AI Credits Test (Intentionally Fails)" case may be expected, but the others need investigation.

5. Consider flagging IP-address requests for review — Some workflows are making connections to raw IP addresses (e.g., 151.101.x.x) which are GitHub's CDN nodes. These are currently allowed after passing raw-IP denial rules, but direct IP usage bypasses domain-name-based policy and could indicate misconfigured clients.

---

🔒 DIFC Integrity Analysis

Key DIFC Metrics

Metric	Value
Total filtered events	0
Unique tools filtered	0
Unique workflows affected	0
Most common filter reason	N/A
Busiest day	N/A

i️ No DIFC integrity-filtered events were found in the last 7 days. The collection job completed with an empty result set (runs: []). Either no tool calls triggered integrity/secrecy filtering, or the DIFC collection pipeline experienced a data gap. The charts below are shown as "no data" placeholders.

📈 DIFC Events Over Time

No event data available for this reporting period. This could reflect a genuinely clean period with no integrity violations, or it may indicate the filtered-integrity log collection pipeline needs investigation.

🔧 Top Filtered Tools

No filtered tool data to report.

🏷️ Filter Reasons and Tags

No tag breakdown available.

💡 DIFC Tuning Recommendations

1. Verify DIFC collection pipeline health — The filtered_integrity log query returned zero results for the 7-day window. Verify that the DIFC event ingestion pipeline is active and that the filtered-logs.json is being populated correctly by the setup step.

2. Establish a DIFC baseline — If the zero-event result is genuine, document it as a baseline for future comparison. A sudden spike in filtered events would then be immediately detectable against this clean baseline.

3. Review DIFC coverage of high-volume workflows — The 118 firewall-enabled workflows include several high-tool-activity runs (e.g., Issue Monster with Pi engine, Agent Persona Explorer). Confirm that DIFC monitoring is configured and active for these workflows.

---

Generated by the Daily Security Observability workflow (consolidated from Daily Firewall Reporter + Daily DIFC Analyzer)
Analysis window: Last 7 days (available data: 2026-06-29) | Repository: github/gh-aw
Run: §28388325811

Generated by 🔒 Daily Security Observability Report · 234.3 AIC · ⌖ 11.1 AIC · ⊞ 10.6K · ◷

• expires on Jul 2, 2026, 9:34 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-07-02T17:34:11.771Z.

Closed by Workflow