diff --git a/README.md b/README.md
index b0e2355..43e3ea2 100644
--- a/README.md
+++ b/README.md
@@ -101,6 +101,12 @@ You need to harden your system to protect your assets as much as possible. Why i
 
 In my opinion, you should drop all non-industry policies, articles, manuals, and others especially on production environments and standalone home servers. These lists exist to give a false sense of security and aren't based on authority standards.
 
+<p align="center">
+  <a href="https://github.com/trimstray/the-practical-linux-hardening-guide">
+    <img src="https://github.com/trimstray/the-practical-linux-hardening-guide/blob/master/static/img/meme_01.png" alt="Master">
+  </a>
+</p>
+
 There are a lot of great GNU/Linux hardening policies available to provide safer operating systems compatible with security protocols. For me, CIS and the STIGs compliances are about the best prescriptive guides - but of course you can choose a different one (e.g. PCI-DSS, DISA).
 
   > Most of all you should use [Security Benchmarks/Policies](#policy-compliance) which describe consensus best practices for the secure configuration of target systems.
diff --git a/static/img/meme_01.png b/static/img/meme_01.png
new file mode 100644
index 0000000..52ee2b4
Binary files /dev/null and b/static/img/meme_01.png differ