neo4j

What is Neo4j?

The Neo4j image packages the Neo4j graph database server so teams can run a graph database in a container without installing and tuning it on the host. Neo4j stores data natively as nodes, relationships, and properties and is queried with the Cypher language, which makes it well suited to highly connected data — knowledge graphs, fraud and anomaly detection, identity and access graphs, network and IT topology, recommendation engines, and GraphRAG for AI applications. The image exposes the Bolt protocol on port 7687 and the Neo4j Browser on port 7474, is configured through NEO4J_* environment variables and neo4j.conf, and persists the database to mounted volumes. It is used by data engineering and application teams running development and CI instances, and by platform teams operating Neo4j on Kubernetes with a reproducible, version-pinned image.

What is Echo's Neo4j image?

Echo's Neo4j image is a hardened build of Neo4j on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your neo4j.conf settings, plugins such as APOC, and data volumes. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:

• Distroless variant — optimized for runtime use, with the smallest possible attack surface
• Default variant — includes essential build tools, package managers, and shells for teams that need operational access

For production Neo4j deployments, the distroless variant keeps all runtime operations — Cypher query execution, transaction processing, Bolt connections, and storage operations — fully intact while minimizing exposure; the default variant suits data and platform teams that need shell access for running cypher-shell, tuning memory settings, or diagnosing query performance.

What is the difference between Echo's Neo4j image and the public Neo4j image?

Public Neo4j images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a graph database server used in production. Neo4j images run continuously with access to connected application data, user credentials, and TLS keys. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and the bundled JVM dependencies — create exploitable paths that bypass application-layer controls entirely, allowing attackers to move from a network-reachable service to host-level access. For teams running Neo4j across many environments, the image is also a steady source of scanner noise in the CI pipeline — every package in the base becomes a finding your security team must triage, even when none of it is reachable from the service. Echo's build retains everything Neo4j needs for Cypher query execution, transaction processing, Bolt connections, and storage operations while removing the packages that don't belong in a production Neo4j graph database server. As we covered in our post on how to protect your company from software supply chain attacks, long-running services that hold sensitive data and listen on the network are among the widest attack surfaces in the container stack. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo images are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.

FAQ

Can I replace my Neo4j image with Echo's Neo4j image?

Yes. Echo's Neo4j image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. Bolt and HTTP connectivity, authentication settings, plugins such as APOC, neo4j.conf tuning, and mounted data volumes all continue to work without changes to your Cypher queries or driver configuration.

Is Echo's Neo4j image FIPS-validated?

Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running Neo4j workloads inside FedRAMP boundaries, where a graph database server that stores highly connected data and authenticates Bolt client connections must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Neo4j image.

What is Echo's vulnerability management SLA on the Neo4j image?

Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a long-running service that holds connected application data, user credentials, and TLS keys and is reachable over the network.

Is Echo's Neo4j image distroless?

Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production Neo4j deployments, the distroless variant is the leaner, more secure choice; for data and platform teams that need shell access for running cypher-shell, tuning memory settings, or diagnosing query performance, the default variant is the right fit.

How does Echo achieve such a drastic CVE reduction in Neo4j?

Echo's Neo4j image is built from source with only the absolute essentials needed to run the Neo4j graph database server, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Neo4j version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.

Will Echo's Neo4j image help us achieve FedRAMP?

Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For data and platform teams running Neo4j under an ATO — whether that's an identity graph, a threat-intelligence knowledge graph, or a supply chain relationship store — Echo's hardened Neo4j image keeps the graph database server layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍