Directory › Connections › Telnet

Purpose

Create a Telnet connection to access legacy network/host services through the portal.

> Note: The beginning of the flow is the same as SSH/RDP/Kubernetes (Connections → Add → Name → Protocol).

> The main differences are in telnet: Protocol Parameters and Telnet-specific authentication matching fields.

Prerequisites

• Permission to create connections in the Connections module.
• Target Telnet host/IP.
• Telnet port (default 23, if not customized).
• Valid login credentials (if the target requires authentication).
• (Optional) Proxy/jump host if required by your network design.

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: TELNET - Legacy Switch 01).
• Protocol: select Telnet.

Why?

• Name improves discoverability and operational consistency.
• Protocol switches the form/engine to Telnet-specific behavior.

3) Configure Proxy

In the Proxy section:

• Hostname
• Port

Why?

• Telnet targets are often in segmented/legacy networks.
• Proxy/jump routing avoids broad direct exposure.

4) (Optional) Apply Additional Connection Restrictions

As shown in the UI:

• Date and time after which this connection may be used
• Date and time before which this connection may be used
• Times connection is allowed to be used (Add Entry)
• Times connection may not be used (Add Entry)
• Hosts from which connection may be accessed (Add Entry)
• Hosts from which connection may not be accessed (Add Entry)

Why?

• Restricts usage windows and source origins.
• Reduces attack surface and supports compliance.

5) Configure telnet: Protocol Parameters

In Network:

• Hostname: target device/server IP or DNS.
• Port: Telnet service port (usually 23).

Why?

• Defines exactly where the Telnet session will connect.

6) Configure Telnet Authentication

In Authentication:

• Username
• Password
• Username regular expression
• Password regular expression
• Login success regular expression
• Login failure regular expression

Why?

• Username/Password provide credentials when login is required.
• Username/Password regex help CyberVision detect interactive prompts from different Telnet implementations (legacy devices often vary).
• Login success regex confirms successful authentication based on terminal output.
• Login failure regex detects failed authentication and avoids ambiguous session states.

7) (Optional) Enable Recordings

In Recordings:

• Enable screen recording
• Enable text recording

Why?

• Session evidence for troubleshooting, audit, and forensic review.
• Text recording is especially useful for command-based Telnet sessions.

8) Save

• Click Save to create the connection.
• Click Cancel to discard changes.

Post-creation validation

1. Confirm the connection appears in Connections.

2. Open it and validate:

• successful TCP/Telnet reachability,
• correct prompt matching (username/password),
• expected success/failure regex behavior,
• recording behavior if enabled.

Best practices

• Use naming standard: TELNET - <Area> - <Device>.
• Prefer SSH over Telnet whenever possible (Telnet is plaintext by design).
• Keep strict source/time restrictions for Telnet connections.
• Use regex carefully and test against real device prompts.
• Periodically review and retire unused legacy Telnet entries.