Policy engine
Rules by package name, version range, age, source, license and custom criteria. Block or log-only, with time-limited exceptions. Re-evaluated on every request.
The next generation Dependency Firewall is launching soon. See what’s new
Maven Dependency Firewall
Java, Kotlin and Scala projects pull from Maven Central, JitPack, and internal repositories at once. Deep transitive graphs, slow patching cycles, and dependency confusion against internal group IDs create a large attack surface. The Maven Dependency Firewall intercepts every artifact request before it lands in your build.
Bytesafe Dependency Firewall sits in front of your existing repository, protecting developers, CI/CD pipelines and AI agents.
EU-based company · Software supply chain security since 2018.
bytesafe.dev / Firewall
47
Blocked today
1,284
Requests today
12
Active rules
Package
Rule
Status
malicious-pkg@2.1.0
Malware scan
BLOCKED
lodash@4.17.20
CVSS ≥ 7.0
BLOCKED
react@19.1.1
Allowlist
APPROVED
new-release@0.0.1
Age < 7 days
DELAYED
axios@1.7.9
Allowlist
APPROVED
Blocked
malicious-pkg@2.1.0
By Exception
lodash@4.17.21
Delayed
new-release@0.0.1
Approved
react@19.1.1
Supply chain attacks on Maven
A selection of documented supply chain attacks on Maven. The Maven ecosystem has been targeted by malicious packages, account takeovers, and dependency confusion attacks.
Transitive CVE exposure2026
Java projects typically have deep transitive dependency graphs. A CVE in a deeply nested library can be difficult to trace. The firewall blocks vulnerable transitive packages at the registry level.
VulnerabilityMalicious Maven Central artifacts2023+
Researchers found packages on Maven Central containing obfuscated malicious code. Unlike npm, Maven Central lacks automated malware scanning. Bytesafe Dependency Firewall adds a scanning layer in front of Central.
Malware uploadSpring4Shell2022
CVE-2022-22965 allowed unauthenticated remote code execution in Spring MVC and WebFlux applications. Affected a large portion of the Java web ecosystem due to Spring's market dominance.
Critical CVEDependency confusion2021+
Attackers register public Maven artifacts using the same group IDs and artifact IDs as internal packages. Build tools that query public repositories before private ones resolve the malicious version silently.
Namespace attackLog4Shell (Log4j)2021
CVE-2021-44228 affected Apache Log4j 2, a ubiquitous Java logging library. Remote code execution with a single log message. Discovered in December 2021 with millions of vulnerable deployments still found in production years later.
Critical CVEDependency Firewall does not prevent all attacks, but blocks packages that match known malware signatures, fail provenance checks, or violate your policies.
Intercepts every Maven package request before it reaches you.
Every package install is a potential entry point. Traditional SCA tools find problems after packages are already in your environment. Dependency Firewall intercepts every Maven request before it reaches your developers, CI/CD pipelines or AI agents.
You define the rules: block packages with known CVEs, block known malicious packages, or delay newly published versions for a configurable period to give the ecosystem community time to surface zero-day threats.
Works in front of enterprise repository platforms and any Maven registry. No agent installs. No workflow changes.
Public Maven registry
Vulnerable and malicious versions included
Risky packages
Dependency Firewall
Policy engineVetted packages only
Developers and CI/CD
Internal environment
Dependency Firewall capabilities
Policy controls, malware blocking, package delay, provenance checks, publish scanning, and full audit visibility across every Maven request.
Vulnerability blocking
Block packages with known CVEs before install. Filter by CVSS and EPSS severity per registry or team. New advisories take effect immediately.
Malware scanning
Detect malicious payloads, suspicious install hooks and obfuscated code before execution. Quarantined packages are logged and never silently dropped.
Provenance verification
Verify packages were built by expected publishers using Sigstore and SLSA attestations. Detect pipeline swaps and version downgrades early.
Dependency confusion
Block namespace attacks where public packages impersonate your internal ones. Configurable upstream priority rules ensure private packages always win.
Zero-day safety delay
Hold newly published versions for a configurable window (7 or 14 days) before they reach developers or pipelines. Gives the ecosystem time to surface threats.
Package observations
Every package is fingerprinted: first-seen date, download frequency, requester, version age. Know exactly what passed through and when.
Audit logging
Every block, allow and exception is recorded and exportable to your SIEM. Built to make security teams and auditors happy out of the box.
Publish scanning
Packages are scanned for malware, secrets, and sensitive data before they are published to an upstream registry.
Add a security layer to Maven
Route Maven package traffic through Dependency Firewall, define policies for what's allowed and let the firewall block the rest. Developers and pipelines keep their existing package manager commands.
01
Route Maven requests through Dependency Firewall
Point your Maven configuration at Dependency Firewall. Every install request passes through the firewall before reaching the registry or your environment.
02
Define your security policies
Set vulnerability thresholds, enable malware scanning, configure safety delays for new versions and write allowlist or blocklist rules. Create multiple firewalls with individual rules for different teams or projects.
03
Bad packages are blocked. Safe ones flow through.
Every request is evaluated in real time. Blocked packages are logged with the policy that triggered them. Approved packages are served transparently.
Configure Maven or Gradle to proxy through Bytesafe Dependency Firewall
Add a mirror entry to your Maven settings.xml or configure a Gradle dependency resolution management block. CI/CD environments pick up the configuration automatically from the shared settings file.
Works with the repositories you already use
JFrog Artifactory
Sonatype Nexus
GitLab
GitHub Packages
Azure Artifacts
AWS CodeArtifact
Firewall rules
Each rule targets an ecosystem and applies a condition: vulnerability severity, package age, license type or name pattern. Rules either block or log. Stack multiple rules per firewall. Changes take effect immediately.
Security teams can start with broad guardrails, then narrow policies by upstream, package, version range, internal status, maximum age, CVSS score and EPSS score.
Live firewall logs
Every blocked package is logged: package name, version, status, ecosystem, which firewall evaluated it, which rule triggered and who requested it. Filter by firewall or user.
The log view gives developers a fast answer when an install fails and gives AppSec a complete audit trail for policy enforcement.
Package details and scorecards
Open a package to review advisories, licenses, project metadata, OpenSSF Scorecard checks, dependency counts and source links before deciding whether to block, allow or investigate further.
The package page brings runtime firewall context together with upstream project health. Security teams can compare CVEs, maintainer signals, and repository hygiene from the same screen.
Sits in front of what you already run
Other enterprise dependency firewalls are often bundled into repository platforms. Dependency Firewall is an independent firewall that works with any registry and is built in the EU.
| Criterion | Dependency Firewall | Other enterprise firewalls |
|---|---|---|
| Works with your existing repository | Yes, as a proxy in front of it | Bundled into their platform most often |
| Deploys in minutes | Yes | Usually weeks of platform work most often |
| Predictable pricing | Flat, no usage-based fees | Usage-based or opaque most often |
| EU data sovereignty | Yes | No, US-based most often |
Maven Dependency Firewall: frequently asked questions
Common questions from security and engineering teams.
How do I configure Maven to use Bytesafe Dependency Firewall?
Add a mirror entry to your settings.xml pointing at your Bytesafe Dependency Firewall endpoint. The mirrorOf field can be `central`, `*`, or a comma-separated list of repository IDs to mirror. See docs.bytesafe.dev for the full configuration reference.
Does it work with Gradle?
Yes. Configure your Gradle project to use the Bytesafe Dependency Firewall URL as a repository in dependencyResolutionManagement (settings.gradle) or as a project-level repository. Both Maven and Gradle work with the same endpoint.
Can I mirror internal Nexus or Artifactory repositories?
Yes. Bytesafe Dependency Firewall can proxy multiple upstreams including Sonatype Nexus, JFrog Artifactory, and Maven Central. Internal group IDs resolve to your private repository, preventing dependency confusion attacks.
Does blocking a transitive dependency break the build?
Yes. If a transitive dependency is blocked, the build fails with a 404 or policy error at the point where that artifact is requested. The firewall log shows the exact artifact, version, rule, and requester.
Can different projects have different policies?
Yes. You can create separate firewalls per project. They are lightweight and easy to clone. You can also differentiate by the user or token used for the session. Firewall configurations are small JSON files that can be managed in Git.
Can packages be delayed before they reach developers?
Yes. Dependency Firewall can hold newly published package versions for a configurable window (7 or 14 days) before they reach developers or pipelines. Centralizing delay rules means the protection applies automatically across all teams and pipelines without each project configuring it separately.
What happens if a package passes through but malware is found later?
The firewall tracks all packages via observations: first-seen date, last-seen date, and which firewalls they passed through. When new malware data surfaces, you can see exactly which projects downloaded the affected package and when.
Can firewall rules be automated?
Yes. All configuration is available via API. Configurations can be version-controlled in Git and deployed through your existing automation. All changes are tracked with full rollback support.
Does Dependency Firewall work with enterprise repository platforms?
Yes. Dependency Firewall speaks the same protocols as your package managers, so it is fully transparent to enterprise repository platforms and package registries, including JFrog Artifactory, Sonatype Nexus, GitLab, GitHub Packages and Azure Artifacts.
How is licensing structured?
Two plans: Cloud for SaaS and Enterprise for custom deployment, Managed Cloud or On-Premise. Both include unlimited users, package requests and bandwidth with no usage-based fees. See pricing for plan details and add-ons.
Watch it block Maven threats
Book a 30-minute session and we'll show you how Dependency Firewall fits into your existing setup. Your registries stay unchanged.