Chapter 11. SSH-specific settings

The following sections describe configuration settings available only for the SSH protocol. Use the following policies to control who, when, and how can access the SSH connection.

  • Hostkeys and host certificates: PSM allows you to set how the identity of the client hosts and servers is verified. For details, see Procedure 11.1, Setting the SSH host keys and certificates of the connection.

  • Authentication Policy: Authentication policies describe the authentication methods allowed in a connection. Different methods can be used for the client and server-side connections. For details, see Section 11.3, Authentication Policies.

  • User List: A user list is a list of usernames permitted to use — or forbidden from using — the connection. Essentially it is a blacklist or a whitelist. All users matching the other requirements of the connection are accepted by default. For details, see Procedure 7.8, Creating and editing user lists.

  • Channel Policy: The channel policy determines which SSH channels (for example terminal session, SCP, and so on) can be used in the connection, and whether they are audited or not. The different channels may be available only under certain restrictions, as set in the channel policy. For details, see Procedure 7.5, Creating and editing channel policies.

  • SSH settings: SSH settings determine the parameters of the connection on the protocol level, including timeout value and greeting message of the connection. The following parameters determine which algorithms are used in the connections, and can be set independently for the client and the server side: key exchange, host key, cipher, MAC, and compression algorithms. The default values include all possible algorithms. For details, see Procedure 11.5, Creating and editing protocol-level SSH settings.

  • Content Policy: Content policies allow you to inspect the content of the connections for various text patterns, and perform an action if the pattern is found. For example, PSM can send an e-mail alert if a specific command is used in an SSH terminal session. For details, see Procedure 7.6.1, Creating a new content policy.

  • Ticketing Policy: Ticketing policies allow you to request a ticket ID from the user before authenticating on the target server. That way, PSM can verify that the user has a valid reason to access the server — and optionally terminate the connection if he does not. For details, see Section 18.5.5, Integrating ticketing systems.

  • Authentication and Authorization plugin:

    PSM provides a plugin framework to integrate PSM to external systems to authenticate or authorize the user before authenticating on the target server. Such plugins can also be used to request additional information from the users, for example, to perform multi-factor authentication.

    For details, see Section 18.5, Integrating external authentication and authorization systems.