Why this matters
- VaultCommerce SOC2 audit requires mTLS between services and brokers.
- SCRAM credentials rotated via HashiCorp Vault; no passwords in git.
- ACL deny-by-default with quarterly access reviews.
- Encryption at rest on broker disks via cloud KMS.
TLS encryptionWire security
SASL / SCRAMAuthentication
ACLsAuthorization
mTLS and SASL
Brokers present server cert; clients present client cert (mTLS) plus SCRAM username. ssl.endpoint.identification.algorithm=https prevents MITM. VaultCommerce internal CA signs all Kafka certs; 90-day rotation automated.
Key points
- mTLS — mutual TLS authenticates client and server
- SCRAM rotation — periodic credential refresh without downtime
- ACL audit — log denied and allowed operations
- Encryption at rest — EBS/disk KMS for broker volumes
- Network policy — Kubernetes deny-all except broker port from app namespaces
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Hardening checklist
- VaultCommerce rollout checklist
Test yourself
Answer these before moving on — recall is what makes it stick.