Security overview
Merge Pilot checks every change before it merges and keeps watching what has merged. On a merge request it looks for secrets, vulnerable or malicious dependencies, unwanted licenses, untrusted package versions, dependencies from unexpected sources, unsafe CI configuration and unsigned commits. On each project's default branch it keeps a vulnerability inventory: every known vulnerability the branch depends on, from when it was first seen until it is fixed, with the merge request that brought it in.
For a short overview of what it is for, see the Security scanning feature page.
This page is the map. The pages it links to describe each part field by field.
Two places security is checked
| Where | What is checked | Decided by |
|---|---|---|
| A merge request, before it merges | Only what the change adds: added lines, new or upgraded dependencies, changed workflows, its commits | The change policy that covers the merge request: each check is a control set to Off, Report or Enforce (see Controls) |
| The default branch of each project in Merge Pilot | Everything the branch depends on now, looked up again when merges, direct changes or new advisories change the picture | The company's Vulnerability tracking settings (see Scanning) |
A finding on a merge request can hold the merge (in Enforce); a finding in the inventory never holds anything by itself. It is a record to work through, accept by exception, or fix.
On merge requests
| Check | What it looks for | Page |
|---|---|---|
| Secret scan | Credentials, keys and tokens in the lines a change adds, in file names and, by default, in its commit messages, title and description | Secret scan, and what to do with a finding: Secret findings |
| Dependency scan | Known vulnerabilities and malicious packages in the dependencies a change adds or upgrades, from the OSV.dev database, with the CISA KEV and EPSS marks below | Dependency scan |
| Licenses | Licenses of new or upgraded dependencies against the company's license policy | Licenses |
| Package health | Dependency versions published only days ago, and deprecated versions | Package health |
| Dependency sources | Where new and changed dependencies come from: a manifest changed without its lockfile, lockfile entries from a registry that is not allowed (dependency confusion), git, URL and local path dependencies, and pip index options | Dependency sources |
| Container image scan | Known vulnerabilities in the container images a change starts referring to (Dockerfile, Kubernetes, Helm, Compose), pulled from public or private registries | Container image scan |
| Infrastructure check | Misconfigurations a change introduces in Terraform, Kubernetes, Helm, Dockerfile, CloudFormation and Azure ARM files | Infrastructure check |
| CI configuration check | Problems in changed GitHub Actions workflows and GitLab CI configuration, such as script injection, unpinned actions, includes and images, and debug logging | CI configuration check |
| Signed commits | Commits without a verified signature | Signed commits |
| Binary files (risk) | A change that adds or changes a binary file, which reviewers cannot read, scores a higher risk | Risk → Diff footprint |
Licenses, package health and dependency sources run inside the dependency scan. Watched repositories are scanned only while the company scans watched merge requests (see Repositories settings).
Exploited in the wild, and likely to be
Two public feeds mark vulnerabilities, wherever Merge Pilot shows them:
- Exploited (KEV): the vulnerability is in CISA's Known Exploited Vulnerabilities catalog: attackers use it now.
- EPSS N%: the probability, from FIRST's Exploit Prediction Scoring System, that it is exploited in the next 30 days.
The marks are matched by CVE (the advisory's own ID or any of its aliases). A company can let a KEV vulnerability count as critical, and hold a merge from an EPSS percentage (see Dependency scan → Settings). The Vulnerabilities page says when each feed was last read (see Vulnerability inventory).
On the default branch
| Feature | What it does | Page |
|---|---|---|
| Project analysis | Reads every dependency manifest of a project's default branch, lists the dependencies, looks up their vulnerabilities and licenses, and keeps the result and its history | Project analysis |
| Vulnerability inventory | Follows each vulnerability on each default branch from first seen to fixed, names the merge request (or direct change) that brought it in and the one that fixed it, and looks for new advisories without reading the repositories | Vulnerability inventory |
| Exceptions | Accept a vulnerability for a while (risk accepted, or not affected), for one project or the whole company: merge requests are no longer held for it. A secret, a license or a package health finding of a merge request is accepted the same way | Vulnerability exceptions |
| SBOM | Export the dependencies a default branch uses, with their licenses, as CycloneDX or SPDX | SBOM export |
Direct changes (pushes that reach a watched branch without a merge request) can refresh the inventory too; see Direct changes.
Where it shows up
| Place | What you see |
|---|---|
| Merge request page | The Secret scan card, the Dependency scan (SCA) card (with licenses, package health and dependency sources), the CI configuration check, Container image scan and Infrastructure check cards, and each control's result in the merge gate |
| In the VCS | One comment per scan kept up to date on the merge request (Merge Pilot: Secret Scan, Merge Pilot: Dependency Scan, Merge Pilot: CI configuration check, Merge Pilot: container image scan, Merge Pilot: infrastructure check), except in watched repositories; the merge gate's status |
| Merge requests list | The Secrets column |
| Insights → Vulnerabilities | The company's vulnerability inventory, the exceptions in force and the exceptions waiting for review |
| A project's Security tab | The last analysis, the project's dependency, container image and infrastructure findings, licenses, dependencies, the analysis history, excluded paths and Export SBOM |
| Notifications | Secrets found in a merge request, Vulnerable dependency introduced by a merge request, the other scan findings of a merge request (see Events → Scan findings), and new vulnerabilities on default branches, as the company's Notifications tab routes them |
| Audit log | Every scan result that changed, re-scans, analyses, exceptions and SBOM exports (see Audit log → Scans) |
Who does what
| Task | Who |
|---|---|
| Turn a check on for a set of changes | Policy managers, company admins, platform admins (in a change policy) |
| Set the company's scan defaults and inventory settings | Company admins, platform admins (company Scanning tab) |
| Re-scan an open merge request | Everyone in the company except auditors |
| Run a project analysis, set a project's excluded paths | Company admins, platform admins |
| Read the vulnerability inventory and exceptions | Company admins, policy managers, auditors, platform admins |
| Accept or revoke a vulnerability exception | Policy managers, company admins, platform admins |
| Read a project's last analysis and export its SBOM | Everyone in the company |
See Roles and users.
Related pages
- Scanning: the company's scan defaults and the vulnerability tracking settings.
- Controls: modes, company settings and policy overrides.
- Project page: the Security tab.
- Governance tab: four-eyes review of exceptions.
Video tutorials
Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →