- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
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 traditional Privileged Session Manager (PSM) and Privileged Session Manager Proxy (PSMP) technologies, covering use cases such SSH 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
Evaluate Existing Standing Access. 7
Vault & Rotate Existing Standing Access Accounts. 7
Enable Vaulted Access via SIA to Linux. 8
Plan Recurring Access Policies. 9
Test & Pilot Zero Standing Privilege Workflows. 10
Enable Zero Standing Privilege for SSH Access. 10
Remove Password & SSH Key Access. 10
Reduce PSM Footprint or Remove PSM.. 11
This document is best suited for Security Architects/Subject Matter Experts (SMEs) and Administrators/Security Engineers. Security Architects/SMEs design and architect Idira solution rollouts, making them crucial for transitioning to Secure Infrastructure Access (SIA). Administrators/Security Engineers maintain Idira solutions, create policies, and execute project tasks, ensuring effective implementation and management of SIA and Zero Standing Privileges (ZSP).
Adopting Secure Infrastructure Access (SIA) with Zero Standing Privileges (ZSP) offers significant benefits and outcomes for organizations. By transitioning from traditional session management solutions like Privileged Session Manager (PSM) and Privileged Session Manager for SSH (PSMP) to SIA, organizations can continue to minimize security risks through session isolation and monitoring while reducing cost. This modern, agentless, SaaS-based solution enhances privileged access management by reducing the footprint of the deployment, improving performance, and providing a better user experience. Additionally, SIA supports various use cases, ensuring comprehensive coverage and streamlined access management. Implementing SIA and ZSP allows organizations to quickly modernize their security posture with minimal internal dissent, leading to a more secure and efficient operational environment.
When PSM or PSMP is used for SSH connections, SIA delivers a lower total cost of ownership (TCO) by eliminating the need for hourly infrastructure costs. Its deployment is far less intrusive, requiring no AppLocker, Group Policy, or even complex and limiting Linux configurations like custom SSHD and requiring SELinux, leveraging lightweight connectors that simplify implementation. The environment’s overall security is further enhanced through Just-in-Time (JIT) PAM controls, eliminating the need for standing privileged credentials that must be inventoried, rotated, and their lifecycles 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. This is especially valuable in environments where elastic workloads are used. SIA will connect users to the system without the need for an existing account removing the need to create accounts on the target, onboard them into PAM, and off from PAM as systems scale up and down.
The table below lays out a comparison showing the benefits that SIA offers.
|
|
SIA |
PSM |
PSMP |
|
Load balancing & High Availability |
Built-in |
Third party Load Balancing and manual failover required | |
|
OS Configurations |
Not Required *Customer Hardening Supported |
GPO, AppLocker, UAC |
SSHD, SELinux |
|
Local Account Requirements |
A single Virtual Account on SIA windows connector |
PSM Connect; PSMAdmin Connect local user accounts | |
|
Capacity |
500 concurrent SSH |
10 concurrent SSH |
<200 concurrent sessions |
|
Supports ZSP? |
Yes |
No | |
|
Upgrade Process |
Seamless |
Requires planning and potential downtime | |
|
Recommended On-premises Host Type |
Virtual Machine |
Physical Server | |
|
Requires Port 1858 to Vault |
No |
Yes | |
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 Linux targets and administrators will need to closely manage and monitor the transition to ensure a smooth implementation and ongoing operation.
Implementing Secure Infrastructure Access (SIA) and Zero Standing Privileges (ZSP) involves several key steps to enhance security and operational efficiency. These steps include setting up certificate requirements, evaluating existing standing access, vaulting and rotating accounts, enabling vaulted access via SIA to Linux, planning recurring access policies, testing and piloting ZSP workflows, removing password and SSH key access, and enabling ZSP for SSH access. Each step is designed to ensure a secure and streamlined access management process.
Idira ZSP reduces the use of standing access in the environment including Linux servers. SIA generates and signs an SSH certificate with the CA private key which is used to authenticate the end user to the target machines as an existing local user of the target machine. The existing local user must be configured to only allow SSH Certificate based authentication and without password or SSH Key authentication. Every new authorized connection request, even by the same user to the same target, generates a new SSH certificate. It is necessary to prepare the Idira CA SSH public key on all Linux servers used for operational access.
First, reach out to the Internal PKI team to validate whether an internal SSH CA public key is already installed on Linux servers. Next, determine the appropriate deployment method for the new Idira SSH CA public key. If an SSH CA public key is installed, download the Idira SSH CA public key to be used within SIA’s configuration. If not, download a deployment script to automatically deploy the necessary SSH CA public key. More information on this process can be found at Certificate Creation for SSH Connections Using SIA and Manage certificates for SIA.
Idira recommends automating the process of deploying the public key to target Linux systems. This can be done with client management or automation solutions.
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.
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.
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:
For organizations with existing privileged session management (PSM) and/or privileged session management for SSH (PSMP) 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.
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.
SIA can be configured to provide vaulted access to end users in the same way that PSM/P does. It is transparent to end users and easy to implement. Once SIA is deployed, the next step is to configure vaulted Linux accounts to use SIA. This can allow organizations to immediately reduce their PSM/P 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 their administrative privilege removed altogether. CyberArk’s best practice is to first enable access for vaulted built-in Linux root accounts, then move on to any personal privileged or shared use accounts. Best practice for built-in “root” accounts is to disable SSH login. In this scenario, SIA can still facilitate access to the target system by leveraging a “Logon” account. More information can be found at Manage virtual machine access.
SIA supports SSH connections from native clients directly from users’ workstations, however, if a more guided connection workflow is needed for end users 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?
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 ZSP SSH access to Linux systems, SIA requires the presence of an account on the target system that it can create an SSH Certificate for to facilitate the login flow. The target account must have password login disabled and should be controlled centrally via a centralized configuration management system.
To develop a comprehensive test plan, begin by outlining the objectives and scope of the pilot, ensuring you identify key metrics for success, such as security improvements and user adoption rates. Conduct the pilot by implementing Zero Standing Privilege (ZSP) workflows in a controlled environment where performance can be closely monitored and feedback gathered. This involves configuring recurring access policies that generate temporary accounts and allocate privileges only at the time of connection. After conducting the pilot, evaluate the results by analyzing the collected data to assess the effectiveness of the ZSP workflows. Based on this feedback, make necessary adjustments to optimize the approach before broader implementation.
Identifying a pilot group is crucial to the success of implementing Zero Standing Privilege (ZSP) workflows. Begin by selecting a representative group of users who have a diverse set of needs and access requirements. Defining the scope of the pilot, including the specific systems and applications that will be tested, ensures comprehensive coverage. Conduct testing with the pilot group, making sure all use cases, such as SSH and SFTP access, are thoroughly evaluated. Continuous monitoring and auditing are essential to validate the effectiveness of the workflows and to identify any issues promptly. Evaluating the results involves assessing whether the ZSP implementation was successful, gathering end-user feedback, and observing any inherent workflow issues that may have emerged during testing.
Once the ZSP workflows have been properly tested and vetted, it should be enabled for all users who access Linux systems. Ensure users are properly educated on the new connection flows and prepare documentation such as FAQs, guides, and troubleshooting materials for end users. This will streamline their adoption of ZSP allowing organizations to continue to secure the environment further.
Once ZSP workflows have been piloted, vetted and enabled, password and SSH Key access for the accounts required for ZSP flow on the target systems can be disabled.
It is recommended to remove any standing access rights to existing operational accounts that have access to target machines. Removing existing standing access should be a phased approach determined by your unique onboarding plan to SIA. To ensure a smooth transition to this new security control, users can temporarily access target systems with either standing or dynamic access. For more information, see Reduce standing access | Idira Docs.
Taking the concept of Zero Standing Privileges further, organizations can move to the final step of removing any local accounts that were left for the ZSP flows. Organizations can leverage functionality provided by Endpoint Privileges Manager to create users on the fly supporting a full ZSP approach. With EPM installed on the target systems, it will integrate with active directory and create user accounts on the target system at the time of the SIA connection. SIA will then provision the right privileges for that user account and the users can continue to perform their tasks as expected. This workflow can be even further enhanced by configuring EPM policies to allow only approved commands to protect from privilege abuse and support more granular privilege control on the system.
Finally, once all SSH use cases have been moved to SIA, the next step is reducing the number of PSM or PSMP servers or their resources. This can greatly decrease the operating costs of the environment. Now that all SSH workflows are moved to SIA, organizations can consider reducing the number of PSM or PSMP servers in the environment or removing them altogether if SSH 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.
|
Reference Name |
URL |
|
SIA Best Practices |
SIA Best Practices: Architecture, Configuration, Security, and Operations |
| Subject | Likes |
|---|---|
| 1 Like | |
| 1 Like | |
| 1 Like | |
| 1 Like | |
| 1 Like |

