TMA-COCKROACHDB-2.2
Ensure Each CockroachDB Node Runs as a Dedicated Process on a Separate Host
Description
For all self-hosted VM or bare-metal production deployments (on-premises or on cloud providers like AWS, GCP, Azure), each CockroachDB node must run as a single, dedicated cockroach start process on its own physical or virtual machine (VM). The benchmark rates this recommendation Manual; the automated check covers its objective pass criterion. Passes when exactly one cockroach start process runs on this host (FAIL when none runs). Also confirm the store directory is not shared with another node.
How it is checked
Audit method: Shell command
out=$(ps -eo args= | grep '[c]ockroach start') || exit 1; printf '%s\n' "$out" | awk 'END {print (NR == 1) ? "compliant" : NR " processes"}'- Expected output
compliant
How it is fixed
Fix method: Guidance or infrastructure patch
Stop the extra cockroach start processes (systemctl stop ...), provision a dedicated VM/host with its own storage for each additional node and redeploy it there.
Properties
- Operating systems
- Any
- Tags
- cockroachdbarchitecture
- Reference
- CIS CockroachDB v25.x Benchmark v1.0.0 - 2.2 Ensure Each CockroachDB Node Runs as a Dedicated Process on a Separate Host
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
tmaegis scan --target cockroachdb