oracle-livelabs · carmenberdant1 · Nov 14, 2025 · Jan 27, 2025 · Feb 4, 2025 · Feb 10, 2025
diff --git a/.DS_Store b/.DS_Store
diff --git a/zpr/compare/images/db-connection-policy.png b/zpr/compare/images/db-connection-policy.png
diff --git a/zpr/compare/images/ingress-rules.png b/zpr/compare/images/ingress-rules.png
diff --git a/zpr/compare/images/zpr-create-namespace.png b/zpr/compare/images/zpr-create-namespace.png
diff --git a/zpr/compare/images/zpr-instance-policy.png b/zpr/compare/images/zpr-instance-policy.png
diff --git a/zpr/compare/images/zpr-protected.png b/zpr/compare/images/zpr-protected.png
diff --git a/zpr/namespace/images/sec-attrs.png b/zpr/namespace/images/sec-attrs.png
diff --git a/zpr/namespace/images/zpr-attribute-namespace.png b/zpr/namespace/images/zpr-attribute-namespace.png
diff --git a/zpr/namespace/images/zpr-attributes-list.png b/zpr/namespace/images/zpr-attributes-list.png
diff --git a/zpr/namespace/images/zpr-create-attribute.png b/zpr/namespace/images/zpr-create-attribute.png
diff --git a/zpr/namespace/images/zpr-create-namespace.png b/zpr/namespace/images/zpr-create-namespace.png
diff --git a/zpr/namespace/images/zpr-namespace-attr.png b/zpr/namespace/images/zpr-namespace-attr.png
diff --git a/zpr/namespace/images/zpr-namespace.png b/zpr/namespace/images/zpr-namespace.png
diff --git a/zpr/namespace/images/zpr-vcn-attribute.png b/zpr/namespace/images/zpr-vcn-attribute.png
diff --git a/zpr/vm-access/images/protect-vm.png b/zpr/vm-access/images/protect-vm.png
diff --git a/zpr/vm-access/images/zpr-egress.png b/zpr/vm-access/images/zpr-egress.png
diff --git a/zpr/vm-access/images/zpr-ingress.png b/zpr/vm-access/images/zpr-ingress.png
diff --git a/zpr/vm-access/images/zpr-instance-policy.png b/zpr/vm-access/images/zpr-instance-policy.png
diff --git a/zpr/vm-access/images/zpr-policy-i1-to-i2.png b/zpr/vm-access/images/zpr-policy-i1-to-i2.png
diff --git a/zpr/vm-access/images/zpr-protect-instance-two.png b/zpr/vm-access/images/zpr-protect-instance-two.png
diff --git a/zpr/vm-access/images/zpr-protect-resource.png b/zpr/vm-access/images/zpr-protect-resource.png
diff --git a/zpr/vm-access/images/zpr-protected.png b/zpr/vm-access/images/zpr-protected.png
diff --git a/zpr/vm-access/vm-access.md b/zpr/vm-access/vm-access.md
@@ -86,8 +86,6 @@ Now we will apply an attribute to your instance two. This will protect your inst
 
   ![Select the resource to protect](images/protect-vm.png)
 
-  ![ZPR protect instance by adding a security attribute](images/zpr-protect-instance-two.png)
-
 
 ## Task 3: Try to ssh into instance 2
 
@@ -119,9 +117,9 @@ Try to ssh from your laptop and also try from your first compute instance. Your
 
 **Note** You would never use 0.0.0.0/0 in production but you would normally use something to limit it to your specific laptop's IP address or something very close to it like 192.1.223.0/12 So try to limit the ingress to a much smaller foot print then all possible IP addresses as done in this screen shot. You should also limit the traffic to port 22 for ssh only to limit someone from trying to attack your server using other tools/ports.
 
-  ![Allow traffic into network](images/ingress-rules.png)
+  ![Allow traffic into network](images/zpr-ingress.png)
 
-  ![Allow traffic out from your network](images/egress-rules.png)
+  ![Allow traffic out from your network](images/zpr-egress.png)
 
 -- Add a security attribute to the instance one
   ![ZPR protect a resource](images/zpr-protect-resource.png)