Enforcing Multi-Factor Authentication for Legacy Applications with Idira

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Idira Success Blogs
5 min read
L4 Transporter

Introduction

Legacy applications pose challenges for organizations needing to enforce multi-factor authentication (MFA). Many lack native MFA support, yet compliance with regulations like NYDFS, HIPAA, PCI DSS, and others require it for all access points. Idira provides an identity security platform that enables organizations to integrate MFA into legacy environments, covering standard users, remote access, privileged accounts, and third-party connections.

The Challenge of Securing Legacy Applications

Legacy applications often rely solely on basic username and password authentication, which is no longer sufficient against modern threats or regulatory demands. Because these systems are critical yet outdated, upgrading them for MFA can be complex or impractical, leaving organizations with significant security challenges.

 

Idira resolves this issue by providing comprehensive MFA enforcement across all access points, leveraging Identity Security solutions including CyberArk’s Adaptive Multi-Factor Authentication, Privilege Access Management (PAM), Remote Access, Secure Infrastructure Access (SIA), and Endpoint Privilege Manager (EPM). The following sections detail how Idira addresses MFA enforcement for legacy applications, ensuring no method of access is left unprotected.

 

MFA Enforcement via RADIUS

A frequently employed method for integrating multi-factor authentication (MFA) into legacy systems is the use of RADIUS. While certain legacy platforms lack support for RADIUS, those that are compatible can utilize Idira to enforce MFA, allowing continued use of the native login application with minimal disruption to the existing authentication process.

 

MFA for Remote Access Use Cases

Idira offers multiple approaches to enforcing multi-factor authentication for remote access use cases. Many organizations rely on VPNs or VDIs to facilitate secure remote connectivity to internally hosted applications, yet some organizations are still only using username and password for VPN and VDI authentication. By integrating CyberArk's adaptive MFA with existing VPN or VDI infrastructure, organizations can mandate a second layer of verification—such as FIDO2, push notifications, one-time passcodes, or biometric —for every remote access attempt. When integrating with VPNs or VDI, be sure to use SAML instead of RADIUS. SAML offers much better security and more options than RADIUS.

 

Another Idira approach is to use the Idira Remote Access solution as a passwordless VPN alternative. The solution provides VPN-less access with passwordless biometric MFA, optionally add session recording, access to a system without seeing the password, and least privilege access to only assigned systems. This solution is ideal for third-party contractors or privileged users requiring access to a server. By using passwordless biometric MFA for remote logins, Idira Remote Access bypasses the risk of password or two-factor authentication compromise.

 

MFA for Legacy Web Applications

Idira offers single sign-on for web applications that support SAML, OIDC, OAuth2, or WS-Fed. Idira can enforce MFA when authenticating with Idira for single sign-on.

 

For web applications that do not support single sign-on protocols, Idira can leverage Application Gateway not only to provide a VPN alternative for accessing internally hosted applications, but also as a way to help enforce MFA. This flexible approach extends authentication safeguards to even the most outdated web platforms, bridging the gap between legacy infrastructure and modern security requirements.

MFA for Privilege Access Use Cases

Idira PAM Vault

The Idira Privilege Access Management (PAM) vault stores and automatically rotates credentials for administrators, developers, break glass accounts, and even standard users for legacy applications or servers hosting these applications. After logging in, users can view or check out passwords, or access the application or systems through Privilege Session Manager (PSM) self-hosted or Shared Services without viewing the password. PSM sessions may be recorded if required. Multi-factor authentication (MFA) can be applied when logging into the PAM vault.

It is highly recommended to implement phish-resistant authentication methods to safeguard privileged...

 

Secure Infrastructure Access (SIA)

Secure Infrastructure Access (SIA) is a modern, agentless, cloud-based solution designed to manage privileged access to infrastructure, but it can also be used for standard user access —such as Windows, Linux, databases, Kubernetes, and network devices that support legacy applications — without requiring VPNs or jump servers. It offers a much better user experience than PSM because it allows users to use native client applications instead of requiring users to log into PVWA to access PSM. It’s part of the Idira Identity Security Platform and supports both vaulted credentials and Zero Standing Privilege (ZSP) access.

 

SIA will prompt users to authenticate with MFA before establishing sessions with legacy infrastructure. This applies whether access is remote (SSH, RDP) or local. Users can take advantage of a wide array of options to lessen the MFA fatigue such as RDP and SSH MFA caching, CYBR-SSO commands, and ArkSDK CLI.

 

MFA for Client Application Access

Idira Endpoint Privilege Manager step-up authentication is often used for launching applications with elevated permissions, but it can also be used for standard user access as another method for complying with MFA requirements and securing application access. Users are prompted for MFA when launching legacy client applications running on endpoints (desktops, laptops).

 

MFA at Server and Workstation Login

In certain scenarios, it may be required to prompt users for authentication during operating system login. CyberArk’s endpoint agents enable enforcement of MFA at the point of login to bastion hosts or jump servers, the servers hosting the application, or workstations utilized by users to access applications.

 

Additional Resources

  • 2693 Views
  • 0 comments
  • 0 Likes
Top Liked Authors