SSH keys

image SSH keys

Can manage one or both sides of a connection securely and cross-organizations SSH keys are often create once and float around forever, but should be properly managed (rotated periodically, removed when no longer in-use etc.). We can handle both client- and server-side of SSH/SFTP connections. For some of our customers, where we manage both the client- and server-side, we have a unique system to securely manage the secret and public keys across platform-, technology-, and organizational boundaries.

Example flows

  • Before we rotate the secret key in the client, we can make sure the corresponding user account on the server has the new public key.
  • Before we rotate the secret key on a server, we can make sure the corresponding clients have updated their well-known ID’s configurations.

Example clients

  • SSH & SFTP clients - OpenSSH and PuTTY formats
    • FileZilla
    • WinSCP
    • File system
    • PuTTY
    • Azure key vaults, Logic Apps etc.
    • SFTP adapters/connections in integration platforms like SAP, IBM, MuleSoft etc.
    • …

Example servers

  • SFTP servers
    • OpenSSH
    • Bitvise SFTP server
    • FileZilla server
    • Azure storage accounts etc.
    • …