diff --git a/OWASP-ZAP-Integration.md b/OWASP-ZAP-Integration.md
new file mode 100644
index 0000000..0fe3aae
--- /dev/null
+++ b/OWASP-ZAP-Integration.md
@@ -0,0 +1,16 @@
+In order to setup OWASP ZAP integration, you will need to have ZAP running on the same host as Sn1per and the http/https proxy listening on port 8081/tcp.
+
+![](https://i0.wp.com/xerosecurity.com/wordpress/wp-content/uploads/2020/06/Sn1per-ZAP2.png?w=740&ssl=1)
+
+In addition, you will need to enable the ZAP API service and disable the API key.
+
+![](https://i2.wp.com/xerosecurity.com/wordpress/wp-content/uploads/2020/06/Sn1per-ZAP1-1.png?w=746&ssl=1)
+
+The last step is to update your /root/.sniper.conf file and enable the following setting:
+```
+ZAP_SCAN="1"
+```
+
+After, you can run the ‘webscan’ mode (ie. ```sniper -t 127.0.0.1 -m webscan -w 127.0.0.1```). After the scan completes, all HTML reports will be saved to /usr/share/sniper/loot/workspace/<workspace>/web/zap-report-$TARGET-$DATE.html.
+
+> ![](https://i1.wp.com/xerosecurity.com/wordpress/wp-content/uploads/2020/06/Sn1per-ZAP4.png?w=1133&ssl=1)
\ No newline at end of file