Achieving PCI Compliance With Percona Server for MongoDB, or Getting as Close as Possible
summary
Describes a concrete checklist to get Percona Server for MongoDB toward PCI: enable envelope encryption for at‑rest data (master key external, supports HashiCorp Vault or local keyfile with strict permissions), enable TLS 1.2 for in‑transit encryption, and turn on audit logging (JSON/BSON, filters for auth and DDL events). Explains how to migrate encryption into a replica set by adding an encrypted node, and emphasizes that configuration plus organizational controls (PCI DSS vs SSF) — not defaults — determine compliance.
AI-written summary · about
chapters (13)
- 0:00Start
- 3:40Data Security Standards
- 4:14Pci Dss
- 14:5110 Track and Monitor all Accesses To Network Resources and Cardholder Data
- 16:06Use of Cryptography
- 20:09Data Rest Encryption
- 21:20Key Management
- 23:41Generate a Key File
- 24:27Enabling Encryption in Transit or Tls 1 2
- 26:38Enable Audit Logging
- 28:12Regular Expressions
- 28:51Causes of Breaches
- 29:30Strong Authentication
related talks
33mKey Management for Data-at-Rest Encryption in Percona Server for MongoDB
09mOpen Software for MongoDB Where Percona Fits
25mPercona Server for MongoDB: Features Overview
21mWhy Pay for MongoDB Enterprise When Open Source Has You Covered?
53mExternal Authentication 101 With Percona Server for MySQL, MongoDB and PostgreSQL and PMM
47mBreakout Session
15mMongoDB Security: Making Things Secure by Default
38mRunning MySQL & MariaDB Server securely in 2019