SaaS - Agent-Based Target Machine Prerequisites Check
Dinesh
Last Update 10 days ago
For Agent-Based connectivity, this prerequisite check must be executed directly on each target endpoint.
1. Download the binary on the Target Machine
Download the correct binary depending on the OS of the target machine:
Download the correct binary depending on the OS of the target machine:
Windows (x64)
Download the EXE file:
Download the EXE file:
Linux (x86_64)
Linux (ARM64)
macOS (ARM - M1/M2/M3)
2. Run the binary
Run it as Administrator (Windows) or with sudo (Linux/macOS), the same way the agent will be installed.
Run it as Administrator (Windows) or with sudo (Linux/macOS), the same way the agent will be installed.
Windows (x64)
Linux (x86_64)
Linux (ARM64)
macOS (ARM - M1/M2/M3)
3. Follow On-Screen Menu
Once the binary starts, you will see an interactive menu. Select:
Once the binary starts, you will see an interactive menu. Select:
- Option 2 → SecOps Cloud (SaaS)
- Option 1 → Agent-Based
- Option 1 → Direct to SecOps Cloud: the checks start right away.
- Option 2 → Via Jump Host / Distribution Server: you will be prompted to enter the Jump Host / Distribution Server IP.
4. Expected Output Summary
After the Target Machine Check completes, you will see a summary similar to:
After the Target Machine Check completes, you will see a summary similar to:
5. Checks Performed
Direct connection:
Direct connection:
- SECOPS_CLOUD_API (Blocker) → HTTPS to api.app.secopsolution.com (agent registration, policies and results), directly or through the proxy (including the Windows system proxy).
- SECOPS_CLOUD_REALTIME (Blocker) → HTTPS to socket.app.secopsolution.com (real-time commands to the agent).
- ADMIN_RIGHTS (Warning) → the check runs as Administrator/root or with sudo, as needed to install the agent.
- RELAY_CERT_DOWNLOAD (Blocker) → TCP 5679 to the Jump Host / Distribution Server (certificate download during agent install).
- RELAY_HTTPS (Blocker) → TCP 5680 to the Jump Host / Distribution Server (agent registration, policies and results).
- RELAY_REALTIME (Blocker) → TCP 5684 to the Jump Host / Distribution Server (real-time commands to the agent).
- PROXY_BYPASS (Warning) → if a system proxy is configured, the Jump Host / Distribution Server IP is excluded from it.
- ADMIN_RIGHTS (Warning) → the check runs as Administrator/root or with sudo, as needed to install the agent.
Important:
- No Blockers should be present in the output. A PASS result confirms the target machine can reach SecOps Cloud or the Jump Host / Distribution Server.
- A “nothing is listening” WARNING typically indicates that the network path is reachable, but the required service is not currently running on the Jump Host / Distribution Server.
If this check is being performed before that server is set up, this behavior is expected. Otherwise, please verify that its services are running before proceeding. - If the machine uses a proxy, make sure SSL inspection is disabled for *.secopsolution.com.
- Any Blockers must be resolved before proceeding with onboarding.