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
Audit period: 2026-03-26 ~06:00 UTC – 15:14 UTC (last 24h, ~9+ hours of coverage) Runs analyzed: 50+ completed runs across 40 pages of workflow history in github/gh-aw Runs with artifacts: 8 confirmed (scout, issue-triage-agent, agent-container-smoke-test, auto-triage ×2, cli-consistency-checker, smoke-cross-repo-pr, daily-token-report)
The detection job across multiple workflows is consistently failing at the "Execute GitHub Copilot CLI" step, followed by a consequent failure of "Parse and conclude threat detection". The actual error output is inaccessible (DIFC-filtered), but the pattern is consistent across unrelated workflows and time windows.
Note: At 11:18 UTC, Auto-Triage Issues succeeded. By 13:44 UTC it was failing. This suggests a regression or transient condition occurred between ~11:18 and ~13:03 UTC today.
The Copilot CLI binary or model endpoint experiencing issues
Detection workflow guard_policy preventing the detection sub-agent from accessing needed data
W2: Audit Agent DIFC Clearance Gap
This audit agent ran without [secret] secrecy clearance. All attempts to download artifact content (agent, firewall-audit-logs, detection) and all job log reads were filtered by DIFC with the message:
"Resource 'resource:actions_get' has secrecy requirements that agent doesn't meet. The agent is not authorized to access [secret]-scoped data."
This means:
The audit cannot inspect actual rpc-messages.jsonl DIFC event counts
Cannot verify tool-level integrity tag correctness
Cannot count filtered vs. total items in any run
Cannot confirm guard error messages or unscoped tags
Recommendation: Future integrity audits should run with [secret] clearance, or artifacts should be exported to a dedicated, lower-secrecy audit store.
🟢 Informational
DIFC Pipeline Health
Confirmed active: DIFC enforcement is working — resource:actions_get and resource:get_job_logs are correctly classified as [secret]-scoped and filtered when accessed by this agent.
Artifact listing accessible: list_workflow_run_artifacts returns metadata without DIFC filtering (artifact IDs, sizes, names, digests), confirming metadata is treated as non-secret.
Run & job metadata accessible: Workflow run lists, job lists, and step-level status/conclusion are all accessible and not filtered.
Auto-Triage Issues succeeded at 11:18 UTC: Run 23591520024 — confirms the pipeline was healthy earlier in the period.
These are isolated failures in the safe_outputs job and may indicate an issue with the safeoutputs service or its configuration at the time of those runs.
Runs With Full Artifact Sets (Detection + Agent + Firewall-Audit-Logs)
These runs completed successfully and produced the expected DIFC artifact sets:
Investigate detection job failures — The "Execute GitHub Copilot CLI" step is failing in the detection job across 5 different workflows between 11:19 and 14:04 UTC. Since Auto-Triage Issues succeeded at 11:18 but failed at 13:44, something regressed. Check if:
A Copilot CLI token or credential expired/rotated between those times
A model endpoint became unavailable
A DIFC policy change affected detection agent access
The actual error output in run 23598572272 detection job logs
Run integrity audits with [secret] clearance — This audit could not inspect actual DIFC event data, integrity tag counts, or guard error messages. A dedicated audit agent with appropriate secrecy clearance is needed for deep DIFC auditing.
Investigate recurring "Post Setup Scripts" failures — 4 different workflows failed in post-setup/teardown. This may indicate a shared infrastructure issue (disk space, runner environment, etc.).
Investigate "Process Safe Outputs" failures — 2 workflows failed in safe_outputs. Check if the safeoutputs service was experiencing issues at those times.
Note
🔒 Integrity filter blocked 2 items
The following items were blocked because they don't meet the GitHub integrity level.
actions_get actions_get: has secrecy requirements that agent doesn't meet. The agent is not authorized to access [secret]-scoped data.
get_job_logs get_job_logs: has secrecy requirements that agent doesn't meet. The agent is not authorized to access [secret]-scoped data.
To allow these resources, lower min-integrity in your GitHub frontmatter:
Audit period: 2026-03-26 ~06:00 UTC – 15:14 UTC (last 24h, ~9+ hours of coverage)
Runs analyzed: 50+ completed runs across 40 pages of workflow history in
github/gh-awRuns with artifacts: 8 confirmed (scout, issue-triage-agent, agent-container-smoke-test, auto-triage ×2, cli-consistency-checker, smoke-cross-repo-pr, daily-token-report)
Findings Summary
[secret]clearance — MCP logs/artifacts inaccessible via DIFCQandSmoke Claude(Process Safe Outputs step)🟡 Warnings
W1: Detection Job Failures — "Execute GitHub Copilot CLI" step (5 occurrences)
The
detectionjob across multiple workflows is consistently failing at the "Execute GitHub Copilot CLI" step, followed by a consequent failure of "Parse and conclude threat detection". The actual error output is inaccessible (DIFC-filtered), but the pattern is consistent across unrelated workflows and time windows.Note: At 11:18 UTC,
Auto-Triage Issuessucceeded. By 13:44 UTC it was failing. This suggests a regression or transient condition occurred between ~11:18 and ~13:03 UTC today.Potential causes:
guard_policypreventing the detection sub-agent from accessing needed dataW2: Audit Agent DIFC Clearance Gap
This audit agent ran without
[secret]secrecy clearance. All attempts to download artifact content (agent,firewall-audit-logs,detection) and all job log reads were filtered by DIFC with the message:This means:
rpc-messages.jsonlDIFC event countsRecommendation: Future integrity audits should run with
[secret]clearance, or artifacts should be exported to a dedicated, lower-secrecy audit store.🟢 Informational
DIFC Pipeline Health
resource:actions_getandresource:get_job_logsare correctly classified as[secret]-scoped and filtered when accessed by this agent.list_workflow_run_artifactsreturns metadata without DIFC filtering (artifact IDs, sizes, names, digests), confirming metadata is treated as non-secret.Infrastructure Failures (Not DIFC-related)
Safe-Outputs Failures
These are isolated failures in the
safe_outputsjob and may indicate an issue with the safeoutputs service or its configuration at the time of those runs.Runs With Full Artifact Sets (Detection + Agent + Firewall-Audit-Logs)
These runs completed successfully and produced the expected DIFC artifact sets:
Runs Analyzed (Selected Completed Runs)
Recommendations
Investigate detection job failures — The "Execute GitHub Copilot CLI" step is failing in the
detectionjob across 5 different workflows between 11:19 and 14:04 UTC. SinceAuto-Triage Issuessucceeded at 11:18 but failed at 13:44, something regressed. Check if:Run integrity audits with
[secret]clearance — This audit could not inspect actual DIFC event data, integrity tag counts, or guard error messages. A dedicated audit agent with appropriate secrecy clearance is needed for deep DIFC auditing.Investigate recurring "Post Setup Scripts" failures — 4 different workflows failed in post-setup/teardown. This may indicate a shared infrastructure issue (disk space, runner environment, etc.).
Investigate "Process Safe Outputs" failures — 2 workflows failed in
safe_outputs. Check if the safeoutputs service was experiencing issues at those times.Note
🔒 Integrity filter blocked 2 items
The following items were blocked because they don't meet the GitHub integrity level.
actions_get: has secrecy requirements that agent doesn't meet. The agent is not authorized to access [secret]-scoped data.get_job_logs: has secrecy requirements that agent doesn't meet. The agent is not authorized to access [secret]-scoped data.To allow these resources, lower
min-integrityin your GitHub frontmatter: