Best Practices for Modernizing RDP Access

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
15 min read
L4 Transporter

Summary

Secure Infrastructure Access (SIA) provides a strategic path for organizations transitioning from no session management or traditional session management solutions like PSM to a modern, secure access model. As an agentless, SaaS-based solution, SIA minimizes security risks by enabling access with Zero Standing Privileges (ZSP) or through vaulted credentials, ensuring session isolation and monitoring is enabled for built-in and operational account access. It is designed to replace or complement legacy Privileged Session Manager (PSM) and Privileged Session Manager Proxy (PSMP) deployments, covering use cases such as RDP, SSH, and database access. By adopting SIA, organizations can modernize privileged access management with reduced costs, improved performance, and enhance user experience. This best practice will allow your organization to roll out SIA and ZSP quickly and with minimal internal dissent.

 

For additional information on various forms of privileged access states, see State of privilege and access hierarchy.

Contents

Benefits and Outcomes. 3

PSM/SIA Comparison. 3

SIA Architecture. 3

Methodology Overview.. 6

Evaluate and Inventory Existing Accounts and Access. 6

Discovery. 6

Vault and Rotate Existing Standing Accounts. 7

Continue to Use PSM While Enabling ZSP. 7

Deploy SIA. 8

Enable Vaulted Access via SIA. 8

Enable Just-in-Time Elevation for Vaulted Accounts. 9

Enable ZSP. 10

Move users to ZSP. 10

Remove privileged accounts. 10

Reduce PSM Footprint or Remove PSM.. 10

User Experience Impacts. 11

Additional Information. 11

 

Audience

  • Administrator/Security Engineer
  • Security Architect/Subject Matter Expert
  • Program Director

This best practice will directly relate to the usage of CyberArk’s Session Management products (PSM and SIA). It will cover the methodology guidance for administrators on how to shift RDP access from PSM to SIA with ZSP for operational accounts and vaulted account access for built-in privileged accounts. Security Architects will benefit from understanding how SIA integrates with existing security frameworks while enhancing compliance and oversight. Program Directors will find value in the streamlined deployment process, which minimizes disruptions and reduces the total cost of ownership, ensuring efficient allocation of resources and improved team adoption.

Benefits and Outcomes

Unlike traditional Privileged Session Management (PSM) solutions that require extensive deployment configurations, Microsoft RDS licensing, and third-party load balancing maintenance, Secure Infrastructure Access (SIA) offers built-in high availability and load balancing, ensuring seamless performance without additional complexity and cost. With a streamlined deployment process, SIA can be up and running in minutes while also supporting zero-downtime upgrades that eliminate disruptions. Its unified connector management provides a single pane of glass for audits and Security Operations Center (SOC) visibility, enhancing oversight and compliance. By reducing the administrative burden on Privileged Access Management (PAM) teams, SIA allows organizations to focus on security rather than operational overhead, leading to increased adoption across teams.

 

SIA also delivers a lower total cost of ownership (TCO) by eliminating the need for Remote Desktop Services (RDS) licensing and reducing hourly infrastructure costs. Its deployment is far less intrusive, requiring no AppLocker or Group Policy Object (GPO) configurations while leveraging lightweight connectors that simplify implementation. Security is further enhanced through Just-in-Time (JIT) PAM controls, eliminating the need for standing privileged credentials that must be inventoried, rotated, and managed. Instead, SIA supports a Zero Standing Privilege (ZSP) model, granting access only when necessary and for a limited time, significantly reducing the attack surface.

 

 

PSM/SIA Comparison

 

SIA

PSM

Licensing

Only required in some cases  [1]

RDS Licensing Required

Load balancing & High Availability

Built-in

Third party Load Balancing and manual failover required

OS Configurations

Not Required

*Customer Hardening Supported

GPO, AppLocker, UAC, etc.

Capacity

8gb RAM + 2vCPU:

100 concurrent RDP

8gb RAM + 8 Core CPU:

10 concurrent RDP

Supports ZSP?

Yes

No

Upgrade Process

Seamless

Requires extensive planning and downtime

Machine Type Recommended

Virtual Machine

Physical Server

Requires Port 1858 to Vault

No

Yes

 

 

SIA Architecture

With VPN-less native access to targets using vaulted credentials and ZSP, SIA enables secure remote access without the complexity of traditional VPNs. Its flexibility across on-premises, hybrid, and cloud environments ensure seamless integration with existing infrastructure. Additionally, SIA strengthens security through credential vaulting and rotation, session isolation and monitoring, and comprehensive audit trails, ensuring compliance and risk mitigation. As a target-agnostic solution, SIA facilitates secure access to servers, databases, and cloud workloads, providing a versatile and future-proof approach to privileged access management.

 

ka3Vy000007aD4LIAU__eid=ka3Vy000007aD4L&feoid=00N2J00000APFDu&refid=0EMVy00000QKHAb.png

ka3Vy000007aD4LIAU__eid=ka3Vy000007aD4L&feoid=00N2J00000APFDu&refid=0EMVy00000QKH8z.png

 

 

Methodology Overview

ka3Vy000007aD4LIAU__eid=ka3Vy000007aD4L&feoid=00N2J00000APFDu&refid=0EMVy00000QKH0w.png

Evaluate and Inventory Existing Accounts and Access

Before transitioning to a Zero Standing Privilege (ZSP) model with Idira Privilege Cloud, organizations must first assess their current privileged access landscape. This begins with a comprehensive inventory of all existing privileged accounts, credentials, and access pathways across the environment. The goal is to identify where standing privileges exist, who has access, and how those accounts are being used.

 

Discovery

If privileged accounts are not already comprehensively accounted for and managed, organizations should leverage Idira Discovery to automatically discover and onboard privileged accounts across systems. This process helps uncover shadow IT, unmanaged credentials, and legacy accounts that may pose security risks. Once the inventory is complete, organizations can classify accounts based on their risk level, usage patterns, and criticality to operations. This assessment provides a clear roadmap for implementing a Just-in-Time (JIT) access model by ensuring that only necessary accounts are maintained, and all others are either vaulted, rotated, or removed.

 

Additionally, organizations should analyze session logs and access patterns to determine which accounts require continuous access and which can transition to JIT controls. This step is crucial for understanding dependencies, minimizing disruption, and prioritizing security improvements. By conducting a thorough evaluation, organizations set a strong foundation for a phased and strategic adoption of Idira Privilege Cloud, ensuring that privileged access is both secure and operationally efficient.

 

Vault and Rotate Existing Standing Accounts

Once privileged accounts are identified, the next critical step is to secure them immediately by vaulting and rotating credentials within Idira Privilege Cloud. Standing privileged accounts—those with persistent access—pose a significant security risk because they can be targeted by attackers, exploited in insider threats, and create compliance challenges.

 

Vaulting these accounts ensures that credentials are no longer stored or shared in unsecured locations, such as spreadsheets or configuration files. Instead, they are securely managed in an encrypted, centralized vault that enforces strict access controls and auditing. Idira Privilege Cloud enables automatic credential rotation, eliminating the need for static passwords that can be compromised over time. This ensures that even if an attacker gains access to an old credential, it becomes useless after rotation.

 

By immediately vaulting and rotating credentials, organizations achieve two key security outcomes:

  1. Immediate Risk Reduction – Removing standing credentials from human management and automating password rotation significantly reduces the risk of unauthorized access and lateral movement by attackers.
  2. Acceleration Toward ZSP – This step lays the groundwork for a true Zero Standing Privilege model by ensuring that credentials are no longer permanently assigned but instead issued dynamically as needed.

For organizations with existing privileged session management (PSM) in place, vaulting and rotating credentials can be implemented alongside existing session isolation mechanisms, ensuring continuous security while transitioning toward a fully JIT-enabled architecture.

 

Continue to Use PSM While Enabling ZSP

For organizations that already have Privileged Session Management (PSM) in place, it is beneficial to continue leveraging its session isolation and monitoring capabilities while enabling Secure Infrastructure Access (SIA) for Just-in-Time (JIT) access or Zero Standing Privilege (ZSP). PSM provides strong controls for session recording, auditing, and enforcement, ensuring that all privileged sessions are monitored and logged for security and compliance. However, traditional PSM implementations often rely on standing privileged accounts, which contradict the principles of Zero Standing Privilege (ZSP). By introducing SIA alongside PSM, organizations can progressively transition to a ZSP model while maintaining session control and oversight.

 

Using SIA in conjunction with PSM allows for a phased migration to JIT access. Initially, privileged users can continue accessing resources through PSM while their accounts are vaulted, rotated, and gradually transitioned to JIT-based access. Over time, instead of logging into persistent privileged accounts, users will authenticate through SIA, which dynamically provisions credentials only when needed. This ensures that standing credentials are minimized while maintaining the security and visibility of session management. 

 

Another advantage of combining SIA with PSM is improved operational flexibility. Idira Privilege Cloud allows organizations to configure SIA access within the Privileged Vault Web Access (PVWA) interface, streamlining the integration. Whether PSM is already in place or not, administrators can follow straightforward configuration steps to enable SIA access globally or on a per-platform basis. By modifying platform settings to connect via Distributed Privilege Access (DPA) and applying necessary user overrides, organizations can ensure a smooth transition to JIT access without disrupting existing workflows. 

 

The long-term benefit of enabling SIA while retaining PSM capabilities is a more secure, scalable, and user-friendly privileged access strategy. Session isolation, auditability, and oversight remain intact while reducing reliance on standing privileged credentials. As organizations mature their security posture, they can shift more access control to SIA, leveraging its VPN-less, native access capabilities and fully embracing a Zero Standing Privilege model without sacrificing visibility or governance.

 

Deploy SIA

If SIA is not already deployed in the environment, administrators can follow a simple process to install the SIA connector. Below is a brief explanation of that process and assumes that the reader has already deployed Privilege Cloud and sign-in flows for their users.

 

  1. Review the SIA requirements to understand what must be configured within the environment before the SIA installation.
  2. Become familiar with Reduce standing access to understand how ZSP is implemented for a window use cases.
  3. Review SIA connector pools and connectors  to understand connector pools, connectors, and best practices for connector installation.
  4. Follow the process to Install a connector  . For this best practice, refer to the “Microsoft Windows” installation.
  5. Finally, refer to Add and manage strong accounts for Windows targets to understand how to configure the account which will facilitate the creation and deletion of ephemeral accounts used for ZSP. Best practices for creating the strong account are provided in the “Strong Account Creation” best practices document.

 

Enable Vaulted Access via SIA

SIA can be configured to provide vaulted access to end users in the same way that PSM does. It is transparent to end users and easy to implement. Once SIA is deployed, the next step is to configure vaulted windows accounts to use SIA. This can allow organizations to immediately reduce their PSM footprint while maintaining critical access for their end users.

 

Note that all built-in accounts are necessitate being vaulted and rotated and cannot be moved to a ZSP approach. This is because those types of accounts cannot have its administrative privilege removed altogether. CyberArk’s best practice is to first enable access for vaulted built-in Windows Local Administrator accounts, then move on to any personal privileged or shared use accounts.

 

Using the Secure Access space for vaulted credentials is recommended. Vaulted privileged credentials will appear in the Secure Access space by default for the users entitled to those accounts. Users can then use the connect button and select the target to access. This approach is suggested for long-term access as it enables users to perform all activities from a single interface. For more information about the Secure Access Space and capabilities, see What is the Secure Access space?

 

For customers who must retain access via the “Connect” button in the PVWA, vaulted account access can be configured centrally via the PSM-RDP connection component settings under administration, or per platform at the connection component level. Idira recommends a phased approach for this so that the new connection method can be tested and validated by smaller groups of accounts before moving to a more centralized one. For this, see the “Configure a Windows platform” section in Configure the Privilege Cloud Portal to support SIA access.

 

Enable Just-in-Time Elevation for Vaulted Accounts

To secure Windows accounts with standing privileges, administrators can configure SIA policies for just-in-time elevation. This adds vaulted accounts to local groups only when needed, removing their privileges when not in use. Thus, accounts are completely unprivileged when inactive. The following high-level procedure can be followed to achieve this.

 

  1. Inventory privileged groups where users are members. Typically, this is the built-in “Administrators” group on windows systems.
  2. Identify if the accounts have direct membership in the groups or if their membership is dictated by a nested domain group.
    1. If the accounts are direct members, use group policies, endpoint management solutions, or custom automation scripts to create a new group on the target systems with equal privileges as the users’ existing group.
      1. Alternatively, the “Administrators” or existing group name can be used. However, be cautioned, when the users connect to a target system, their direct membership will be removed when they disconnect. In some cases, this may be the desired result as it will clear the accounts’ memberships automatically resulting in accounts with zero standing privileges.
    2. If the accounts are given membership to the local group via a domain group’s membership the existing group names can be used. When the user connects, it will add the user directly to the local group then remove their direct membership from the local group. They will retain their membership of the domain group whose membership will be removed later.
  3. Create access policies for the relevant users and configure the “profile” in the access rule with the group(s) name.
  4. Educate users on using the “Just-in-time elevation with a vaulted credential” option when connecting with the vaulted credential.
  5. Remove the standing membership from the privileged credentials.
    1. For situations where a domain group is nested into a local group, the nested group should be removed from the local group. This can be done with group policy configurations, endpoint management solutions, or custom automation scripts.

 

Enable ZSP

The subsequent step involves enabling ZSP access. In contrast to Just-in-time elevation, SIA generates a temporary account and allocates privileges at the time of connection. Upon disconnecting, it revokes privileges and deletes the account, ensuring that privileged accounts do not have any pre-existing privileges and do not exist prior to connection. This significantly enhances security.

 

Enabling ZSP access is done by configuring recurring access policies. Refer to Create a recurring access policy | Idira Docs . Best practices for policy configurations and naming can be found in their respective best practices documents. Idira recommends planning by highest risk as recommended by Idira Blueprint. The most addressed initial use cases are included below. Note that policy best practices can be found in the Best Practices document tailored to that topic.

  • For most organizations, starting with Domain Administrators is recommended. The optimal best practice for the Domain Admins group in an Active Directory domain is to keep the group solely populated with the built-in administrator account, devoid of any additional accounts. Implementing ZSP for domain administrators facilitates this approach effectively.
  • Switching to domain-based Windows administrator accounts is the logical next step. Organizations often use accounts like "ADM" or "Admin-" for privileged users to access Windows systems and assigned on a 1:1 basis. Policies should be created for these accounts to enable ZSP access to windows servers. For this, see Set up Windows ZSP access with an ephemeral domain user.
  • Finally, there may be cases where windows servers have additional local accounts that are members of the local administrators group. This approach is commonly adopted because the servers are not domain-joined. See Set up and access an out-of-domain Windows target. for more information.

 

Move users to ZSP

Once ZSP has been enabled, it’s time to begin using ZSP. It’s critical that administrators effectively communicate the change with their users and educate them on the process for connecting via ZSP. Overall, the general process remains unchanged from those discussed above - from the Secure Access space. See Connect to a Windows target  for more information.

 

Remove privileged accounts

Once all users have begun using ZSP, the accounts that the users once used which had standing privileges can be disabled and eventually removed. Organizations should adhere to their own procedures and requirements to determine how long they should retain the accounts, but they should, at the very least be disabled at this stage. It’s best practice to disable the accounts in a systematic way, monitoring any issues throughout the process. Start with lower-risk batches of accounts and move to more critical during maintenance windows.

 

Reduce PSM Footprint or Remove PSM

Reducing the number of PSMs or their resources can greatly decrease the operating costs of the environment.  Now that all RDP workflows are moved to SIA, organizations can consider reducing the number of PSM servers in the environment or removing them altogether if RDP access is all they are used for.

 

It’s critical to evaluate if PSMs are used for additional use cases not currently addressed by SIA like Domain Admin access via thick clients like ADUC, GPMC, DNS snap-ins. An activity report can be run from the Privilege Cloud web interface to understand which connection components continue to be used. Once the evaluation is complete, organizations can decide if the resources (RAM; CPU) or the number of PSMs can be reduced.

 

User Experience Impacts

Enabling ZSP (Zero Standing Privileges) access will necessitate changes for users. Administrators must communicate these changes and educate users on the new process for connecting via ZSP. A helpful Guide for Moving from PSM/P to SIA that includes communications is included in our customer community portal.

 

Overall, users will need to adapt to new methods of accessing Windows targets and administrators will need to closely manage and monitor the transition to ensure a smooth implementation and ongoing operation.

 

Additional Information

Reference Name

URL

SIA Best Practices

SIA Best Practices: Architecture, Configuration, Security, and Operations

 

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