Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

What is the procedure for securing a Linux, Apache, MySQL, PHP Server (or even Perl) for production use?

Other than setting the MySQL password and the root password for Linux what other (maybe not so obvious) steps should be taken?

Also what steps can I take, if I was going to be extra paranoid, that may not normally be necessary?

This is for a basic single site use but must be secure.

share|improve this question
    
Apache Hardening on a sister site. –  Marcin Mar 4 '11 at 20:28

3 Answers 3

up vote 13 down vote accepted

These recommendations are off of the top of my head and not intended to be comprehensive.

Check out Bastille, it's a series of scripts that implements best practices in Linux.

Don't send authentication data over plaintext protocols. For example, disable FTP. If you send authentication data via Apache, use SSL.

Disable and remove any unnecessary software including the GUI interface.

Audit any files with the SUID bit set and remove. (This will severely limit non-root abilities. Understand the implications for each individual change.)

Audit public writable directories and remove the writable bit. (Leave /tmp alone.)

Avoid running any daemon as root.

Research all multi-user software that listens on sockets in detail for security best practices.

Avoiding adding users to the system is one of the best approaches. Multi-user systems require greater attention to detail.

Enforce password standards. For example: minimum 10 characters, non-alphanumeric characters, using letters and numbers. This is to make brute forcing more difficult in case of password file compromise. Enforce this via the system.

Lock out users after 5 failed authentication attempts with a minimum of 10 minute lockout. Maintain a password history so users can't use the past 5 passwords.

If you have a larger environment, using network segregation with multiple subnets to isolate risk is an absolute requirement. If a smaller environment, running a firewall on the local system to limit exposure is recommended. For example, only allowing SSH to your IP. tcpwrappers can be used too for an extra layer. (/etc/hosts.allow, /etc/hosts.deny)

And, of course, keeping all software up to date. Especially public facing daemons.

With SSH:

  • Disable SSH protocol 1
  • Only allow root authentication without-password (only keypair)

With Apache:

  • Disable any modules that are not needed
  • Disable .htaccess and public directories
  • Disable FollowSymlink and any unnecessary options
  • Do not install PHP if you don't need it.

With MySQL:

  • Disable default users.
  • Don't use wildcard hosts.
  • Be sure to set unique host for every user.
  • Don't listen on tcp unless necessary. (Unusually unavoidable.)
  • Limit application user privileges as much as possible. (SELECT,INSERT,UPDATE,DELETE ideal for write and SELECT for read)

I'd recommend researching php.ini tuning for security specifically. It's riskier software by default.

Bastille

share|improve this answer
    
I will suggest to read cyberciti.biz/tips/php-security-best-practices-tutorial.html for php tunning –  ALex_hha Jul 24 '13 at 12:47

Here is a good article that you can use as a base for your setup and change accordingly to your ditribution: http://it.toolbox.com/blogs/rayheffer/how-to-build-a-secure-lamp-web-server-with-centos-5-36786

share|improve this answer
    
But basically, do not load modules you don't explicitly need, hide all version numbers and debug/informations pages, create a mysql user for each application with hardened passwords, always have people work on your server using regular user account and make them sudo if they need root permissions, use a firewall like iptables and only open ports based on what you absolutely need to come inside your box... That plus latest patches will already give you quite a secure setup. –  Alexandre Nizoux Mar 8 '10 at 15:02
    
This article is not good. Disabling selinux, nothing about hardening mysql, disabling unnecessary apache modules... –  sumar Mar 8 '10 at 16:03

The Defense Information Security Agency has a set of security checklists that are good places to start. Even better is to understand the rationale for each entry, but that's not a quick answer. I would recommend you look at the Enclave, Network, Unix, and Web Server STIGs.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.