Open a repository assessment
- Under Assets, open CI/CD security and choose a repository. You can also open the CI/CD tab from the repository page.
- Confirm the branch in the header. ZeroPath uses the repository’s configured scan branch or the provider’s default branch when none is configured. Checked shows the last successful collection when one is available.
- Start in Controls. Open Findings for issues in workflow files or Coverage to check whether ZeroPath collected the evidence you need.
Read the results
Review controls and release policy
Controls is the starting view. Open a control for its evidence, observation date, and recommended action when available.
The release assessment highlights a control to review or identifies evidence that is pending, stale, or unavailable. Select Review guardrail to open the highlighted control or Review policy evidence to see the release controls. Observed release guardrails means ZeroPath found no gaps in the release controls it reviewed.
Review workflow findings and coverage
- Findings shows severity, location, and suggested changes. Workflows shows the files inspected and file-level analysis gaps.
- Coverage shows how many files were analyzed, collection errors, and the next scheduled check when available. A partial collection can leave files or settings unverified. An interrupted check can leave earlier results visible.
- Changes shows detected changes to settings, workflow findings, and required GitHub status checks. See change history.
Verify a change
Make the fix in your provider and push workflow changes to the monitored branch. ZeroPath queues checks on supported pushes and runs daily checks. To request an earlier check, open CI/CD actions and select Request reassessment. This requires permission to start scans (SCAN_START). Provider limits and connection health can delay the result.
Reload results displays the latest saved assessment. Check the observation time for the specific control you changed. GitHub ruleset and environment checks and GitLab protected-environment approval checks follow a weekly schedule, including after a requested reassessment.
Access and troubleshooting
GitHub App connections use Contents read access for workflow definitions, Actions read access for run metadata, and Administration read access for Actions settings. For a customer-managed app, add any missing permissions in GitHub and approve the update on the installation. See GitHub Enterprise App setup.
GitLab connections depend on the token’s role, server version, and plan. ZeroPath uses the static CI Lint API to expand includes at the monitored commit when available. Expanded findings refer to line numbers in the expanded configuration. If expansion fails, ZeroPath checks the readable root configuration and reports partial coverage.
What ZeroPath checks
GitHub Actions
- Provider settings include branch protection, workflow token permissions, workflow PR approvals, allowed actions, and full SHA pinning. Release policy covers PR approvals and required checks in active rulesets, environment reviewers, and deployment self-review.
- Workflow analysis checks mutable action and image references, broad token permissions, inherited secrets, untrusted script inputs, runner and checkout settings, privileged containers, Docker socket mounts, and OIDC token permissions.
GitLab CI/CD
- Provider settings include branch protection and Developer push rules, job visibility, pushes with job tokens, variable override roles, required pipelines before merge, parent-project fork pipelines, and protected-environment approvals.
- Workflow analysis checks mutable images and includes, debug logging, Docker-in-Docker without TLS, and default OIDC token declarations.