Managing access to critical infrastructure is a challenge for many organizations. Legacy tools often struggle to keep up, creating inefficiencies, security gaps, and frustration. StrongDM offers a modern solution that simplifies access management, strengthens security, and improves workflows. In this post, we’ll explore 13 real-world examples of how StrongDM helps teams solve access challenges and achieve their goals.
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 Zero Trust PAM 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.
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.
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 Zero Trust PAM platform can work for you.
About the Author
💙 this post?
Then get all that StrongDM goodness, right in your inbox.
You May Also Like
Network Level Authentication (NLA) is a security feature of Microsoft’s Remote Desktop Protocol (RDP) that requires users to authenticate before establishing a remote session. By enforcing this pre-authentication step, NLA reduces the risk of unauthorized access, conserves server resources, and protects against attacks like credential interception and denial of service. While effective in securing RDP sessions, NLA is limited to a single protocol, lacks flexibility, and can add complexity in diverse, modern IT environments that rely on multiple systems and protocols.
Enterprises seek ways to effectively address the needs of dynamic, always-evolving cloud infrastructures, and StrongDM has developed a platform that is designed with built-in capabilities to support continuous compliance in AWS environments.
IP whitelisting is a security strategy that restricts access to a network/system to a specified list of trusted IP addresses. This approach ensures that only individuals using the approved addresses can access certain resources.
