How to Configure Neo4j Encryption at REST

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up neo4j encryption at rest by encrypting the underlying storage volume. The graph database engine relies on the host system to lock disk files. Teams often mount encrypted block storage and think their sensitive graph data is safe. Still, broad database roles still let logged-in users read plain text nodes. Disk rules only protect your files if someone steals a physical drive. How to set up neo4j encryption at rest The graph database does not lock its own store files on the disk. Ins

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up neo4j encryption at rest by encrypting the underlying storage volume. The graph database engine relies on the host system to lock disk files. Teams often mount encrypted block storage and think their sensitive graph data is safe. Still, broad database roles still let logged-in users read plain text nodes. Disk rules only protect your files if someone steals a physical drive.

How to set up neo4j encryption at rest

The graph database does not lock its own store files on the disk. Instead, it writes standard files to a chosen directory on your server. To protect these files, you must turn on disk locking in your host OS. On Linux hosts, teams use standard volume encryption tools to lock the mount point. The OS unlocks blocks in memory when the database process reads or writes data.

In cloud setups, the workflow is even simpler for platform teams. You attach an encrypted block volume from your cloud provider to the host instance. The cloud platform manages the master keys through its own key service. You mount that volume to the path where the database keeps its data. You should also map transaction logs and backup folders to that same locked volume.

For managed cloud graph services, the provider turns on storage locking by default. Some high-tier plans let you bring your own master key for extra control. When you rotate that key, the storage layer re-wraps the volume keys behind the scenes. The database engine keeps running and does not know the disk is locked.

How to secure backups and log directories

Setting up neo4j encryption at rest requires more than locking the main data folder. A graph system writes data to several paths during normal daily operations. Transaction logs hold every graph change before it lands in the main store. If those logs sit on an open volume, an attacker can read raw records.

Database dumps and offline backups create another big risk for your team. When an engineer runs a backup job, the tool writes a single file. If the backup script sends that file to an open bucket, the protection fails. You must verify that every target bucket and mount point uses strong volume keys. You also need strict host permissions so other server apps cannot read the mount.

Encryption at Rest + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

What disk locking solves and what it misses

Storage locking solves one narrow problem for security and platform teams. It stops someone from reading raw disk blocks without the master volume key. This helps you pass audits that check for stolen drives or unlinked cloud snapshots. Once the server boots and mounts the volume, the OS reads the data in plain text.

To the running database engine, the locked disk looks like any normal folder. Any user or app with a valid login can query the full graph. Disk keys do not check who runs a query or what nodes they pull. If a developer logs in with a shared admin role, they get everything. They can pull emails, phone numbers, card numbers, or national IDs in one query.

Native database roles also leave a wide operational gap during live sessions. Roles decide who can log in and which labels they can read. They do not inspect individual Cypher statements in flight or limit bulk exports. They also cannot rewrite sensitive properties like emails or card numbers in query results. True data safety requires controls that sit in front of the live database session.

Check database and API queries on the wire

Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.

Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.

Frequently asked questions

Does Neo4j have a built-in setting for disk encryption?

No, the database engine does not encrypt its own store files on disk. You must use OS disk tools or encrypted cloud volumes below the database.

Which folders need to sit on an encrypted volume?

You should place the data directory, transaction logs, and backup paths on locked volumes. Leaving logs or dumps on open disks exposes your raw graph records.

Does neo4j encryption at rest hide sensitive fields from analysts?

No, disk encryption only protects offline files and unmounted drives. Logged-in users still get plain text results unless you mask fields in flight.

The query runs. The emails stay hidden.