> ## Documentation Index
> Fetch the complete documentation index at: https://zeropath.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# CI/CD security

> Review pipeline controls, workflow findings, and release policy changes in GitHub and GitLab

Use CI/CD security to see which pipeline controls ZeroPath checked for your branch and where evidence is missing. ZeroPath reads provider settings and workflow definitions for imported GitHub and GitLab repositories. Make changes in your provider and use the next assessment to review the result. Monitoring is read-only.

## Open a repository assessment

1. Under **Assets**, open **CI/CD security** and choose a repository. You can also open the **CI/CD** tab from the repository page.
2. 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.
3. 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.

| Status | What it means |
| - | - |
| **Needs attention** | The observed setting failed the control. Review the recommendation. |
| **Unavailable** | ZeroPath could not establish a result. Check **Coverage** for collection limits. |
| **Previous evidence** | ZeroPath is showing a saved observation. Check its date before relying on it. |
| **Pass** or **Not applicable** | The control passed on the observed evidence or did not apply to the repository. |

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](#change-history).

For CI/CD findings from code scans, open [**Issues → CI/CD**](https://zeropath.com/docs/platform/issues.md#export-findings). Use **Export** there to download findings from the selected scope. Review pipeline controls, coverage, and observation times in the repository assessment. To configure checks ZeroPath publishes on pull requests, see [PR scanning](https://zeropath.com/docs/scanning/pr-scanning.md).

## 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

| When you see | What to check |
| - | - |
| **Full source access required** | You need repository view access to the whole source. For a partitioned import, this can require access to all application partitions. |
| **Enrollment queued** or **First check queued** | Supported imports are enrolled automatically. Check again after the first collection. On a self-hosted deployment, use a distribution release that includes CI/CD monitoring and verify that the monitor worker is running. |
| **Collection needs attention** or **Coverage is incomplete** | Review **Coverage** for collection gaps. Confirm the monitored branch exists and the provider connection can read it. |
| **Unsupported provider** | Continuous monitoring uses GitHub or GitLab connections. Other providers, including Bitbucket, can show this state on their repository tab. |

**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](https://zeropath.com/docs/integrations/github-enterprise-server.md#what-the-app-can-access).

**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.

The monitor reads workflow definitions without executing them and saves assessment results and run metadata. Review effective approval and bypass rules, runner behavior, cloud trust policies, and artifact provenance in the systems that control them.

## Change history

ZeroPath retains up to 20 changes from the past 90 days. Routine checks and unrelated commits leave history unchanged. For GitHub rulesets, **Changes** can show additions, removals, or replacements in the required check set after two complete observations for the same branch. Review classic branch protection in GitHub for other required checks.

Imports of the same source repository and configured scan branch in one organization share a monitor. Changing the scan branch can switch the history. Removing the last import for a monitor deletes its stored evidence and history.

## API and MCP

Use the [API reference](https://zeropath.com/docs/api-reference/introduction.md#cicd-security) for REST paths or the [MCP tool reference](https://zeropath.com/docs/mcp/tools.md#cicd-security) for tool names and permissions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.