This post is to describe the configuration for integrating CyberArk with other popular enterprise software or services. 

    LDAP Integration

    – (Optional) Windows Domain Controller Firewall Rule to allow CyberArk Servers to query AD database. (LDAP 389 and LDAPS 636)
    – LDAP Bind Account
    – LDAP Groups
    – Enable LDAP/S

    LDAPS Integration

    Configured through PVWA

    LDAP Login for PVWA

    LDAP Login for Vault

    • import CA root cert
    • configure DNS record in hosts file
    Bindusername and bindpassword is the one you entered when you integrated CyberArk with your LDAP. If for some reason, you are having trouble to create a new mapping , usually there is an issue with your binding account. You can modify username / password from following configuration location:

    Note: once your CyberArk integrated with LDAP, the LDAP integration wizard will grey out. To re-activate LDAP integration wizard, you will need to delete Administration – LDAP integration – Server configuration (eg. Also delete LDAP directory mapping from PrivateArk client.

    YouTube: CyberArk PAS 12 0 Lab – 2.1 LDAP Domain Integration

    12.1 Lab – LDAP & SMTP Integration

    SMTP Notification

    There are a couple of steps you will need to make sure first before you integrated with SMTP server. First thing is to make sure ENE service is up and running. Second thing is to make sure your built-in administrator user has business email address associate with it. 
    1. Log onto the PrivateArk Administrative Client as an administrator user.
    2. Make sure that the business email address of the user who will issue ENE notifications is specified in their user properties. This user must belong to the Vault Admins group. By default, this is the Administrator user.

    Note: If you need to run the wizard again, you can change the IP address of the SMTP server to and save. Also ensure that the Event Notification Engine service is running on the Vault Server.

    Issue: PAM Administrators not receive ENE Test email.
    Make sure PAM administrators accounts have been configured a business email address. 


    Note: Time synchronization is critically important in CyberArk PAS architecture. Even more so when implementing the CyberArk Cluster Vault Management solution. In the following exercise we will integrate both nodes of the cluster vault with an external time source.

    1. Logon as Administrator to the passive node of the cluster.
    a. Using Windows File Explorer navigate to ‘C:\Program Files(x86)\PrivateArk\Server\Conf’.
    2. Edit the dbparm.ini file adding the following line to the end of the file. This will create inbound and outbound firewall rules that will allow the vault to communicate to the NTP server.

    3. Enable the Windows Time service using the Windows Services applet .
    4. Double click “Windows Time” to display the service properties.
    5. Update the Startup type to Automatic (Delayed Start) and click OK.
    6. Start the Windows Time service.
    7. Repeat the above procedures on the active node of the cluster before proceeding.
    8. To commit the changes made to the DBParm.ini file, we must restart the PrivateArk Server service.
    Note: In an HA Cluster Vault implementation, you can no longer start and stop CyberArk services through the normal interface. Services must be restarted using the ClusterVault Management or CVM interface. To restart the services, we will simply failover to the passive node to commit the changes.
    9. Ensure that you are logged into the active node of the cluster. Open the CVM to determine the active and passive node. Only the active node is capable of manually executing the failover procedure.
    10. Open the CVM on the active node and click the center icon with the opposing arrows to initiate the failover procedure.
    11. Click Continue to confirm the switch
    a. Observe the failover progress in the CVM or alternatively monitor “C:\Program Files (x86)\PrivateArk\Server\ClusterVault\ClusterVaultConsole.log”
    b. The log will display the failover sequence.
    12. Next, we need to set a special time skew so that, if the clock is very far off, the vault will not make too large of a system time change at once. This will force the NTP service to change every 30 minutes for the first 3 checks and then every 8 hours. This prevents triggering anti-tampering protections in the vault that could be activated by creating new audit entries that occur before existing audit entries.
    13. Ensure you are working on the active node.
    14. Open regedit. Browse to HKLM\System\CurrentControlSet\Services\W32Time\Parameters.
    15. Add a new DWORD and name it “Period”.
    a. Double click it and change the Base to decimal and make the Value data “65532”.
    b. Close the Registry Editor.
    16. Open an Administrative Command prompt and run the following command:
    W32tm /config /manualpeerlist: /syncfromflags:manual /reliable:YES /update
    17. Failover to the passive node. When failover is complete, login to the active node.
    Complete steps 13 – 17 on the active node of the Cluster Vault.
    18. Both nodes of the Vault Cluster are now sync’ed to an external NTP time source.

    For NTP Client Configuration on Vault:


    SIEM Integration / Syslog

    Rename one of the sample translator files
    • Translator files translate CyberArk logging format into the SIEM logging format
    • These five files will cover the most commonly deployed SIEM systems
    • The Arcsight translator file  works with Splunk and others

    Add SYSLOG configuration to dbparm.ini

    C:\Program Files (x86)\PrivateArk\Server\Conf\dbparm.ini

    AutomaticallyAddBuiltInGroups=”Backup Users,DR Users,Operators,Auditors,Notification Engines”

    • Restart the PrivateArk Server Service.
    • Use the Windows Services applet to restart, to ensure that service dependencies restart successfully.


    Configure paragent.ini with the following information:
    • SNMPHostIP The IP address of the remote computer where SNMP traps will be sent.
    • SNMPTrapPort The port through which SNMP traps will be sent to the remote computer.
    • SNMPCommunity The name of location where the SNMP traps originated.

    • Restart the PrivateArk Remote Control Agent  service to read the changes made into memory.
    • Check with the administrator of the SNMP console to ensure that the SNMP messages sent are
    being received and are readable.

    Vault Backup Steps

    Step 1: The Vault Backup utility (PAReplicate.exe) generates a metadata backup in the Vault’s Metadata Backup folder, then exports the contents of the Data folder and the contents of the Metadata Backup folder to the computer on which the Backup utility is installed.
    Step 2: After the replication process is complete, the external backup application copies all the files from the replicated Data folder and the Metadata folder.
    Keep the replicated files on the Backup utility machine after the external backup application copies all the files. The next time you run the Backup utility to the same location, it will update only the modified files and reduce the time of the replication.

    Backup folder:

    CMD Backup


    @echo off
    cd “c:\Program Files (x86)\PrivateArk\Replicate”
    echo %date% %time% Start of task > ReplicateBatch.log
    echo User=%UserName%, Path=%path% >> ReplicateBatch.log
    PAReplicate.exe Vault.ini /logonfromfile user.ini /fullbackup 1>> ReplicateBatch.log 2>> ReplicateBatch.err
    echo %date% %time% End of task >> ReplicateBatch.log

    Scheduled Job:

    • Runas Local System (run with highest privileges set)
    • Program/script: “c:\Program Files (x86)\PrivateArk\Replicate\PAReplicate.exe”
    • Add arguments: vault.ini /logonfromfile user.ini /fullbackup
    • Start in: c:\Program Files (x86)\PrivateArk\Replicate

    Firewall on Vault

    After vault has been hardened, here is how Windows Firewall with Advanced Security looks like:

    Wrong One

    Right One

    Only having CyberArk hardening process created rules. No other external configuration firewall rules. 

    By netsec

    Leave a Reply