add pull only details

Author: afzaljasani

docs/cloud/features/security/security.md

@@ -22,15 +22,17 @@ For some customers, our hybrid deployment option is a great fit. It provides a s
 
 In a hybrid deployment, Tobiko Cloud does not execute tasks directly with the engine. Instead, it passes tasks to the executors hosted in your environment, which then execute the tasks with the engine. 
 
-Executors are Docker containers that connect to both Tobiko Cloud and your SQL engine. They pull work tasks from the Tobiko Cloud scheduler and execute them with your SQL engine.
+Executors are Docker containers that connect to both Tobiko Cloud and your SQL engine. They pull work tasks from the Tobiko Cloud scheduler and execute them with your SQL engine. This is a pull-only mechanism authenicated through an OAuth Client ID/Secret. Whitelist IPs in your network to allow reaching Tobiko Cloud IPs from the executor: 34.28.17.91, 34.136.27.153,
+34.136.131.201
 
 Below is a diagram of the components along with their description. 
 
 ![tobiko_cloud_hybrid_deployment](./tcloud_hybrid_deployment.png){ width=80% height=60% style="display: block; margin: 0 auto" }
 
 
-- **Helm Chart**: For production environements, we provide a [Helm chart](./hybrid_executors_helm.md) that includes robust configurability, secret management, and scaling options.
-- **Docker Compose**: For simpler environments or testing, we offer a [Docker Compose setup](./hybrid_executors_docker_compose) to quickly deploy executors on any machine with Docker.
+- **Helm Chart**: For production environements, we provide a [Helm chart](/cloud/features/scheduler/hybrid_executors_helm.md) that includes robust configurability, secret management, and scaling options.
+- **Docker Compose**: For simpler environments or testing, we offer a [Docker Compose setup](/scheduler/hybrid_executors_docker_compose) to quickly deploy executors on any machine with Docker.
+
 
 
 ## Internal Code Practices