diff --git a/content/cloud/network/images/network_secutity_groups_egress.png b/content/cloud/network/images/network_secutity_groups_egress.png
new file mode 100644
index 0000000000000000000000000000000000000000..4a5a28726dd51b03b8c644b3ed11e51845a20f9e
Binary files /dev/null and b/content/cloud/network/images/network_secutity_groups_egress.png differ
diff --git a/content/cloud/network/index.md b/content/cloud/network/index.md
index 2b39cace9a403a14b5e624626caf55bf1e5f8aa1..97d62866e11739b726ca3d00ddf8186b50d64029 100644
--- a/content/cloud/network/index.md
+++ b/content/cloud/network/index.md
@@ -210,3 +210,9 @@ The new floating IP address for the router must be from the same network pool wh
 
 2. Now click on the **Associate** button next to the Floating IP you just created. Select **Port to be associated** with the desired instance. Confirm with the **Associate** button. Repeat this section for all your machines requiring a Floating IP.
 ![](images/associate-fip.png)
+
+
+## Default Egress rules
+If you delete default egress rules, your virtual machine loses will not be able to send outgoing communication. To fix this, add a new egress rule with *any* IP protocol and port range, set Remote IP prefix to *0.0.0.0/0* (IPv4) or *::/0* (IPv6).
+
+![](images/network_secutity_groups_egress.png)
\ No newline at end of file