diff --git a/.gitbook/assets/image (410).png b/.gitbook/assets/image (410).png
new file mode 100644
index 000000000..ccf2d624c
Binary files /dev/null and b/.gitbook/assets/image (410).png differ
diff --git a/.gitbook/assets/image (411).png b/.gitbook/assets/image (411).png
new file mode 100644
index 000000000..670189d25
Binary files /dev/null and b/.gitbook/assets/image (411).png differ
diff --git a/pentesting/2375-pentesting-docker.md b/pentesting/2375-pentesting-docker.md
index 08f079c03..4c59fbe08 100644
--- a/pentesting/2375-pentesting-docker.md
+++ b/pentesting/2375-pentesting-docker.md
@@ -219,3 +219,17 @@ cat /mnt/etc/shadow
 
 If you are inside a host that is using docker, you may [**read this information to try to elevate privileges**](../linux-unix/privilege-escalation/#writable-docker-socket).
 
+## Securing your Dockerfiles
+
+* You can use the tool [https://github.com/buddy-works/dockerfile-linter](https://github.com/buddy-works/dockerfile-linter) to **inspect your Dockerfile** and find all types of misconfigurations. Each misconfiguration will be given an ID, you can find here [https://github.com/buddy-works/dockerfile-linter/blob/master/Rules.md](https://github.com/buddy-works/dockerfile-linter/blob/master/Rules.md) how to fix each of them.
+  * `dockerfilelinter -f Dockerfile`
+
+![](../.gitbook/assets/image%20%28410%29.png)
+
+* You can use the tool [https://github.com/replicatedhq/dockerfilelint](https://github.com/replicatedhq/dockerfilelint) to **inspect your Dockerfile** and find all types of misconfigurations.
+  * `dockerfilelint Dockerfile`
+
+![](../.gitbook/assets/image%20%28411%29.png)
+
+
+