Skip to content

Add Sentinel CI workflow for workflow security scanning#66

Closed
jpr5 wants to merge 1 commit into
mainfrom
sentinel-rollout/add-workflow
Closed

Add Sentinel CI workflow for workflow security scanning#66
jpr5 wants to merge 1 commit into
mainfrom
sentinel-rollout/add-workflow

Conversation

@jpr5
Copy link
Copy Markdown
Contributor

@jpr5 jpr5 commented May 22, 2026

Summary

  • Adds .github/workflows/sentinel.yml for automated workflow security scanning via Sentinel
  • Runs on all pull requests and pushes to main
  • Configured in warn-only mode (fail-on-findings: false) — surfaces findings without blocking merges
  • Part of the org-wide Sentinel rollout (spec)

Details

Sentinel scans GitHub Actions workflows for security issues (credential exposure, injection risks, overly broad permissions, unpinned actions, etc.). This initial rollout uses severity: high to focus on the most impactful findings.

Test plan

  • CI runs the new Sentinel workflow on this PR
  • Workflow completes without blocking the PR (warn-only mode)
  • Review any findings surfaced in the Actions tab

@jpr5 jpr5 force-pushed the sentinel-rollout/add-workflow branch from 5f1136e to 5e9149f Compare May 22, 2026 20:49
@jpr5
Copy link
Copy Markdown
Contributor Author

jpr5 commented May 22, 2026

Force-pushed with SHA-pinned actions to satisfy zizmor's unpinned-uses rule. Per the org-wide sentinel rollout, the floating-tag-for-easy-updates model is being replaced with SHA-pin + dependabot. Spec updated. Rest of the PR unchanged.

@jpr5
Copy link
Copy Markdown
Contributor Author

jpr5 commented May 22, 2026

Promoted to blocking mode — this repo had zero sentinel findings on the warn-only scan, so we're skipping the 7-day warn-only observation period. fail-on-findings is now true; future PRs that introduce critical/high findings will block merge.

@jpr5 jpr5 force-pushed the sentinel-rollout/add-workflow branch from 5e9149f to 33712dd Compare May 22, 2026 21:33
@jpr5
Copy link
Copy Markdown
Contributor Author

jpr5 commented May 22, 2026

Promoted to blocking mode — this repo had zero sentinel findings on the warn-only scan, so we're skipping the 7-day warn-only observation period. fail-on-findings is now true; future PRs that introduce critical/high findings will block merge.

1 similar comment
@jpr5
Copy link
Copy Markdown
Contributor Author

jpr5 commented May 22, 2026

Promoted to blocking mode — this repo had zero sentinel findings on the warn-only scan, so we're skipping the 7-day warn-only observation period. fail-on-findings is now true; future PRs that introduce critical/high findings will block merge.

Part of org-wide sentinel rollout. Warn-only mode (fail-on-findings: false).
Spec: https://www.notion.so/copilotkit/3683aa381852818bacd8e14eb7233c22
@jpr5 jpr5 closed this May 22, 2026
@jpr5 jpr5 force-pushed the sentinel-rollout/add-workflow branch from 33712dd to d0a4de6 Compare May 22, 2026 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant