Home›Services›DevSecOps Pipeline

Security checks in every merge request — built from open tools

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.

from $8,000 · fixed price Measured first, then fixed price and dates Any GitLab tier
The problem

Security questionnaires ask how you scan; the answer is thin or noisy.

What we do

Open-source checks for code, secrets, dependencies, images and IaC in every merge request.

The result

Findings with owners and deadlines, an SBOM per release, any GitLab tier.

Is this you?

The checks

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.

CheckOpen tool (typical)What it catches
Code analysis (SAST)Semgrep Community Edition or OpengrepInjection, unsafe APIs, common mistakes per language
SecretsGitleaksAPI keys, tokens and passwords committed to Git
DependenciesTrivyKnown vulnerabilities in libraries
Container imagesTrivyVulnerable OS packages and misconfigurations in images
Infrastructure codeCheckov or TrivyPublic buckets, open security groups, missing encryption
SBOMCycloneDX via Trivy or Syft, stored in Dependency-TrackWhat each release contains, and alerts when a new vulnerability affects it
SigningcosignProof that an image was built by your pipeline
Findings in one placeDefectDojoDeduplicated findings, owners, deadlines, accepted risks

What you get

CI template

One include line per project; versions pinned and updated centrally.

Agreed thresholds

What blocks a merge, what only warns — decided with your developers, not imposed.

Triage process

Who looks at new findings, how false positives are marked, how exceptions expire.

Dashboards

Open findings by team and severity, trend over time, SBOM per release.

Developer guide

Two pages: what the checks do, how to read a finding, how to fix or dispute it.

Handover

Session with developers and with whoever owns security.

How it goes

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.

  1. Step 1 · 1–3 days

    Baseline

    Pilot projects scanned, current findings measured, thresholds proposed. Final fixed price.

  2. Step 2

    Build

    CI template, Dependency-Track and DefectDojo set up; pilot teams use it and give feedback.

  3. Step 3

    Roll-out

    Template added to all agreed projects, in batches, warnings first, blocking later.

  4. Step 4

    Handover

    Dashboards, guide, sessions, tuning of noisy rules.

What we need from you

  • Maintainer access to the GitLab groups in scope.
  • Somewhere to run Dependency-Track and DefectDojo (we can deploy them).
  • One developer per pilot team, and one person who owns security decisions.

Not included

  • Fixing the vulnerabilities found in your code — we help triage and prioritise.
  • Penetration testing.
  • Certifying compliance with any standard.
from $8,000

Fixed price after the measurement in step 1. Paid by milestone.

What changes the price

  • Number of projects and languages.
  • Existing tools to replace or connect.
  • Where the tools run — your servers or ours.

Leaving a commercial scanner? See Snyk / SonarQube exit.

Questions teams ask

Will this slow down our pipelines?

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.

We already have GitLab Ultimate. Is this still useful?

Then we build on GitLab's own scanners and add what is missing, such as Dependency-Track for SBOM monitoring.

How do you deal with false positives?

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.

Does this make us CRA-compliant?

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.

Often done together

Tell us how many projects and which languages

We give you a price range on a 30-minute call.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Book a 30-minute call