The Remote Access feature allows you to access your devices' administration interfaces directly from Zebrix Control, even when you are not connected to the same network as the devices.

Thanks to the Zebrix Probe deployed on the local network where your devices are located, Zebrix Control acts as a secure relay between your browser and the target device.

This allows you to:

• Access your devices from anywhere in the world
• Manage devices located on remote networks
• Avoid the need for complex VPN infrastructures
• Avoid maintaining dedicated administration workstations
• Reduce on-site interventions
• Centralize all access through a single interface

Depending on the capabilities of the device, Zebrix Control supports access via:

• HTTP
• HTTPS
• SSH

Access is performed directly from the device page within Zebrix Control.

Remote Access relies on the Zebrix Probe installed on the local network where the devices are located.

When a user requests HTTP, HTTPS, or SSH access:

• The browser communicates with Zebrix Control
• The Probe establishes a connection to the Zebrix Cloud
• The Probe establishes a connection to the target device
• Traffic is then securely relayed between both endpoints

This architecture makes it possible to access devices located on private networks without exposing them directly to the Internet.

Several conditions must be met before Remote Access can be used.

The Zebrix Probe must be able to communicate with the Zebrix Control platform.

The following outbound connection must be allowed:

• TCP 40000 to the Zebrix Control cloud

In the Administration → Organization menu, enable the Remote Access option.

Users must have the Remote Access permission assigned to their role.

Without this permission, HTTP, HTTPS, and SSH actions will not be visible in the interface.

The available protocols depend on the services exposed by the device.

Examples:

• Cisco Room Series: HTTP, HTTPS, and SSH
• Biamp Devio: HTTPS
• Barco ClickShare: HTTPS

If a service is not available on the device, the corresponding action will not appear in Zebrix Control.

From the device page:

1. Click Actions
2. Select the desired protocol:
   • HTTP
   • HTTPS
   • SSH

The available actions are automatically adapted to the capabilities of the device.

When you select HTTP or HTTPS, Zebrix Control automatically opens a new browser tab.

You are then redirected directly to the device's web administration interface.

Authentication remains managed by the device itself.

When using HTTP, only the communication between the Probe and the device is performed over HTTP. All other communications in the chain remain secured and encrypted.

When you select SSH, a terminal window opens directly within Zebrix Control.

You can then establish an SSH session with the device and execute any commands authorized by the device.

Authentication remains managed by the device itself.

The Remote Access service relies on the Zebrix Control infrastructure hosted in France.

Connections transit through an environment certified:

• SecNumCloud
• HDS (Health Data Hosting Certification)

This architecture provides a high level of security, traceability, and compliance for remote administration operations.

Remote Access remains subject to:

• Explicit activation of the feature at the organization level
• User permissions assigned through roles
• Services actually available on the target devices

Devices are never exposed directly to the Internet, and no VPN infrastructure is required to administer them remotely.

Zebrix Control is not a VPN solution.

The platform enables the monitoring, administration, and control of devices integrated into the Zebrix Control ecosystem, but it does not provide remote network access to customer infrastructures or unsupported devices.

Only devices that have been certified or validated by Zebrix Control are compatible with the platform and can be managed through it. Support for a device is subject to its prior integration and validation by the Zebrix teams.

For any requirement involving remote access to a corporate network, servers, or non-certified devices, the use of a VPN solution or another dedicated secure remote access mechanism remains necessary.

Key points:

• Zebrix Control does not replace a VPN.
• Zebrix Control does not provide network access to customer infrastructures.
• Only certified and officially supported devices can be managed through the platform.
• Non-certified devices cannot be accessed or managed by Zebrix Control.