Agentless Remote Access

SecOps Solution supports remote access to devices that do not have the SecOps agent installed. This is done through a Jump Host, a machine on the same network as the target device that does have the SecOps Jump Host package installed. The Jump Host acts as a bridge, enabling the SecOps platform to reach devices it cannot contact directly.

How It Works

No software is installed on the target device. Instead, a Jump Host agent on the same network connects outbound to the SecOps platform and tunnels the session to the target using the credentials configured for that device.

SecOps Platform → Jump Host Agent → Target Device


Requirements

Jump Host

• A machine on the same network as the target device
• The SecOps Jump Host agent installed and running on the Jump Host machine
• The Jump Host must be online when a remote access session is initiated
• Outbound internet access from the Jump Host (see firewall requirements below)

Target Device (Windows)

• RDP must be enabled:
  • Open System Properties → Remote tab → select Allow remote connections to this computer
  • Windows Firewall should automatically allow RDP when it is enabled; if not, add an exception for port 3389
• A Windows user account with a username and password (local or domain account)
• The target must be reachable from the Jump Host on port 3389

Target Device (Linux)

• SSH must be enabled and accessible from the Jump Host on port 22
• A valid OS username and password for the target device

Firewall and Network Requirements

Jump Host machine (outbound)

The Jump Host needs to reach the SecOps platform

 

Jump Host machine (inbound)

The following inbound ports must be open on the Jump Host for file transfer to work.

 

Target machine (from Jump Host)

The Jump Host must be able to reach the target device

Troubleshooting

Remote access unavailable for a private asset :

The Jump Host agent must be online and associated with the asset in the SecOps platform. Verify the Jump Host device is reachable and the agent service is running.

Session fails to connect to the target : 

Confirm that RDP (port 3389) or SSH (port 22) is enabled on the target device and that the Jump Host can reach the target on that port. Test connectivity from the Jump Host with telnet <target-ip> 3389 or telnet <target-ip> 22.

Authentication failure :

Verify the credentials configured in the SecOps platform match a valid user account on the target device. For Windows, ensure the account has permission to connect via Remote Desktop (it must be in the Remote Desktop Users or Administrators group).