Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/dev-sec/ansible-mysql-hardening
This Ansible role provides security configuration for MySQL.
https://github.com/dev-sec/ansible-mysql-hardening
ansible database hardening mysql mysql-hardening playbook protection role security
Last synced: 2 months ago
JSON representation
This Ansible role provides security configuration for MySQL.
- Host: GitHub
- URL: https://github.com/dev-sec/ansible-mysql-hardening
- Owner: dev-sec
- Archived: true
- Created: 2015-07-02T16:28:08.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2020-11-16T19:54:29.000Z (about 4 years ago)
- Last Synced: 2024-08-03T09:05:22.758Z (6 months ago)
- Topics: ansible, database, hardening, mysql, mysql-hardening, playbook, protection, role, security
- Language: Ruby
- Homepage: http://dev-sec.io/
- Size: 108 KB
- Stars: 140
- Watchers: 28
- Forks: 29
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
Awesome Lists containing this project
- awesome-list-ansible - ansible-mysql-hardening
README
# mysql-hardening (Ansible role)
**Attention:** This role has been migrated to our hardening-collection:
* https://github.com/dev-sec/ansible-os-hardening/
* https://galaxy.ansible.com/devsec/hardening
## Requirements
* Ansible
* Set up `mysql_root_password` variable
## Installation
Install the role with ansible-galaxy:
```sh
ansible-galaxy install dev-sec.mysql-hardening
```
### Example Playbook
```yml
- hosts: localhost
roles:
- dev-sec.mysql-hardening
```
This hardening role installs the hardening but expects an existing installation of MySQL, MariaDB or Percona. Please ensure that the following variables are set accordingly:
* `mysql_hardening_enabled: yes` role is enabled by default and can be disabled without removing it from a playbook. You can use conditional variable, for example: `mysql_hardening_enabled: "{{ true if mysql_enabled else false }}"`
* `mysql_hardening_user: 'mysql'` The user that mysql runs as.
* `mysql_datadir: '/var/lib/mysql'` The MySQL data directory
* `mysql_hardening_mysql_hardening_conf_file: '/etc/mysql/conf.d/hardening.cnf'` The path to the configuration file where the hardening will be performed
## Role Variables
* `mysql_hardening_chroot`
* Default: ""
* Description: [chroot](http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_chroot)
* `mysql_hardening_options.safe-user-create`
* Default: 1
* Description: [safe-user-create](http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_safe-user-create)
* `mysql_hardening_options.secure-auth`
* Default: 1
* Description: [secure-auth](http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_secure-auth)
* `mysql_hardening_options.skip-symbolic-links`
* Default: 1
* Description: [skip-symbolic-links](http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_symbolic-links)
* `mysql_hardening_skip_grant_tables:`
* Default: false
* Description: [skip-grant-tables](https://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_skip-grant-tables)
* `mysql_hardening_skip_show_database`
* Default: 1
* Description: [skip-show-database](http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_skip-show-database)
* `mysql_hardening_options.local-infile`
* Default: 0
* Description: [local-infile](http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_local_infile)
* `mysql_hardening_options.allow-suspicious-udfs`
* Default: 0
* Description: [allow-suspicious-udfs](https://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_allow-suspicious-udfs)
* `mysql_hardening_chroot.automatic-sp-privileges`
* Default: 0
* Description: [automatic_sp_privileges](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_automatic_sp_privileges)
* `mysql_hardening_options.secure-file-priv`
* Default: /tmp
* Description: [secure-file-priv](https://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_secure-file-priv)
* `mysql_allow_remote_root`
* Default: false
* Description: delete remote root users
* `mysql_remove_anonymous_users`
* Default: true
* Description: remove users without authentication
* `mysql_remove_test_database`
* Default: true
* Description: remove test database
Further information is available at [Deutsche Telekom (German)](http://www.telekom.com/static/-/155996/7/technische-sicherheitsanforderungen-si) and [Symantec](http://www.symantec.com/connect/articles/securing-mysql-step-step)
## Local Testing
The preferred way of locally testing the role is to use Docker. You will have to install Docker on your system. See [Get started](https://docs.docker.com/) for a Docker package suitable to for your system.
You can also use vagrant and Virtualbox or VMWare to run tests locally. You will have to install Virtualbox and Vagrant on your system. See [Vagrant Downloads](http://downloads.vagrantup.com/) for a vagrant package suitable for your system. For all our tests we use `test-kitchen`. If you are not familiar with `test-kitchen` please have a look at [their guide](http://kitchen.ci/docs/getting-started).
Next install test-kitchen:
```sh
# Install dependencies
gem install bundler
bundle install
```
### Testing with Docker
```sh
# list all available machines
bundle exec kitchen list
# fast test on one machine
bundle exec kitchen test mysql-centos7-ansible-latest
# test on all machines
bundle exec kitchen test
# for development
bundle exec kitchen create mysql-centos7-ansible-latest
bundle exec kitchen converge mysql-centos7-ansible-latest
```
### Testing with Virtualbox
```sh
# fast test on one machine
KITCHEN_YAML=".kitchen.vagrant.yml" bundle exec kitchen test default-ubuntu-1404
# test on all machines
KITCHEN_YAML=".kitchen.vagrant.yml" bundle exec kitchen test
# for development
KITCHEN_YAML=".kitchen.vagrant.yml" bundle exec kitchen create default-ubuntu-1404
KITCHEN_YAML=".kitchen.vagrant.yml" bundle exec kitchen converge default-ubuntu-1404
```
For more information see [test-kitchen](http://kitchen.ci/docs/getting-started)
## License and Author
* Author:: Sebastian Gumprich
* Author:: Anton Lugovoi
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
[1]: http://travis-ci.org/dev-sec/ansible-mysql-hardening
[2]: https://gitter.im/dev-sec/general
[3]: https://galaxy.ansible.com/dev-sec/mysql-hardening/