The HIPAA Multi-Factor Authentication (MFA) requirement is a security measure that requires users to verify their identity using at least two different factors—such as something they know (a password), something they have (a smartphone or token), or something they are (a fingerprint)—to access systems containing electronic Protected Health Information (ePHI). This additional layer of security is designed to protect sensitive healthcare data from unauthorized access, even if one credential is compromised, and helps organizations comply with the HIPAA Security Rule.
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
Following on the heels of our recent announcement of 2022 being the Year of Access, StrongDM continues to ease friction and remove the barriers standing between technical staff and access to the resources they need—without sacrificing security—with our latest product release.
We’ve made it even easier to manage access to backend infrastructure in an increasingly ephemeral computing environment. Simply put, this is the most impactful, far-reaching release we’ve done to date, and early feedback from our customers has been a resounding “yassssssss.”
Take a look.
Simplify Provisioning with Deeper Identity Provider Integrations
We listened to our customers and, by far, the feature everyone was clamoring for was deeper integrations with identity providers. In fact, according to our recent survey, 53% of organizations take hours or weeks to grant access to infrastructure. Additionally, 88% of organizations require two or more persons to approve access requests.
With the release of tighter integrations with Okta and Microsoft Entra ID (formerly Azure AD) (or any SCIM-based directory service for that matter), you now have the ability to manage just-in-time, least-privilege access to your critical infrastructure right from your preferred identity provider (IdP), dramatically reducing the time needed to approve requests and grant access.
This means increased developer productivity and faster development cycles, all while supporting Zero Trust security for hybrid and multi-cloud environments. Not too shabby, eh?
More specifically, you can now:
- Automate user and group provisioning with a single source of truth.
- Synchronize Role assignments from your IdP to StrongDM.
- Choose which users and groups of users you want your IdP to manage in StrongDM.
- Manage policy exceptions via StrongDM by assigning IdP-managed users to StrongDM-managed Roles or StrongDM-managed users and service accounts to IdP-managed Roles.
Here’s a more in-depth product video that gives you a taste of what these integrations can do.
- Okta documentation
- Microsoft Entra ID (formerly Azure AD) documentation
Get More Flexibility with Dynamic Access Rules
A perfect complement to static access rules, dynamic access rules eliminate loads of manual administrative work, giving businesses more granular control when provisioning infrastructure and enabling staff to access the resources they need more quickly.
Dynamic access rules enable businesses to enforce a powerful set of rules based on attributes such as tags and resource types. With this model, also known as attribute-based access control (ABAC), access is granted dynamically to Roles and their users every time a resource gets spun up or torn down.
This is particularly useful for companies with large installed bases with lots of resources on the backend, especially ephemeral ones. Basing access rules on tags offers much more flexibility with so much ephemerality in today’s computing landscape.
If you’re interested in seeing dynamic rules in action, check out this short video and let us know what you think. Good or bad.
- Dynamic Access Rules documentation
New to StrongDM? Sign up for our free no-BS demo and discover how frustration-free Zero Trust can work for you. Or, feel free to check out the results of our survey to see how you stack up against your peers.
About the Author
💙 this post?
Then get all that StrongDM goodness, right in your inbox.
You May Also Like
I’ll spare you the “I drink your milkshake” tropes, but we all face a sobering reality: there will be breaches in 2025. Breaches aren’t a question of “if” anymore—they’re a question of “when” and “how bad.” It’s a foregone conclusion, like taxes or the 37th season of Grey’s Anatomy. But here’s the good news: knowing the inevitability of breaches gives us the perfect opportunity to prepare, if we have the will – and strategy – oh, and tools – to do it. And no, I’m not talking about the “build a bunker and buy 1,000 cans of beans” kind of preparation. I’m talking about a smarter, modern approach to managing access.
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.
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.
