Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia

Chapter 8 Configuring SSH Tectia

SSH Tectia Manager provides a web-based administration interface for creating SSH Tectia Client, ConnectSecure, and Server configurations. This administration interface enables:

  • creating configurations

  • editing configurations

  • storing multiple configurations

  • audit log of the changes made

  • online help for the configuration parameters

  • create/edit → assign → deploy task flow

SSH Tectia Manager generates configuration files dynamically for different SSH Tectia software versions based on the configurations the administrator has specified using the SSH Tectia Manager administration interface.

The SSH Tectia configurations are managed separately for SSH Tectia G3 versions (5.x and 6.x) and SSH Tectia version 4.x to enable full use of the improved G3 configuration format, which provides flexible and more fine-grained configuration setups. Note, however, that the administration interface of SSH Tectia Manager does not support every possible configuration option. Advanced G3 configurations can be entered directly in XML. See Advanced XML Configuration.

During standard operation the task flow typically has three steps:

  1. Create/edit the configurations (Configurations → Edit Configurations).

    • Create the configuration and files to be distributed based on the environment, configuration requirements, and company security policy.

  2. Assign the configurations to the hosts and host groups (Configurations → Assign configurations).

    • Define the configuration to be used per host group or per host.

    • If no configuration is defined, the configuration of the parent group will be used.

    After the definitions for all host groups have been created, only edit and deploy actions (steps 1 and 3) are needed. By default the settings are inherited from a parent group, so creating a default setting and assigning it to the root of the view is recommended.

    SSH Tectia Connector tunneling configurations are defined per host or host group and do not need to be separately assigned, as they are assigned according to the tunneling rule set defined in Configurations → Connector configurations.

  3. Deploy the configurations to the hosts (Configurations → Deploy configurations).

    • Distribution will be started after the administrator launches the deployment.

    • Configuration updates will be queued and executed in parallel to a predefined number of hosts.

    • Old pending configuration updates will be overridden if a new update is launched before all the old ones have been successfully completed.

It is good practise to set up a group of test machines, where each new configuration is tested before applying it into production. In case strict configuration verification policy is in use, the person making the actual deployment should not be the same person who created or changed the configuration (checking/verification of the new settings made).


Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more