pam_pwnd VS ansible-collection-hardening

> If the user has a super secure password shared with a different, compromised service, libcrack will not detect that.

There's a module[0] for that (TM).

> Expiry results in passwords like: (prefix)Dec2020, (prefix)5

libcrack can enforce similarity and rotation checks too [1].

> or cycling the last 2/3 entries.

There's also another module[2] just for that.

[0]: https://github.com/skx/pam_pwnd

An ansible collection for hardening Linux systems I mostly wrote: https://github.com/dev-sec/ansible-collection-hardening

Another ansible collection to manage Icinga: https://github.com/T-Systems-MMS/ansible-collection-icinga-d...

And the yunohost app for invoice ninja: https://github.com/YunoHost-Apps/invoiceninja5_ynh

i have some packer builds where itll install ansible, run playbooks locally, then uninstall ansible. such as the the devsec os hardening role: https://github.com/dev-sec/ansible-collection-hardening

This collection is also interesting https://github.com/dev-sec/ansible-collection-hardening/

Second you want to ensure the os is secure and up to date. Take a look at os hardening best practices, for example this ansible playbook for linux: https://github.com/dev-sec/ansible-collection-hardening

To ensure SSH and other security related things are configured correctly, you can take a look at DevSec which helps you to apply proven security configuration principles. Also there is guides like "Secure Secure Shell" which can help you to better understand what you can do to increase the security of your servers (this one is from 2015 but many aspects are still relevant).

I learned a lot by using and reading through the source code of these ansible roles: https://github.com/dev-sec/ansible-collection-hardening

Have a look at https://github.com/dev-sec/ansible-collection-hardening

You can do much more https://github.com/dev-sec/ansible-collection-hardening/tree/master/roles/ssh_hardening