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
Any Maven-compatible repository can be an upstream.
Rules that run before the build resolves
Block artifacts with known CVEs
- log4j-core 2.14.1CVE-2021-44228 · CVSS 10.0Blocked
- log4j-core 2.24.3Served
Resolve your group IDs from your own repository
com.acme:billing-core- Nexus, internal3.2.0Resolved
- Maven Central99.0.0Not asked
Keep unapproved licenses out of the build
- slf4j-api 2.0.17MITServed
- commons-lang3 3.19.0Apache-2.0Served
- mysql-connector-j 9.1.0GPL-2.0Blocked
Hold new versions until they have cooled off
<version>[1.21,)</version>- jsoup 1.21.22 days oldHeld
- jsoup 1.21.141 days oldResolved
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.
<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.
- Laptop, CI or agentPackage managerMaven Central
- Web proxyZscaler, Prisma Access, Squid
- Your rulesDependency Firewall
Best for: every laptop and agent at once, including machines nobody has configured.
Web proxy chainingWhat 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.
Why a package was blocked
Open a blocked request to see the package, how old the release is, the rule that stopped it and when it will be allowed.
Add or request a time-limited exception from the same drawer to let one package or version through while the rule keeps applying to everything else. The decision stays attached to the original request, so nothing has to be reconstructed from CI output later.
Every package that passed through
See which packages each firewall served over a period, with ecosystem, version, first-seen and last-seen time, vulnerability signals and request counts.
When a new advisory or malware report appears, search for the package and see where it was observed and when exposure started.
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 blockingSpring4Shell
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 blockingDependency 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.
Questions
How do I configure Maven to use Bytesafe Dependency Firewall?
Does it work with Gradle?
Can the firewall sit in front of internal Nexus or Artifactory repositories?
Does blocking a transitive dependency break the build?
Can different Maven projects have different policies?
Can Maven installs go through the firewall without changing developer machines?
What happens if a Maven package passes through but malware is found later?
Can firewall rules be automated?
Does Dependency Firewall work with enterprise repository platforms?
How is licensing structured?
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.