MySQL Security: Best Practices
MySQL Security: Best Practices
Manizha Davis
Oracle Enterprise Architect
[email protected]
The development, release, and timing of any features or functionality described for
Oracle’s products remains at the sole discretion of Oracle.
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal/Restricted/Highly Restricted 3
Goals are simple
• Protect Data
– From those who shouldn’t see it
– Don’t lose the data
• Maintain Data Availability
Security
SSL/TLS Block Threats
Firewall &
Public/Private Key Encryption Auditing
Auditing
Transparent Encryption Regulatory Compliance
Key Management Login and Query Activities
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential – Internal 12
Regulatory Compliance
• Regulations
– PCI – DSS: Payment Card Data
– HIPAA: Privacy of Health Data
– Sarbanes Oxley, GLBA, The USA Patriot Act:
Financial Data, NPI "personally identifiable financial information"
– FERPA – Student Data
– EU General Data Protection Directive: Protection of Personal Data (GDPR)
– Data Protection Act (UK): Protection of Personal Data
• Requirements
– Continuous Monitoring (Users, Schema, Backups, etc)
– Data Protection (Encryption, Privilege Management, etc.)
– Data Retention (Backups, User Activity, etc.)
– Data Auditing (User activity, etc.)
• X.509
– Server authenticates client via certificates
• MySQL Native, SHA 256 Password plugin
– Native uses SHA1 or plugin with SHA-256 hashing and per user salting for user account passwords.