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

SSH

Chapter 5 Authentication

The Secure Shell protocol used by Tectia Server for IBM z/OS provides mutual authentication – the client authenticates the server and the server authenticates the client user. Both parties are assured of the identity of the other party.

The Secure Shell server host can authenticate itself using either traditional public-key authentication or certificate authentication.

Different methods can be used to authenticate Secure Shell client users. These authentication methods can be combined or used separately, depending on the level of functionality and security you want.

Secure Shell user authentication methods. Note that all of the methods are not available on z/OS.

Figure 5.1. Secure Shell user authentication methods. Note that all of the methods are not available on z/OS.

Tectia Server for IBM z/OS allows public-key and password authentication by default. It also supports keyboard-interactive and host-based authentication.


 

 
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