How to Secure MySQL Database Server

Share this Article :

A Default MySQL installation is completely vulnerable to attacks. MySQL installation should be made as secure as possible. This is to protect the data collections and the information maintained by the MySQL server from unauthorized or anonymous access. In This post, i will share with you on how to secure your database server with the simple configuration and wizard.

Default and unsecured MySQL database:

    mysql> select user,host,password from mysql.user;
    +------+-----------+------------------+
    | user | host      | password         |
    +------+-----------+------------------+
    | root | localhost |                  |
    | root | CentOS57  |                  |
    | root | 127.0.0.1 |                  |
    |      | localhost |                  |
    |      | CentOS57  |                  |
    +------+-----------+------------------+
    5 rows in set (0.00 sec)
    

root password has not been set and anonymous user can access this MySQL server.

Also Read :   Rescan SCSI Bus to Add or Remove a SCSI Devices on Linux

Simply run this command to secure MySQL server:

    [[email protected] ~]# /usr/bin/mysql_secure_installation
    
    [[email protected] ~]# /usr/bin/mysql_secure_installation
    
    
    
    
    NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
          SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!
    
    
    In order to log into MySQL to secure it, we'll need the current
    password for the root user.  If you've just installed MySQL, and
    you haven't set the root password yet, the password will be blank,
    so you should just press enter here.
    
    Enter current password for root (enter for none):
    OK, successfully used password, moving on...
    
    Setting the root password ensures that nobody can log into the MySQL
    root user without the proper authorisation.
    
    Set root password? [Y/n] y
    New password:
    Re-enter new password:
    Password updated successfully!
    Reloading privilege tables..
     ... Success!
    
    
    By default, a MySQL installation has an anonymous user, allowing anyone
    to log into MySQL without having to have a user account created for
    them.  This is intended only for testing, and to make the installation
    go a bit smoother.  You should remove them before moving into a
    production environment.
    
    Remove anonymous users? [Y/n] y
     ... Success!
    
    Normally, root should only be allowed to connect from 'localhost'.  This
    ensures that someone cannot guess at the root password from the network.
    
    Disallow root login remotely? [Y/n] n
     ... skipping.
    
    By default, MySQL comes with a database named 'test' that anyone can
    access.  This is also intended only for testing, and should be removed
    before moving into a production environment.
    
    Remove test database and access to it? [Y/n] n
     ... skipping.
    
    Reloading the privilege tables will ensure that all changes made so far
    will take effect immediately.
    
    Reload privilege tables now? [Y/n] y
     ... Success!
    
    Cleaning up...
    
    
    
    All done!  If you've completed all of the above steps, your MySQL
    installation should now be secure.
    
    Thanks for using MySQL!
    

Secure MySQL database :

    mysql> select user,host,password from mysql.user;
    +------+-----------+------------------+
    | user | host      | password         |
    +------+-----------+------------------+
    | root | localhost | 5d2e19393cc5ef67 |
    | root | CentOS57  | 5d2e19393cc5ef67 |
    | root | 127.0.0.1 | 5d2e19393cc5ef67 |
    +------+-----------+------------------+
    3 rows in set (0.00 sec)
    

Above steps is not the complete solutions to secure your production MySQL server. It just only basics how-to steps from my own experiences. I highly recommend you to read through the following article:
http://dev.mysql.com/doc/refman/5.0/en/security.html
http://dev.mysql.com/doc/refman/5.0/en/default-privileges.html


Leave a Reply