New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need/Interest in hardening base image for Docker? #42

Open

JJediny opened this issue Jan 1, 2016 · 1 comment

JJediny commented Jan 1, 2016

Apologizes for not digging in more to see if I couldn't answer more of these myself, but asking this more to get opinions on how practical it is...

How much of the chef based hardening should or shouldn't be translated into a reusable dockerfile/docker image?

What hardening steps would still be appropriate given some of the issues containerization solves - like controlled ssh access, isolating instances/processes/runtime, etc.
How much disk space is added by the hardening process?
How many new processes are spawned as a result of hardening and/or required monitoring/logging?

jsalva commented Dec 8, 2016

+1; any insights?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment