You don't need a security suite subscription to catch leaked keys, vulnerable dependencies and risky infrastructure changes before they ship. We build the checks into your GitLab pipelines, agree with your team what blocks a merge, and make sure findings are fixed, not just counted.
Security questionnaires ask how you scan; the answer is thin or noisy.
Open-source checks for code, secrets, dependencies, images and IaC in every merge request.
Findings with owners and deadlines, an SBOM per release, any GitLab tier.
One reusable CI template, included in each project. Each check runs where it is fast enough not to slow developers down. How the pipeline covers each task of NIST SSDF: see the SSDF coverage map.
| Check | Open tool (typical) | What it catches |
|---|---|---|
| Code analysis (SAST) | Semgrep Community Edition or Opengrep | Injection, unsafe APIs, common mistakes per language |
| Secrets | Gitleaks | API keys, tokens and passwords committed to Git |
| Dependencies | Trivy | Known vulnerabilities in libraries |
| Container images | Trivy | Vulnerable OS packages and misconfigurations in images |
| Infrastructure code | Checkov or Trivy | Public buckets, open security groups, missing encryption |
| SBOM | CycloneDX via Trivy or Syft, stored in Dependency-Track | What each release contains, and alerts when a new vulnerability affects it |
| Signing | cosign | Proof that an image was built by your pipeline |
| Findings in one place | DefectDojo | Deduplicated findings, owners, deadlines, accepted risks |
One include line per project; versions pinned and updated centrally.
What blocks a merge, what only warns — decided with your developers, not imposed.
Who looks at new findings, how false positives are marked, how exceptions expire.
Open findings by team and severity, trend over time, SBOM per release.
Two pages: what the checks do, how to read a finding, how to fix or dispute it.
Session with developers and with whoever owns security.
The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.
Pilot projects scanned, current findings measured, thresholds proposed. Final fixed price.
CI template, Dependency-Track and DefectDojo set up; pilot teams use it and give feedback.
Template added to all agreed projects, in batches, warnings first, blocking later.
Dashboards, guide, sessions, tuning of noisy rules.
Fixed price after the measurement in step 1. Paid by milestone.
Leaving a commercial scanner? See Snyk / SonarQube exit.
The fast checks run on every merge request; heavy ones run on the main branch or on a schedule. We measure the added time in the pilot.
Then we build on GitLab's own scanners and add what is missing, such as Dependency-Track for SBOM monitoring.
Every check starts in warning mode. We tune rules with your developers before anything blocks a merge, and exceptions get an owner and an expiry date.
It covers several technical measures the Cyber Resilience Act asks for, such as an SBOM and regular security testing. Compliance is broader — see our CRA page.
We give you a price range on a 30-minute call.