Dependency Firewall offer: 50% off the base fee. See pricing

Dependency Firewallfor Maven

Your rules check every artifact Maven and Gradle resolve and block risky versions before they reach the build.

  • Built in Sweden and hosted in the EU
  • Supply chain security since 2018

Supported Maven upstreams

Maven Central
JFrog Artifactory
Sonatype Nexus
GitLab
GitHub Packages
Azure Artifacts
AWS CodeArtifact

Any Maven-compatible repository can be an upstream.

Connect one project or the whole company

Package manager config

Set the registry per project

One <mirror> entry in settings.xml sends Maven Central, your own repositories and plugin repositories through the firewall.

settings.xml
<mirror>  <id>firewall</id>  <url>https://FIREWALL_HOST/v1/NAMESPACE_ID/maven/FIREWALL_ID/</url>  <mirrorOf>*</mirrorOf></mirror>

Best for: trying it on one project, CI pipelines, teams that own their config.

Web proxy chaining

Route the company through your web proxy

Your web proxy hands Maven traffic to the firewall. Nothing changes on developer machines.

  1. Laptop, CI or agentPackage managerMaven Central
  2. Web proxyZscaler, Prisma Access, Squid
  3. Your rulesDependency Firewall

Best for: every laptop and agent at once, including machines nobody has configured.

Web proxy chaining

What your team sees after a block

1 of 3 · Logs

Live firewall logs

Every request is logged: package name, version, status, ecosystem, which firewall evaluated it, which rule triggered and who requested it. Filter by firewall or user, and tail live during incidents or CI/CD runs.

Developers get a fast answer when an install fails, and AppSec gets an audit trail for every decision.

Maven Central incidents and the rule that covers each

  • Log4Shell (Log4j)

    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.

    Vulnerability blocking
  • Spring4Shell

    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.

    Vulnerability blocking
  • Dependency confusion

    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.

    Dependency confusion

Clients, proxies and deployment

  • Clients

    Maven and Gradle.

  • Web proxies

    Zscaler, Prisma Access, Squid and other web proxies that decrypt TLS.

  • Deployment

    Cloud as EU-hosted SaaS. Enterprise as Managed Cloud, BYO Cloud or On-Premise.

Explore supported ecosystems

See the setup, rules and incidents for each package ecosystem.

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 the firewall sit in front of internal Nexus or Artifactory repositories?
Yes. A firewall can have several upstreams, such as Sonatype Nexus, JFrog Artifactory and Maven Central. It proxies requests to them and copies nothing in advance. Internal group IDs resolve from your private repository, which prevents dependency confusion.
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 Maven 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 Maven installs go through the firewall without changing developer machines?
Yes, with web proxy chaining. A company web proxy that already decrypts TLS, such as Zscaler, Prisma Access or Squid, hands registry traffic to the firewall. Package managers keep the public registry address, and rules, exceptions and logs apply as with a configured client. It is set up on request. Web proxy chaining
What happens if a Maven 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 own 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 transparent to enterprise repository platforms and package registries, including JFrog Artifactory, Sonatype Nexus, GitLab, GitHub Packages and Azure Artifacts. It can also sit directly in front of the public registry.
How is licensing structured?
Cloud is the SaaS plan. Enterprise is for custom deployment, Managed Cloud or On-Premise. Cloud is priced on whichever you use most: active users, packages scanned or downloads served. Plan details and add-ons

Put Maven installs behind the firewall

Point one pipeline at Dependency Firewall and read the decisions in the log. The trial runs for 14 days.