EZGIT adds the short-term certificates to the computer’s SSH agent, which is the credential manager used by most git clients. Allowing your users to use their favorite git tool while being protected by EZGIT.
EZGIT 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.
EZGIT can be easily deployed! All you need is add your EZGIT Certificate Authority to your GitHub organization. If your GitHub users do not match your IDP aliases, EZGIT will automatically map them.
Save hours of engineering productivity by no longer having developers register their SSH Keys in GitHub by switching to EZGIT. EZGIT uses your secure developer identity to authenticate your developers 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.
Following SSH Keys best practices is hard and failing to do it have caused many companies to have their source code compromised. Are your engineers keeping their SSH keys safe? Are they password protected? Have their shared/emailed/committed their private key by mistake? EZSSH removes all that complexity by hiding all the key management form the user and issuing time bound certificates.
With the increase in cyber-attack sophistication, Identity providers have added security controls such as MFA, Conditional Access, and abnormal behavior detections. However, when it comes to securing repositories, we are still using 25 year-old SSH keys. EZGIT is the first SSH CA for GitHub, allowing you to use the same identity security tools to secure your code.
