Skip to main content
2 video tutorials

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​

WhereWhat is checkedDecided by
A merge request, before it mergesOnly what the change adds: added lines, new or upgraded dependencies, changed workflows, its commitsThe 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 PilotEverything the branch depends on now, looked up again when merges, direct changes or new advisories change the pictureThe 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​

CheckWhat it looks forPage
Secret scanCredentials, keys and tokens in the lines a change adds, in file names and, by default, in its commit messages, title and descriptionSecret scan, and what to do with a finding: Secret findings
Dependency scanKnown vulnerabilities and malicious packages in the dependencies a change adds or upgrades, from the OSV.dev database, with the CISA KEV and EPSS marks belowDependency scan
LicensesLicenses of new or upgraded dependencies against the company's license policyLicenses
Package healthDependency versions published only days ago, and deprecated versionsPackage health
Dependency sourcesWhere 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 optionsDependency sources
Container image scanKnown vulnerabilities in the container images a change starts referring to (Dockerfile, Kubernetes, Helm, Compose), pulled from public or private registriesContainer image scan
Infrastructure checkMisconfigurations a change introduces in Terraform, Kubernetes, Helm, Dockerfile, CloudFormation and Azure ARM filesInfrastructure check
CI configuration checkProblems in changed GitHub Actions workflows and GitLab CI configuration, such as script injection, unpinned actions, includes and images, and debug loggingCI configuration check
Signed commitsCommits without a verified signatureSigned commits
Binary files (risk)A change that adds or changes a binary file, which reviewers cannot read, scores a higher riskRisk → 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​

FeatureWhat it doesPage
Project analysisReads every dependency manifest of a project's default branch, lists the dependencies, looks up their vulnerabilities and licenses, and keeps the result and its historyProject analysis
Vulnerability inventoryFollows 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 repositoriesVulnerability inventory
ExceptionsAccept 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 wayVulnerability exceptions
SBOMExport the dependencies a default branch uses, with their licenses, as CycloneDX or SPDXSBOM 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​

PlaceWhat you see
Merge request pageThe 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 VCSOne 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 listThe Secrets column
Insights → VulnerabilitiesThe company's vulnerability inventory, the exceptions in force and the exceptions waiting for review
A project's Security tabThe last analysis, the project's dependency, container image and infrastructure findings, licenses, dependencies, the analysis history, excluded paths and Export SBOM
NotificationsSecrets 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 logEvery scan result that changed, re-scans, analyses, exceptions and SBOM exports (see Audit log → Scans)

Who does what​

TaskWho
Turn a check on for a set of changesPolicy managers, company admins, platform admins (in a change policy)
Set the company's scan defaults and inventory settingsCompany admins, platform admins (company Scanning tab)
Re-scan an open merge requestEveryone in the company except auditors
Run a project analysis, set a project's excluded pathsCompany admins, platform admins
Read the vulnerability inventory and exceptionsCompany admins, policy managers, auditors, platform admins
Accept or revoke a vulnerability exceptionPolicy managers, company admins, platform admins
Read a project's last analysis and export its SBOMEveryone in the company

See Roles and users.

  • 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 →

Catch a Leaked Secret Before It MergesYouTube ↗
Block Vulnerable DependenciesYouTube ↗