Legacy systemsTelnetrloginrshSSH

Modern access control for systems you can't change.

Telnet-era applications and old Unix hosts still run critical work. Put single sign-on, MFA, access rules, recording and live oversight in front of them, without touching the system itself.

What you get

  • Every legacy protocol: Telnet, rlogin and rsh, plus SSH in legacy compatibility mode for old algorithms.

  • Sign-in handled for users: the gateway answers the login and password prompts with a vaulted account, so users never learn it. Or users can log in at the system's own prompt.

  • Old screens display correctly: 50 character encodings, from DOS code pages (CP437, CP850, CP862) to Shift_JIS, Big5 and KOI8-R, plus right-to-left display.

  • Same oversight as modern systems: recording, search, replay, sharing, monitoring and command policy.

Legacy systems

Modern access control for systems you can't change.

  • Every legacy protocol
  • Sign-in handled for users
  • Old screens display correctly
  • Same oversight as modern systems

Old screens display correctly.

Set up

  1. 01

    Add the system and pick its protocol and sign-in mode

  2. 02

    Choose its default character encoding

  3. 03

    Grant access

  4. 04

    Users connect from their list.

Telnet, rlogin and rsh are unencrypted on the wire. Keep the segment between the gateway and the system on a trusted network: users only ever reach the gateway, over HTTPS.

FAQ

Prove it on your own systems.

A proof of concept runs inside your environment, on the systems you choose, with success criteria agreed up front.

Book a POC
  1. 01Scope call
  2. 02Deploy & connect your systems
  3. 03Review the evidence together