Every build pulls packages and images from the internet. Commercial repository firewalls put new ones in quarantine until security has looked at them. We build the same control on open tools: images are scanned and blocked in Harbor, packages enter your internal registry only through an approved merge request, and everything approved keeps being watched.
New dependencies arrive in builds without anyone from security seeing them.
Quarantine for images, an approval flow for packages, monitoring after approval.
Builds use only approved components; every decision has a reviewer and a date.
So you know what the commercial benchmark is:
Same goal — nothing new enters builds without a check — reached with open, generally available tools.
Harbor proxy projects that scan every new image and refuse to serve those above your severity threshold or unsigned.
Allow-list project, check pipeline and publishing into your internal registry, ready for the first requests.
How a developer asks for an exception, who decides, and when the exception expires.
Dependency-Track fed with everything approved; alerts to the owners of affected projects.
One page for developers (how to request a package), one for security (how to review).
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.
What your builds pull today, from where, and how often new dependencies appear. Fixed price and plan.
Harbor proxy projects with scanning and blocking; builds re-pointed.
Allow-list, check pipeline, internal registry; pilot team first.
Dependency-Track, exception process, guides, sessions for developers and security.
Fixed price after the measurement in step 1. Paid by milestone.
Often combined with a DevSecOps Pipeline on GitLab or a Nexus CE clean-up.
For images, no: scanning happens in the proxy. For packages, a new dependency waits for an approval. We agree a response time with security and pre-approve common, well-known packages so the queue stays short.
Those products bring their own threat data and transparent quarantine for packages. Our set-up uses open scanners and an explicit approval step instead. For many teams that is enough; for others the commercial product is worth its price — we tell you which after the measurement.
Yes. Nexus CE can host the approved packages; we add the approval flow and the image quarantine around it.
No. Premium makes approvals by the security group enforceable in one project; on Free we use a separate allow-list project that only security can merge into.
Formats and number of pipelines — enough for a price range on a 30-minute call.