Merge branch 'main' into docs/add-docker-troubleshooting

Author: RomuDeuxfois

docs/deployment/ecosystem/executors.md

@@ -29,7 +29,7 @@ payloads on endpoints.
 ## Tanium Agent
 
 The Tanium agent can be leveraged to execute implants as detached processes that will then execute payloads, according
-to the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/overview).
+to the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/platform/overview/).
 
 The implants will be downloaded to these folders on the different assets:
 
@@ -127,7 +127,7 @@ Endpoints from the selected computer groups should now appear in the **OpenAEV E
 ## CrowdStrike Falcon Agent
 
 The CrowdStrike Falcon agent can be leveraged to execute implants as detached processes that will then execute payloads
-according to the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/overview).
+according to the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/platform/overview/).
 
 The implants will be downloaded to these folders on the different assets:
 
@@ -297,7 +297,7 @@ Endpoint on the OpenAEV endpoint page.
 ## Palo Alto Cortex Agent
 
 The Palo Alto Cortex agent can be leveraged to execute implants as detached processes that will then execute payloads
-according to the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/overview).
+according to the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/platform/overview/).
 
 On Windows, because Palo Alto Cortex whitelists its own process tree, OpenAEV creates a scheduled task to detach the process that will execute the payloads. 
 
@@ -390,7 +390,7 @@ Endpoint on the OpenAEV endpoint page.
 ## SentinelOne Agent
 
 The SentinelOne agent can be leveraged to execute implants as detached processes that will then execute payloads
-according to the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/overview).
+according to the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/platform/overview/).
 
 The implants will be downloaded to these folders on the different assets:
 
@@ -490,7 +490,7 @@ Endpoint on the OpenAEV endpoint page.
 ## Caldera Agent
 
 The Caldera agent can be leveraged to execute implants as detached processes that will then execute payloads according to
-the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/overview/#architecture).
+the [OpenAEV architecture](https://docs.openaev.io/latest/deployment/platform/overview/).
 
 !!! note "Caldera already installed"
 

docs/usage/openaev-agent.md

@@ -224,6 +224,20 @@ The installation creates two firewall rules:
 
 ---
 
+## Proxy Configuration
+
+To use a proxy with the OpenAEV Agent, define both `HTTP_PROXY` and `HTTPS_PROXY` **before running the installer**.
+
+You can configure them in either of the following ways:
+- **Machine-wide (persistent):** set them as system environment variables so they are available globally.
+- **Session-only (temporary):** set/export them in the same terminal session immediately before executing the installation script.
+
+If the agent is installed as a service, make sure these variables are also available to the service account.
+
+Verify that your proxy is correctly configured and communicate well with your OpenAEV Agent installed.
+
+---
+
 ## Features
 
 The main features of the OpenAEV Agent include: