Why this matters
- VaultCommerce uses SASL/SCRAM-SHA-512 + TLS 1.3 on all broker and client connections.
- ACLs follow least privilege: inventory-service can READ orders, WRITE inventory-events only.
- Super users bypass ACLs — limit to break-glass admin principals.
- Security misconfiguration is a compliance audit failure, not just an ops issue.
TLS encryptionWire security
SASL / SCRAMAuthentication
ACLsAuthorization
Authentication stack
Clients present SCRAM credentials; brokers verify against KRaft-stored credentials (or LDAP). security.protocol=SASL_SSL combines encryption and auth. VaultCommerce rotates SCRAM passwords quarterly via Vault secrets injection into Kubernetes.
Key points
- SASL/SCRAM-SHA-512 — username/password challenge-response auth
- TLS/mTLS — encrypt traffic; mTLS adds client certificate identity
- ACL principal — User:service-name mapped from SASL or cert DN
- Operation — READ, WRITE, CREATE, DESCRIBE, CLUSTER_ACTION, etc.
- allow.everyone.if.no.acl.found — must be false in production
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
- ACL patterns
- VaultCommerce rollout checklist
Test yourself
Answer these before moving on — recall is what makes it stick.