After acquiring a technology product, we've all had to find, and then implement the guidance in the product's hardening guide (or a third party's guide in some cases). You know, to change the unsafe defaults to safer ones.

What's your favorite example of a hardening guide (for an SMB or enterprise product) that clearly shows how dangerous the product was as it left the factory.

Links to the guide and some commentary would be most welcome! (Or you can DM me, if I can figure out how those work here)

Please boot for reach. 🔐​🙏​

@boblord an attempt from the community a while ago was bettercrypto.org to make secure configurations for common tools easier discoverable to sysadmins.