Security Hardening: MongoDB / Redis / Elasticsearch
Symptom
Ziel: NoSQL-/Datenspeicher nach CIS-Art härten – Authentifizierung, Netzwerkbeschränkung, Sperren gefährlicher Befehle, TLS, Least-Privilege-Rollen und Auditing.
1. Authentifizierung AKTIVIEREN – nicht authentifizierten Zugriff unterbinden
Diese Produkte werden oft mit standardmäßig DEAKTIVIERTER Authentifizierung ausgeliefert und kompromittiert, wenn sie offen im Internet stehen. Aktiviere die Authentifizierung und lege einen Administrator an.
MongoDB
// mongod.conf:
security:
authorization: enabled
// Create an administrator user (first time, via the localhost exception):
use admin
db.createUser({ user: "admin", pwd: passwordPrompt(),
roles: [ { role: "userAdminAnyDatabase", db: "admin" } ] })
// Then connect with: mongosh -u admin --authenticationDatabase adminRedis
# redis.conf — ACL (Redis 6+): disable the default user, define named users:
user default off
user admin on >AdminPassword789! ~* &* +@all
user app on >AppPassword456! ~app:* +@read +@write
# Note: requirepass is a legacy compatibility setting that only sets the 'default' user's password;
# do not confuse it with ACL users. You can also keep users in an aclfile (persisted with ACL SAVE).Elasticsearch
# 8.x: security (authentication + TLS) is configured automatically on first start; elasticsearch.yml:
xpack.security.enabled: true
# Set/reset the password of the 'elastic' user:
bin/elasticsearch-reset-password -u elastic
# (elasticsearch-setup-passwords is deprecated since 8.0)
# Create separate users with dedicated roles for Kibana/clients instead of 'elastic'.2. Netzwerk beschränken – nur benötigte Interfaces und Ports öffnen
Vermeide, dass der Dienst auf 0.0.0.0 für alle lauscht. Binde die Adresse an ein internes Interface/Loopback und aktiviere den Protected Mode.
MongoDB
# mongod.conf — internal interface + loopback only:
net:
bindIp: 127.0.0.1,10.0.0.10
port: 27017
# Never use bindIpAll: true; limit the port with a firewall.Redis
# redis.conf:
bind 127.0.0.1 10.0.0.10
protected-mode yes
port 6379
# protected-mode blocks external access when no password is set;
# still limit 6379 with a firewall.Elasticsearch
# elasticsearch.yml — pin the listening interface:
network.host: 10.0.0.10
http.port: 9200
transport.port: 9300
# Open only the required ports in the firewall;
# 9300 (transport) must never be exposed externally.3. Gefährliche Befehle einschränken
Ein einziger Befehl kann alle Daten löschen. Benenne destruktive/administrative Befehle um oder entferne sie, oder blockiere Wildcard-Ziele.
MongoDB
// Use role-based control instead of a separate command block:
// Grant destructive privileges (dropDatabase, dropCollection) only to
// dbAdmin/clusterAdmin roles; do not grant them to the application user.
db.grantRolesToUser("app", [ { role: "readWrite", db: "appdb" } ])
// Do NOT grant dbAdmin/root to the application user.Redis
# For Redis 6+ the preferred way is ACLs (do not give the application user dangerous commands):
# ACL SETUSER app ... -@dangerous
# Legacy method — disable/rename commands in redis.conf:
rename-command FLUSHALL ""
rename-command FLUSHDB ""
rename-command KEYS ""
rename-command DEBUG ""
# Caution: renaming CONFIG can break Sentinel, CONFIG REWRITE and management tools.Elasticsearch
# elasticsearch.yml — block wildcard/all-index deletion:
action.destructive_requires_name: true
# This rejects DELETE /* or DELETE /_all;
# bulk deletion is not possible without naming the index explicitly.4. TLS/verschlüsselte Verbindungen aktivieren
Zugangsdaten und Daten dürfen nicht unverschlüsselt über ein offenes Netzwerk laufen. Aktiviere TLS für Client- und knotenübergreifenden Verkehr.
MongoDB
# mongod.conf — client TLS:
net:
tls:
mode: requireTLS
certificateKeyFile: /etc/ssl/mongodb.pem
CAFile: /etc/ssl/ca.pem
# Client: mongosh --tls --tlsCAFile ca.pemRedis
# redis.conf — enable TLS, close the plain port:
port 0
tls-port 6379
tls-cert-file /etc/redis/redis.crt
tls-key-file /etc/redis/redis.key
tls-ca-cert-file /etc/redis/ca.crtElasticsearch
# elasticsearch.yml — HTTP and transport TLS:
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.keystore.path: http.p12
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: transport.p125. Least-Privilege-Rollen vergeben – breite Rollen vermeiden
Gib jedem Benutzer nur den Zugriff, den seine Aufgabe erfordert. Verwende statt breiter/administrativer Rollen feingranulare Rollen, die auf bestimmte Datenbanken, Key-Muster oder Indizes begrenzt sind.
MongoDB
// Instead of broad readWrite, grant only on the required DB;
// define a custom role if needed:
db.createRole({ role: "ordersRW",
privileges: [ { resource: { db: "appdb", collection: "orders" },
actions: [ "find", "insert", "update" ] } ], roles: [] })
db.grantRolesToUser("app", [ { role: "ordersRW", db: "appdb" } ])Redis
# Limit by key pattern and command category with ACLs:
ACL SETUSER app on >AppPassword456! ~app:* +@read +@write -@dangerous
# Only keys with the 'app:' prefix, read/write; dangerous commands forbidden.
ACL LIST
ACL WHOAMIElasticsearch
# Define a fine-grained role (read-only on specific indices):
POST /_security/role/orders_read
{ "indices": [ { "names": [ "orders-*" ],
"privileges": [ "read" ] } ] }
# Assign it to the user:
POST /_security/user/app
{ "password": "...", "roles": [ "orders_read" ] }6. Auditing/Logging aktivieren – Zugriffe und Änderungen überwachen
Unbefugte Zugriffsversuche und administrative Vorgänge müssen aufgezeichnet werden. Aktiviere das Audit Log und leite es an eine zentrale Stelle weiter.
MongoDB
# Auditing (requires MongoDB Enterprise) — mongod.conf:
auditLog:
destination: file
format: JSON
path: /var/log/mongodb/audit.json
# Filter: capture events such as authenticate, createUser, dropDatabase.Redis
# Redis has no full audit; use ACL LOG to see rejected
# authentication/command attempts:
ACL LOG
ACL LOG RESET
# Also: route the loglevel notice and logfile settings to a central collector.Elasticsearch
# elasticsearch.yml — enable security auditing:
xpack.security.audit.enabled: true
xpack.security.audit.logfile.events.include:
[ authentication_failed, access_denied, connection_denied ]
# Records are written to the <cluster>_audit.json file.