diff --git a/Servers & Workflows/Linux/Automation/Puppet/Puppet Deployment.md b/Servers & Workflows/Linux/Automation/Puppet/Puppet Deployment.md
index f527f22..b511487 100644
--- a/Servers & Workflows/Linux/Automation/Puppet/Puppet Deployment.md	
+++ b/Servers & Workflows/Linux/Automation/Puppet/Puppet Deployment.md	
@@ -24,6 +24,10 @@ systemctl enable --now puppetserver
 # Validate Successful Deployment
 exec bash
 puppetserver -v
+
+# Open Necessary Firewall Port for Agent Communication
+sudo firewall-cmd --add-port=8140/tcp --permanent
+sudo firewall-cmd --reload
 ```
 
 ### Install Puppet Agent
@@ -37,4 +41,18 @@ sudo /opt/puppetlabs/bin/puppet resource service puppet ensure=running enable=tr
 
 # Configure Puppet Server to Connect To
 puppet config set server lab-puppet-01.bunny-lab.io --section main
+
+# Establish Secure Connection to Puppet Server
+puppet ssl bootstrap
+
+# ((On the Puppet Server))
+# You will see an error stating: "Couldn't fetch certificate from CA server; you might still need to sign this agent's certificate (fedora.bunny-lab.io)."
+# Run the following command (as root) on the Puppet Server to generate a certificate
+puppetserver ca sign --certname fedora.bunny-lab.io
+```
+
+#### Validate Agent Functionality
+At this point, you want to ensure that the device being managed by the agent is able to pull down configurations from the Puppet Server.  You will know if it worked by getting a message similar to `Notice: Applied catalog in X.XX seconds` after running the following command:
+``` sh
+puppet agent --test
 ```
\ No newline at end of file