Directory › Connections › SSH

Purpose

Create an SSH connection to access a Linux/Unix server through the portal.

Prerequisites

• Permission to create connections in the Connections module.
• SSH server host/IP.
• SSH port (default 22, if not customized).
• Valid credentials (username/password or equivalent credential method).
• (Optional) Proxy/jump host, if required by your environment.

Step-by-step

1) Create the connection

1. Open Connections.

2. Click Add.

2) Set general connection details

In the Connection section:

• Name: define a clear name (example: SSH - App Server 01).
• Protocol: select SSH.

Why?

• Name improves searchability, standardization, and daily operations.
• Protocol selects the technical connection engine (SSH vs RDP/Kubernetes).

3) Configure Proxy

In the Proxy section:

• Hostname: proxy/jump host.
• Port: proxy port.

Why?

• In segmented networks, SSH servers are often not directly exposed.
• A proxy enables controlled and auditable access without broad network exposure.

4) (Optional) Apply usage restrictions

In Additional Connection Restrictions:

• Allowed date/time windows.
• Allowed/blocked schedules.
• Allowed/blocked source hosts.

Why?

• Reduces attack surface.
• Enforces compliance (access only in approved windows).
• Prevents out-of-context or unauthorized use.

5) Configure SSH protocol parameters

In ssh: Protocol Parameters:

Network

• Hostname: server IP/DNS (example: 10.17.17.109).
• Port: 22 (or custom SSH port).

Authentication

• Username: remote account username.
• Password: remote account password (when applicable).

Why?

• Hostname/Port define the exact technical destination.
• Username/Password define identity for host authentication.

6) (Optional) Enable recordings

In the Recordings section:

• Enable session recording
• Enable keystroke recording

Why?

• Provides forensic auditability and command traceability.
• Helps with incident analysis, compliance, and operational reviews.

7) Save

• Click Save.

Post-creation validation

1. Confirm the connection appears in the Connections list.

2. Open the connection and validate:

• connectivity,
• authentication,
• functional shell prompt,
• recording behavior (if enabled).

Best practices

• Use a naming standard: SSH - <Team> - <Server>.
• Prefer private network + proxy instead of direct exposure.
• Apply source/time restrictions for sensitive access.
• Periodically review and remove/disable unused connections.