SSH Communications Security
Price: Tectia Client, $149; Tectia Server, $2,390; Tectia Manager, $7,375
SSH Communications Security's SSH Tectia turns the venerable protocol into an enterprise-caliber product with strong central management.
Since 1995, when Tatu YlÖnen replaced Telnet and the "R" series of commands (rlogin, rsh, rcp) from the *nix world, SSH (Secure Shell) has been a workhorse for secure communications. The company he founded, SSH Communi-cations Security, has built SSH into a powerful enterprise tool, SSH Tectia.
Tectia delivers strong security and robust management, though enterprise-scale installation is somewhat problematic and the client interface could be improved.
Tectia Client presents a simple GUI for secure remote administration of a host and secure file transfer via secure FTP; a separate agent, Tectia Connector, enables transparent secure connection to pre-existing enterprise applications.
Tectia Client and Server run on a wide range of *nix and Windows platforms; Tectia Connector runs on Windows systems. We used a Windows 2003 Server running SQL and IIS for Tectia Server, with a mix of Windows 2000 SP4, Windows XP SP2 and Fedora Core 3 (Linux) clients.
Tectia's strength is its rock-solid security. Nothing--Nessus, Ethereal or a general SSH hacking tool--penetrates the encrypted stream. No tracks from client login are left on the local hard drive.
Tectia is fast and accurate. Entering commands and transferring files was seamless, and the clients were stable under a variety of stress tests. Additionally, you have decent control of multiple clients via the Tectia Manager.
Nonetheless, while installation was easy with one client and a single server, it got more difficult as we scaled to multiple clients on multiple operating systems. The deployment became tedious; the standard SSH system and File Transfer system were different installations.
Add in the client for agent-based SSH connections and installation becomes very complex. We found little help in the minimal installation information available online. And, we had to plow through a glut of inconsistent documentation that offered conflicting direction on things like which file to open, where the files are located and, simply, how to begin the installation.
This was first published in January 2006