ansible-collection-hardening VS goss

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

Certain checks may be possible with goss and the kgoss wrapper: https://github.com/goss-org/goss/tree/master/extras/kgoss

Docker would work. I suggest also integrating infrastructure tests to validate your install script behaved as expected. For example, you could use goss.

I've used https://github.com/goss-org/goss in the past and enjoyed it

To answer my own question... https://github.com/goss-org/goss looks like it might do the job - at least for Linux. Windows support is alpha - and there isn't a wealth of CIS benchmarks. Might be a good project to contribute to

Adding an extra layer of security on the container image to verify if it is working as expected and has all required files with correct permissions. We can use dgoss to do validation tests of container images.

Bit of a strange one here - Goss. This is a testing tool that we use on all of our servers to validate they are working as expected. Think of it as a sanity check after changes. We have a set of tests setup that validate that the server is working as expected and we run it automatically after any change.

check out https://github.com/aelsabbahy/goss

Use GOSS, a YML-based open-source tool that can assert the test results (i.e., verifying if the SSH port 22 is closed or not).