Enterprise Networking Requirements
Available in sensor version 1.2.4+
All Linux EDR instances have Enterprise Networking enabled by default, which can be used to connect to a specific subset of addresses. This allows you to connect to a single Red Canary domain, https://cwp-ingest.redcanary.io, for delivery of all telemetry and health and error reporting. This is available in any paid Linux EDR account.
Add the following keys to /opt/redcanary/config.json. Both are required for enabling enterprise networking. These values are available in Red Canary under Endpoints > Deploy Sensors.
Migrating from Standard to Enterprise Networking
If you are already use Red Canary Linux EDR without Enterprise Networking, you can migrate to it by adding the outpost_auth_token and offload_target to your config.json file, and restarting the service. You must be on sensor version 1.2.4 or above to use Enterprise Networking.
Once the new configuration is saved, restart the service for enterprise networking to take effect.
systemctl restart cfsvcd
Please allow-list https://cwp-ingest.redcanary.io.
If there are any issues, check the sensor log file for errors relating to
Outpost and reach out for support if needed. You can contact us in your dedicated Slack channel or at firstname.lastname@example.org.
Standard Networking Requirements
Red Canary also supports standard networking if you choose not to use enterprise networking for any reason or have a sensor version older than 1.2.4. Your firewall needs to be set to allow the following:
- s3-us-east-2.amazonaws.com (tcp/443)
- 220.127.116.11 (tcp/443) (sentry.io)
- 18.104.22.168 (tcp/443) (o1.ingest.sentry.io)
You will also need to remove the offload_target and outpost_auth_token from your config.json file:
Proxy SupportTo utilize a SOCKS proxy...
- Set the
- Or, add the following to config.json:
Note: This feature is available in v0.4.8+
The agent supports the use of an HTTP Connect proxy. This can be configured through the config.json file.
The agent utilizes the following precedence order when determining what proxy settings to utilize, if any at all.
- config.json's http_proxy field
- config.json's env_http_proxy_disabled field
- HTTPS_PROXY & HTTP_PROXY environment variables
Define proxy settings via config.json:
This overrides any proxy settings configured via the HTTPS_PROXY or HTTP_PROXY environment variables on the endpoint. Ensure `config.json` is valid JSON. (The comma at the end may not be needed).
To opt out of the use of proxy settings already defined via endpoint environment variables HTTPS_PROXY and/or HTTP_PROXY
The default value for this is false. When configured as false, this means the agent will utilize the HTTPS_PROXY or HTTP_PROXY environment variable for proxy settings, if set. Ensure `config.json` is valid JSON. (The comma at the end may not be needed).