Add container security section

09-container-security/README.md

@@ -0,0 +1,33 @@
+# Container Security
+
+There are two main considerations when it comes to container security (1) the contents of your container image and (2) the security of the execution configuration and environment.
+
+## Image Security
+
+*“What vulnerabilities exist in your image that an attacker could exploit?”*
+
+- Keep attack surface area as small as possible:
+  - Use minimal base images (multi-stage builds are a key enabler)
+  - Don’t install things you don’t need (don’t install dev deps)
+- Scan images!
+- Use users with minimal permissions
+- Keep sensitive info out of images
+- Sign and verify images
+- Use fixed image tags, either:
+  - Pin major.minor (allows patch fixes to be integrated)
+  - Pin specific image hash
+
+## Runtime Security
+
+*If an attacker successfully compromises a container, what can they do? How difficult will it be to move laterally?*
+
+### Docker daemon (dockerd)
+  - Start with --userns-remap option(https://docs.docker.com/engine/security/userns-remap/)
+
+### Individual containers:
+- Use read only filesystem if writes are not needed
+- --cap-drop=all, then --cap-add anything you need
+- Limit cpu and memory --cpus=“0.5” --memory 1024m
+- Use --security-opt
+  - seccomp profiles (https://docs.docker.com/engine/security/seccomp/)
+  - apparmor profiles (https://docs.docker.com/engine/security/apparmor/)

10-interacting-with-docker-objects/README.md

@@ -10,6 +10,7 @@
 6) rm
 7) prune
 8) save
+9) docker scan <image> (snyk security scan, also show trivy)
 
 ## Containers
 

12-deploying-containers/docker-compose-prod.yml

@@ -1,3 +1,5 @@
+version: '3.7'
+
 services:
   client-react-nginx:
     image: sidpalas/devops-directive-docker-course-client-react-nginx:5
@@ -66,4 +68,4 @@ volumes:
 
 networks:
   frontend:
-  backend:
+  backend: