System Requirements | Guardz Help Center

General Agent requirements

CPU micro-architectures such as x86_32, RISC, and MIPS are not supported by SentinelOne components.
If you use PAN-OS 8.1 (Palo Alto Networks), you must manually add SentinelOne as an approved application.
Self-hosted (on-premises) Management Consoles on version Grand Canyon and later do not support Legacy Windows Agents.

Every Agent must have working DNS and be able to connect to the Management Console.
Agents that reach the Management Console through a proxy server or firewall gateway must have an average network bandwidth of at least 5 Mb.
For Windows Agents: if there is a web proxy between the endpoints and the Console, Guardz recommends configuring the proxy for the Windows Agent in the installation command. If the proxy was not configured, the Agent is already installed, and there is no connection between the Agent and the Platform, see How to Fix Never Connected Agents.
Cloud-based Platform: if the Agent is configured to go through an internal proxy server, the endpoint must reach the proxy through a VPN.
Self-hosted (on-premises) Platform:
- If the endpoint is removed from the organization network, it must connect to the Platform through a VPN.
- If the endpoint is on the same network as the Platform, a VPN connection is not required.

Starting with version X SP4 for cloud consoles (Y SP2 for self-hosted consoles), all new Management Console configurations use TLS version 1.2 or 1.3. The Management Console will not connect with or upgrade Agents that use TLS versions earlier than 1.2 — patch or update the OS of those endpoints to a version that supports TLS 1.2 or 1.3.
Existing Consoles might not be affected by this change immediately, but the rollout is being enrolled progressively. Endpoints that only support TLS 1.0 or 1.1 must be updated to TLS 1.2 or 1.3. Third-party tools are available to help identify operating systems that require updates.

Note: This change does not affect endpoints running the Windows Legacy Agent.