- Notifications
You must be signed in to change notification settings - Fork32
Ansible playbooks of "How To Secure A Linux Server".
License
moltenbit/How-To-Secure-A-Linux-Server-With-Ansible
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
Ansible playbooks of"How To Secure A Linux Server".
These Ansible playbooks are made to help install secure Linux servers faster.
- InstallAnsible
- git clone this repository
git clone https://github.com/moltenbit/How-To-Secure-A-Linux-Server-With-Ansiblecd How-To-Secure-A-Linux-Server-With-Ansiblessh-keygen -t ed25519- Change all variables ingroup_vars/variables.yml according to your needs.
- Enable SSH root access before running the playbooks:
nano /etc/ssh/sshd_config[...]PermitRootLogin yes[...]- Recommended: configure static IP address on your system.
- Add your systems IP address tohosts.yml.
Run the requirements playbook using the root password you specified while installing the server:
ansible-playbook --inventory hosts.yml --ask-pass requirements-playbook.yml
Run the main playbook with the new users password you specified in thevariables.yml file:
ansible-playbook --inventory hosts.yml --ask-pass main-playbook.yml
If you need to run the playbooks multiple times remember to use the SSH key and the new SSH port:
ansible-playbook --inventory hosts.yml -e ansible_ssh_port=SSH_PORT --key-file /PATH/TO/SSH/KEY main-playbook.yml
Tested on Debian 12 Bookworm.
The playbook uses most of the settings from"How To Secure A Linux Server" / my choices if the guide has more than one option to do something.
- sudo installed
- groups created forsshusers,sudousers andsuusers
- new user created with the name specified invariables.yml and added to groups
- use of sudo limited to sudousers group
- use of su limited to suusers group
- passwordless sudo enabled for the new user
- SSH public key added to authorized_keys file
Uses best practice rules fromNeo23x0
ClamAV is set to run everyday at 3 AM to scan the full system, exluding sys folders.
UFW is set to default deny in and out.The SSH-Port is set tolimit in, allowed outgoing ports by default are 53 (DNS), 123 (NTP), 80 (http), 443 (https) and the mail port specified invariables.yml.
PSAD and Fail2Ban is configured according to "How To Secure A Linux Server" guide.
Lynis is configured according to "How To Secure A Linux Server" guide and will run an audit + send the report as an attachment to your mail address configured invariables.yml.Current Lynis rating is 77.
For mailing I chose msmtp with the help fromDecatec's guide. This will send a testmail.
Installed packages are:
- apt-transport-https
- ca-certificates
- host
- kbtin
- ntp
- libpam-pwquality
- unattended-upgrades
- apt-listchanges
- apticron
- ufw
- psad
- fail2ban
- msmtp
- msmtp-mta
- mailutils
- clamav
- clamav-freshclam
- clamav-daemon
- rkhunter
- auditd
- audispd-plugins
Password quality is done via pam_pwquality according to "How To Secure A Linux Server" guide.
Rkhunter is configured according to "How To Secure A Linux Server" guide.
SSH is configured according to "How To Secure A Linux Server" guide.
Unattended upgrades is configured to only upgrade security upgrades automatically. Automatic restarts are enabled.
- use Ansible vault to securely store secrets
Read all tasks carefully and make sure they do not break your system before using these playbooks! Do not rely solely on the Ansible playbooks for security! It is your responsibility to make sure all settings you need have been set and are working. This is just a starting point! Depending on your needs and goals make sure to further secure your system.
- imthenachoman for creating the greatHow To Secure A Linux Server guide
- Neo23x0 for the auditd best practice rules
- Decatec for the easy mail configuration
About
Ansible playbooks of "How To Secure A Linux Server".
Topics
Resources
License
Uh oh!
There was an error while loading.Please reload this page.