Running MySQL & MariaDB Server securely in 2019
summary
Comparisons target MySQL 8 vs MariaDB 10.3/10.4 with concrete steps: enable caching_sha2_password for modern auth, run mysql_ssl_rsa_setup to get TLS certs, and keep SELinux and iptables enforcing while deploying a secure 3‑node Galera Cluster (MariaDB 10.4) that actually works with encrypted cluster traffic and MariaDB gcache encryption. Benchmarks show SSL and tablespace encryption cost near 0–3% overhead; use Percona or MariaDB audit plugins, Amazon KMS or Percona Vault for key management, and MariaBackup for encrypted backups.
AI-written summary · about
chapters (33)
- 0:00Start
- 4:30Secure your databases
- 5:47Historically...
- 6:40Signs of poor security
- 8:11Trust based security
- 9:40Password snooping
- 11:42Password attacks
- 13:37Data theft
- 14:24Structured Query Language (SQL)
- 14:40MySQL security by version
- 15:31Key security features by version
- 17:07Installation Default Passwords
- 20:09Security Hardening 101
- 21:03PASSWORD EXPIRE
- 21:21MySQL 8 improvements
- 23:03MariaDB Server passwords
- 24:33Default client connection traffic (5.6)
- 25:075.7 non-SSL client connection traffic
- 25:20SSL system variables
- 26:16Stronger passwords (sha256)
- 26:49Configuring PAM (Demo only)
- 27:11Installing PAM Plugin
- 28:07MariaDB Authentication Plugins
- 29:04Unix Socket Authentication (MariaDB 10.1)
- 29:14Auditing Plugin Options
- 29:49MariaDB Audit Log Format
- 30:03Auditing Implementation
- 30:36Secure Storage
- 31:14Encryption in MariaDB Server III
- 32:02Encryption in MySQL
- 32:40Encryption conclusions
- 33:55Data Masking
- 34:47Firewalls...
