<img src="https://ws.zoominfo.com/pixel/6169bf9791429100154fc0a2" width="1" height="1" style="display: none;">

Supercharge Your SSH and Kubernetes Resources with Remote Identities

StrongDM manages and audits access to infrastructure.
  • Role-based, attribute-based, & just-in-time access to infrastructure
  • Connect any person or service to any infrastructure, anywhere
  • Logging like you've never seen

StrongDM, the People-First Access platform that gives technical staff direct access to the critical infrastructure they need to be their most productive, now gives you more authentication flexibility with Remote Identities. This new feature enables you to connect to StrongDM resources using the identities of individual users instead of a leased credential.

Remote Identities helps you leverage the native capabilities of your SSH and Kubernetes resources and capitalize on infrastructure workflow investments you’ve already made.

Here’s how.

SSH and Kubernetes Remote Identities in the StrongDM Admin UI

What Is the Remote Identities Feature All About?

With Remote Identities, you authenticate to an SSH or Kubernetes resource using the identity of the StrongDM user connecting to it instead of StrongDM’s standard leased credential method.

In the StrongDM leased credential model, users access SSH and Kubernetes resources through a centralized set of credentials. This simplifies credential management and helps prevent credential sprawl while preserving all identity information about the StrongDM user accessing your infrastructure in our comprehensive logs.

But, what if you want to take advantage of user profiles and home directories on your servers, or have StrongDM users without auditing privileges relying on native Kubernetes logging and RBAC? Remote Identities allows you to leverage these resource-specific features and more.

Ultimately, though, we leave it up to you to choose if you want to use leased credentials or Remote Identities. Understanding the benefits of using Remote Identities can help you decide.

Remote Identity setting for SSH in the StrongDM Admin UI

What Are the Benefits of Using Remote Identities?

The Remote Identities feature allows you to extract more value from your SSH and Kubernetes resources by leveraging their native capabilities.

For instance, it’s now easier to do these tasks:

  • Assign Kubernetes permissions at the group level with native Kubernetes RBAC 
  • Include user-specific profiles on your servers
  • Identify specific users associated with processes being executed on multi-tenant systems 

Additionally, you can leverage pre-existing investments in infrastructure processes or workflows (such as native alerting, log aggregation, and SIEM integrations).

Have you already done any of the following?

  • Set up a SIEM aggregation that consumes native logs directly from your resources
  • Establish a local threat identification system that relies on user identities
  • Employ disk and compute quotas on a per-user basis

Remote Identities enables you to keep operating all of these processes within StrongDM.

When Does Using Remote Identities Make Sense?

We’ve already highlighted some of the most prominent use cases where authenticating using a remote identity, rather than a leased credential, makes sense. However, let’s recap them here along with a few others:

  • Leveraging user-specific profiles and home directories on servers
  • Enabling targeted identification and cancellation of server processes based on the user
  • Enforcing per-user, per-server quotas on resource usage in multi-tenant systems
  • Leveraging native Kubernetes RBAC
  • Being able to identify specific StrongDM users in a resource’s native logs
  • Using local threat identification systems on resources
  • Supporting custom notification, approval, and escalation workflows running on your resources that need to be aware of a user’s identity


New to StrongDM? Sign up for our free no-BS demo and discover how our People-First Access platform can work for you.


About the Author

, People-First Access platform, StrongDM, gives technical staff access to the infrastructure they need to be productive.

StrongDM logo
💙 this post?
Then get all that StrongDM goodness, right in your inbox.

You May Also Like

AWS Secrets Manager Alternatives & Competitors
Alternatives to AWS Secrets Manager
AWS Secrets Manager is a popular and highly intuitive secrets management tool that lets organizations automate secrets rotation processes and securely store, manage, and audit IT credentials. However, certain AWS Secrets Manager alternatives are available if you are looking to avoid getting tied down exclusively to AWS products or prioritize efficient user onboarding. In this product comparison guide, we evaluate AWS Secrets Manager competitors that can fill in some of its product gaps.
Azure Key Vault Alternatives & Competitors
Alternatives to Azure Key Vault
Microsoft Azure Key Vault is a cryptographic and secrets management solution for storing encryption keys, certificates, and passwords. While known for its interface simplicity and robust security, users should look to Azure Key Vault alternatives if they prioritize employee onboarding automation or need quick and easy implementation. This article evaluates Azure Key Vault competitors regarding security features, pricing, and usability to identify the best alternative options.
Google Cloud Secret Manager Alternatives & Competitors
Alternatives to Google Cloud Secret Manager
Google Cloud Secret Manager is an intuitive platform for managing API keys, user passwords, digital certificates, and other sensitive data and administering access control policies for business resources. While cost-friendly and reliable for securing Google Cloud applications, you should look to other Google Cloud Secret Manager competitors if you manage complex infrastructure and need multiple integrations.
CI/CD Security and CI/CD Pipeline Explained
CI/CD Security Explained: Securing CI/CD Pipeline with Access Automation
A continuous integration, continuous delivery pipeline—or CI/CD pipeline—is a process workflow companies use to streamline and automate software development. A CI/CD pipeline automatically builds and tests code changes to detect bugs before the new code is merged and deployed.
What Is SCIM Provisioning? How It Works, Benefits, and More
What Is SCIM Provisioning? How It Works, Benefits, and More
In this article, we will define SCIM and cover the basics of SCIM security. You’ll learn what SCIM stands for, how SCIM provisioning works, and why SCIM SSO is essential. By the end of this article, you will have a clear understanding of what SCIM means and how auto-provisioning via SCIM streamlines cloud identity management, increases employee productivity, and reduces IT costs.