Docker Bench: auditing container security, with the commands

Day 1 of working through every AWS security lab. Running Docker Bench against a live server, picking a warning, fixing it with auditd, and proving the fix.

Day 1 of 38: complete every AWS security lab.

The fixing part is what makes it worth doing. Running a scanner is easy; remediating and then proving the remediation is the skill.

Tip

The warning I picked to fix:

Always look before you change. You want to know what was there.

Reviewing the security of your containers certainly seems like it should be standard practice. But do check in with your own company's security posture and compliance requirements, so that what you are doing lines up with what you are actually required to do.

Careful

I'm posting the steps for these labs as I go, mostly for accountability. 38 to get through.

Should I start an accountability group? Genuinely asking.

Contents

Originally posted