Manually managing SSH keys is a time intensive task for security teams and an inconvenience for engineers. EZSSH simplifies the identity lifecycle by introducing automation and centralized controls to an otherwise decentralized toolset.
EZSSH uses your secure corporate identity to authenticate users. Reducing onboarding time and improving user experience by removing the user’s responsibility of creating and managing SSH keys.
EZSSH can be easily deployed by adding your access policy’s own Certificate Authority key to the allowed SSH CAs (Each policy has a downloadable script that you can run in all your endpoints).
While using a short-term certificate sounds like a lot of work for a user each time they want to login. The user is not aware of all of this going on in the background. The user simply types the command, and we do all the magic in the backend, the only thing the user knows is they got a secure way to connect to their infrastructure.
With the increase in cyber-attack sophistication, such as the recent Solar Winds attack, the security community was reminded of the risks and challenges associated with using 3rd party tooling and infrastructure. EZSSH was built for a Zero Trust model, which means using native Linux libraries for authentication and no custom code/agents running your servers.
With the expanded cloud workloads, digital transformation and shifts to remote work, you can no longer depend on an isolated network to protect your endpoints from attackers. EZSSH protects your SSH endpoints by using the latest cryptographic technologies by issuing short term certificates to securely access critical endpoints, limiting the damage from a compromised key, and preventing brute force attacks.
Save hours of engineering productivity by no longer having engineers manually add and remove SSH keys to endpoints. EZSSH uses your secure developer identity to authenticate engineers and issue a short-lived certificate. Reducing onboarding time, while also protecting the user key from being stolen due to mismanagement of the private key.
