UseCase10_GitHubSSH - sandersdHES/PAMEmergingTech GitHub Wiki

This use case demonstrates how to use PAM360 to securely manage and store SSH keys used for accessing GitHub. It includes generating SSH keys, configuring GitHub to use the public key, storing the private key securely in PAM360, and testing authentication.

GitHub supports SSH key-based authentication for pushing and pulling code securely without using a password or token. While this is convenient, private key security is critical. PAM360 allows you to safely manage private keys, associate metadata, and monitor their use—aligning with privileged access best practices.

• Admin access to PAM360
• A GitHub account
• A local terminal with SSH and keygen tools installed
• Git installed (to test SSH authentication)

In your terminal (Linux/macOS/WSL on Windows), run:

ssh-keygen -t rsa -b 4096 -f "$HOME\.ssh\github_pam360_key"

This will generate:

• github_pam360_key → Private key
• github_pam360_key.pub → Public key

Alternative: PAM360 can also generate the key pair for you (with passphrase) via its SSH Key Management feature. This will be showcased in the use case 6.xx

1. Open GitHub SSH Key Settings
2. Click “New SSH key”
3. Provide a name like pam360 test
4. Paste the contents of your github_pam360_key.pub file

1. Go to PAM360 > Resources > SSH Keys
2. Click “Add SSH Key”
3. Upload the private key file: github_pam360_key
4. Optionally, add metadata:
   • Usage: GitHub Access
   • Associated User/Team
   • Expiration Policy, etc.

PAM360 ensures the key is encrypted at rest and access-controlled.

Use the command line to test the private key manually:

ssh -i ~/.ssh/github_pam360_key -T [email protected]

If everything is configured properly, GitHub should respond:

Hi your-username! You've successfully authenticated...

If everything is configured properly, GitHub should respond:

With this configuration, you can now:

• Use PAM360 to securely store and track SSH keys
• Control access to critical developer tools like GitHub
• Reduce the risk of lost or compromised private keys
• Align with enterprise-grade key management practices

This setup demonstrates how PAM360 extends beyond infrastructure management and supports developer workflows as part of a Zero Trust strategy.