This guide outlines the steps to create and configure a strong account, CYBR-SA01, as a domain account in Active Directory (AD) for use with Idira Secure Infrastructure Access (SIA) to manage ephemeral users, such as UserID-sBmF2M9TUGYWzRV. The account is added to a security group, SIA-StrongAccountGroup, which is configured with permissions to create, delete, and manage user accounts, modify group membership, and delete user profile folders under C:\Users on target servers for session cleanup in the OU where the security group is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com. Idira recommends using a domain account rather than a local account with the same name and password on all target machines, and the account must be a member of the local Administrators group on each target system, preferably managed via a Domain Group Policy Object (GPO), with a Local GPO used when needed.
Steps
Step 1: Create the Strong Account in Active Directory
Open Active Directory Users and Computers (ADUC): Launch ADUC on a domain controller or a machine with AD administrative tools. Navigate to the desired Organizational Unit (OU), for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com. Create the Strong Account: Right-click the OU, select New > User. Enter CYBR-SA01 for Full name and User logon name, for example. Set a strong initial password and select Password never expires to prevent disruptions (ensure password rotation is managed by Idira Privilege Cloud CPM). The account will be created in the default Domain Users group with minimal permissions. This account will need to be added to a Safe in Idira SIA for secure management and password rotation. Click Next and Finish to create the domain account, CYBR-SA01. Secure the Account: Right-click CYBR-SA01, select Properties, and go to the Account tab. Check Account is sensitive and cannot be delegated to enhance security.
Step 2: Add the Strong Account to a Safe
Add the Strong Account to a Safe: Log in to the Idira Privilege Cloud portal. Go to the Safes page, click Create Safe. Set the Safe name to SIA-StrongAccounts. Once created, select the SIA-StrongAccounts Safe, go to the Members tab, and click Add members. On the Select Safe members page, search for and select the DPA RDP Privilege Cloud Secrets Access role to enable retrieval of CYBR-SA01 during Dynamic Privileged Access (DPA) provisioning, then click Next. On the Set Safe permissions page, verify that Read only is selected for Permissions presets. Save the configuration.
Step 3: Delegate Permissions in Active Directory
The strong account should be a domain user defined with only those permissions required to perform the following operations in the OU where the security group SIA-StrongAccountGroup is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com, as defined in the SIA access policy:
Create, delete, and manage user accounts Modify the membership of a group
To perform profile cleanup at the end of the session, the account should also have sufficient permissions to delete folders under C:\Users on the target servers. The security group SIA-StrongAccountGroup will be the AD group used when setting up an ephemeral domain user policy.
Create a Security Group and Add CYBR-SA01: In ADUC, navigate to an OU, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com. Right-click the OU, select New > Group, and name the group SIA-StrongAccountGroup. Set the group type to Security and scope to Domain local. Right-click SIA-StrongAccountGroup, select Properties, go to the Members tab, and click Add. Search for and add CYBR-SA01 to the group. Delegate Permissions for User and Group Management:
Create, delete, and manage user accounts Modify the membership of a group
In ADUC, right-click the OU where SIA-StrongAccountGroup is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com. Select Delegate Control. Add SIA-StrongAccountGroup in the Users or Groups step. Delegate the following common tasks:
Create, delete, and manage user accounts Modify the membership of a group
Avoid granting unnecessary permissions beyond those required for user and group management. Grant Permissions for Profile Cleanup:
Create or edit a Domain GPO linked to the OU where SIA-StrongAccountGroup is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com. Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > File System>Right Click Add C:\Users, assign SIA-StrongAccountGroup Full Control, and apply to This folder, subfolders, and files.
On the target server, open Local Group Policy Editor (gpedit.msc). Navigate to Computer Configuration > Windows Settings > Security Settings > File System. Add C:\Users, assign SIA-StrongAccountGroup Full Control, and apply to This folder, subfolders, and files.
On each target server, grant SIA-StrongAccountGroup Full Control permissions on the C:\Users folder to allow deletion of user profile folders (e.g., C:\Users\UserID-sBmF2M9TUGYWzRV) at session end. To configure via Domain GPO: For non-domain-joined systems or when a Domain GPO cannot be applied, configure a Local GPO: Verify Permissions: In ADUC, right-click the OU where SIA-StrongAccountGroup is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com, select Properties > Security tab. Click Advanced, locate SIA-StrongAccountGroup, and confirm it has Create User objects, Delete User objects, Read All Properties, and Write All Properties for User objects, and Write All Properties for Group objects. On a target server, right-click C:\Users, select Properties > Security tab, and confirm SIA-StrongAccountGroup has Full Control. Verify that CYBR-SA01 is a member of SIA-StrongAccountGroup in ADUC. Important Note: The security group configured in the SIA policy, SIA-StrongAccountGroup, determines the OU where ephemeral user accounts are created and removed. For example, if SIA-StrongAccountGroup is stored in OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com, ephemeral user accounts (e.g., UserID-sBmF2M9TUGYWzRV) will be created and removed within this OU.
Step 4: Configure Group Policy for Minimal Permissions and Local Administrators Membership
Create a Domain Group Policy Object (GPO): Open Group Policy Management Console (GPMC). Right-click the OU where SIA-StrongAccountGroup is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com, and select Create a GPO in this domain, and Link it here. Name the GPO,SIA-StrongAccount_LocalPermissions. Add CYBR-SA01 to Local Administrators Group:
On the target server, open Local Group Policy Editor (gpedit.msc). Navigate to Computer Configuration > Windows Settings > Security Settings > Restricted Groups. Add the Administrators group and include CYBR-SA01 as a member.
Edit the Domain GPO and navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Restricted Groups. Right-click Restricted Groups, select Add Group, and add Administrators. In the Members section, add CYBR-SA01 to ensure it is a member of the local Administrators group on each target system in the OU. This is the recommended method for domain-joined systems, as it can be easily managed and aligns with common organizational capabilities. For non-domain-joined systems or when a Domain GPO cannot be applied, configure a Local GPO: Deny Logon Policies:
Deny log on locally. Deny log on through Remote Desktop Services. Deny log on as a batch job. Deny log on as a service.
On the target server, open Local Group Policy Editor (gpedit.msc). Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment. Add CYBR-SA01 to the same deny logon policies listed above.
In the Domain GPO, navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignment. Add CYBR-SA01 to the following policies to restrict access and prevent abuse: For non-domain-joined systems or when a Domain GPO cannot be applied, configure a Local GPO: Apply the GPO: For the Domain GPO, link it to the OU where SIA-StrongAccountGroup is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com. Run gpupdate /force on affected systems to apply the Domain GPO. For Local GPOs, apply changes on each target server by closing the Local Group Policy Editor or running gpupdate /force.
Step 5: Configure the Strong Account in Idira SIA
Configure a Strong Account:
Safe: SIA-StrongAccounts. Account name: CYBR-SA01. Domain: example.com. Enable creation of ephemeral domain users: Check this option to allow CYBR-SA01 to create ephemeral users like UserID-sBmF2M9TUGYWzRV. Ensure CYBR-SA01 belongs to the domain defined in the Domain field (example.com). Domain controller name (optional): Enter the hostname or FQDN of a writable domain controller (e.g., dc01.example.com). If an SIA Connector is installed, the connector will deduce the name, and this field is optional. Otherwise, this field is mandatory to ensure SIA can create ephemeral users. Domain NetBIOS (optional): Enter the domain NetBIOS name (e.g., EXAMPLE). If an SIA Connector is installed, the connector will deduce the name, and this field is optional. Otherwise, this field is mandatory. Enable LDAP Secure: Check this option to use LDAP Secure over TLS with port 636 for creating ephemeral users in Active Directory. Enable certificate validation: Do not check this option during initial setup, as certificate validation will be enabled later after testing the strong account and ephemeral user creation. Enable WinRM over HTTPS: Check this option to use WinRM over HTTPS with port 5986 for deleting ephemeral user profiles. Enable certificate validation: Do not check this option during initial setup, as certificate validation will be enabled later after testing the strong account and ephemeral user creation.
Log in to the Idira SIA portal. Navigate to Strong accounts. Click Add a strong account. Select the strong account location: Domain account. Enter the following details: Click Add and continue to complete the account configuration. Ensure the DPA RDP Privilege Cloud Secrets Access role is assigned to the SIA-StrongAccounts Safe in Idira SIA (configured in Step 2). For PAM Self-Hosted environments, ensure the service user CyberarkSecureAccessService has List and Retrieve permissions to the SIA-StrongAccounts Safe.
Step 6: Confirm the Configuration
Verify Account Existence in Active Directory: Open ADUC and navigate to an OU, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com. Confirm CYBR-SA01 exists with Password never expires and Account is sensitive and cannot be delegated enabled (Step 1.3). Check Delegated Permissions: In ADUC, right-click the OU where SIA-StrongAccountGroup is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com, select Properties > Security tab. Click Advanced, locate SIA-StrongAccountGroup, and confirm it has Create User objects, Delete User objects, Read All Properties, and Write All Properties for User objects, and Write All Properties for Group objects. On a target server, right-click C:\Users, select Properties > Security tab, and confirm SIA-StrongAccountGroup has Full Control (via Domain or Local GPO). Verify that CYBR-SA01 is a member of SIA-StrongAccountGroup in ADUC. Confirm Group Policy Settings: For domain-joined systems in the OU where SIA-StrongAccountGroup is stored, for example, OU=StrongAccounts,OU=SIA,OU=Users,DC=example,DC=com, run gpresult /r to ensure the StrongAccount_LocalPermissions Domain GPO applies. Verify CYBR-SA01 is in the local Administrators group via Computer Management > Local Users and Groups > Groups. Confirm CYBR-SA01 is listed in Deny log on locally, Deny log on through Remote Desktop Services, Deny log on as a batch job, and Deny log on as a service policies. For non-domain-joined systems, open Local Group Policy Editor (gpedit.msc) on the target server and verify the same settings (Administrators group membership and deny logon policies) are applied via the Local GPO named StrongAccount_LocalPermissions. Test Safe Permissions in Idira SIA: Log in to the Idira SIA portal. Verify that CYBR-SA01 is listed as a member of the SIA-StrongAccounts Safe with the DPA RDP Privilege Cloud Secrets Access role and read only permissions. Confirm that you can successfully use Verify for the strong account in the SIA portal. Test in Idira SIA: Verify an SIA access policy has been created for the domain ephemeral and test using the Connection guidance page in the SIA portal.
*Note:
Implement TLS Certificate Validation (Mandatory for Production): After confirming successful ephemeral user creation and profile cleanup without certificate validation
Manage certificates:
https://docs.cyberark.com/ispss-access/latest/en/content/hometileslps/dpa-crtfcts-lp.htm
https://community.cyberark.com/s/article/SIA-Target-Validation-Error
View full article