Info Security Memo
  • Blog
  • Sitemap
    • Categories
  • Contact
  • About
  • Resources
  • Tools
  • 51sec.org

Build Confidence

Focusing on Information Security 

Info Security Notes

CyberArk PAS (PSM) Installation - Part 4

8/1/2020

0 Comments

 
CyberArk PAS (PSM) Installation - Part 4

High Level Installation Steps:

Basically, follow the hardware requirements out of CyberArk Docs system requirements guide for hardware specs and prerequisite software needed, then do installation as show below.


EPV = Digital Vault + PVWA + CPM
PAS = EPV + PSM


Related Posts:
  • CyberArk PAS (Vault PrivateArk Server and Client) Installation - Part 1
  • CyberArk PAS (PVWA) Installation - Part 2
  • CyberArk PAS (CPM) Installation - Part 3
  • CyberArk PAS (PSM) Installation - Part 4
  • CyberArk PAS (PTA) Installation - Part 5
  • CyberArk PAS (PTA) Configuration - Part 5.1
  • CyberArk PSM HTML5 Gateway Installation and Configuration - Part 6



PSM Architect





PSM  Installation (High Level )


Enterprise Password Vault Solution (PSM) Installation High Level


For the PSMs
-        Install Windows 2012 R2 or Windows 2016

-        Install at least .NET Framework 4.6.2 (if that or a greater version not already included)

-        Install all the latest Windows OS patches

-        Add the domain account we are using to install PSM to the local administrators group of the new PSM VM build

-        The rest is performed during the install which includes:

o   Setting up the Remote Desktop Session Host role (not from individual checkboxed RD options) and selecting session-based (which will then ask for connection brokers and RD gateway servers in later steps).


Component
Description
PVWA
Password Vault Web Access (PVWA) is a fully featured web interface that provides a single console for requesting, accessing and managing privileged accounts throughout the enterprise by both end users and administrators.
CPM
Central Policy Manager is a integral part of the PAS controlling and managing the Master policy. This password management component can change passwords automatically on remote machines and store the new passwords in the EPV, with no human intervention, according to the organizational policy. It also enables organizations to verify passwords on remote machines, and reconcile them when necessary.
PSM
Privileged Session Manager enables organizations to isolate, monitor, record, and control privileged sessions on critical systems including Unix and Windows-based systems, databases and virtual machines. The solution acts as a jump server and single access control point. It prevents malware from jumping to a target system and records keystrokes and commands for continuous monitoring. The resulting detailed session recordings and audit logs are used to simplify compliance audits and accelerate forensics investigations.
PTA
Privileged Threat Analytics is an expert system for privileged account security intelligence, providing targeted, immediately actionable threat alerts by identifying previously undetectable malicious privileged user and account activity. The solution applies patent pending analytic technology to a rich set of privileged user and account behavior collected from multiple sources across the network. CyberArk Privileged Threat Analytics then produces highly accurate and immediately actionable intelligence, allowing incident response teams to respond directly to the attack.


PSM  Installation Overview

The PSM installation is divided into several configurable stages: set up, installation, post-installation, hardening and registration.

Note: https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/PSM_AutomaticInstallation.htm

PSM  Installation - Set Up

This stage performs the following:
Step
Procedure
Default setting
.Net 4.5.2
This step verifies that a compatible version of .Net Framework is installed on the machine.
Enable = "Yes"
Install Remote Desktop Services
This step installs the Remote Desktop Services (RDS) Session Host Role
Enable = "Yes"
Disable NLA
This step disables NLA.
Enable ="Yes"
Update the RDS security layer
This step updates the RDS security layer to 1.
This step is disabled by default since we highly recommend that you configure secure RDP connections using SSL. For details, see Secure RDP Connections with SSL.
Enable this step if you do not secure RDP Connections with SSL.
Enable ="No"


Configure the set up stage



  1. From the installation CD, copy the PSM folder to the component server and unzip.

    Open InstallationAutomation\Prerequisites\PrerequisitesConfig.XML and select the steps to enable by setting Enable = "Yes".
Run the set up stage
To run the script in standard mode, open a PowerShell window and run the following command:
CD “<CD-Image Path>\InstallationAutomation”
.\Execute-Stage.ps1 “<CD-Image Path>\InstallationAutomation\Prerequisites\PrerequisitesConfig.XML”

The Remote Desktop Services (RDS) installation requires a machine restart. You will be notified before the restart begins.

To run the script in silent mode which includes an automatic restart, open a PowerShell window and run the following command:
 .\Execute-Stage.ps1 .\Prerequisites\PrerequisitesConfig.XML silent


PSM  Installation Steps:


Run the PSM installation wizard.
To install PSM:
  1. Log on as a domain user who is a member of the local administrators group.
  2. Create a new folder on the PSM server machine. From the installation CD, copy the contents of the Privileged Session Manager folder to your new folder .
    Display the contents of the Privileged Session Manager folder.
  3. Start the installation procedure:
    Double-click Setup.exe or,
    On systems that are UAC-enabled, right-click Setup.exethen select Run as Administrator.
    The PSM installation wizard appears and displays a list of prerequisites that are installed before the PSM installation continues.
4. Click Install to begin the installation process; the installation process begins and the Setup window appears.
5. Click next until on the Destination Location window, click Next to accept the default location provided by the installation.
6. On the Recordings Folder window, click Next to accept the default recordings folder provided by the installation.

7. On the Password Vault Web Access Environment window, click Next to accept the default name of the PVWA Configuration Safe provided by the installation.

8. Click Next; the installation automatically installs the Oracle Instant Client, then displays the Vault's Connection Details window. Next.

9. On the Vault's Username and Password Details window, specify the username and password of the Vault user carrying out this installation, then click Next .

10. On the API Gateway Connection Details window, enter the protocol and hostname of the PVWA where the PSM connects to the API Gateway, then click Next to display the Setup Complete window. This information is used to generate an endpoint for API calls (<protocol>://<Host>/passwordvault/api).

11 Click Finish to complete the Privileged Session Manager installation.

12. Restart the PSM server. 
On the PVWA machine, run iisreset,



Activate the PSM server

To activate PSM:
  1. If you did not use the default recordings folder provided by the installation , you will need to update the path to the recordings folder.
    Go to PVWA > ADMINISTRATION > Options > Privileged Session Management > General settings > Recorder settings. Update the value of the recordings folder path on the PSM machine.
  2. You need to manually start the CyberArk Privileged Session Manager Service:
    1. Go to Start> Settings > Control Panel.
    2. Select Administrative Tools > Services.
    3. Right-click CyberArk Privileged Session Manager.
    4. Select Start.

Post Installation

The post installation stage configures the PSM server after it has been installed successfully.
The post installation stages does the following steps automatically. For troubleshooting or to perform the step manually, see the procedure:
Step
Procedure
Disables the screen saver for local PSM users
Disable the screen saver for the PSM local users
Configures users for PSM sessions
Configure users for PSM sessions
Enables PSM for web applications
Configure PSM to connect to Web applications
Enables users to print PSM sessions
Enable Users to Print PSM Sessions

Configure the post-installation stage
From the CD image, open InstallationAutomation\PostInstallation\PostInstallationConfig.XML. and select the steps you want to enable by setting Enable = "Yes"

Run the post-installation stage
Open a PowerShell window and run the following command:
 
CD “<CD-Image Path>\InstallationAutomation”
.\Execute-Stage.ps1 “<CD-Image Path>\Installation automation\PostInstallation\PostInstallationConfig.XML

Following the installation
Perform the following steps, if required:
Step
Description
Check the installation log files
Verify that the installation completed successfully.
Connect to a target system directly from desktop
If NLA is enabled in your environment and your users connect directly from their desktops.
Configure the PSM users’ passwords
This procedure describes how to configure the PSMConnect and PSMAdminConnect users’ passwords so that they are managed by the CPM.
Enable maintenance users to logon remotely
Maintenance users who need to logon remotely to the PSM server must be members of the RemoteDesktopUsers group in the PSM server and must also be added to the list of users with the “Allow log on through Remote Desktop Services” permission in the Windows security policy.





Hardening

The PSM hardening stage enhances PSM security by defining a highly secured Windows server. The hardening procedure, which disables multiple operating system services on the PSM server machine, is included as part of the PSM installation.

From the CD image, open InstallationAutomation\Hardening\HardeningConfig.XML and verify that the following parameters are set to Enable = Yes:
Step
Description
1. Runs the hardening script
The PSM hardening procedure on the PSM server machine enhances PSM security.
Default: Enabled = Yes
Additional step parameters:
  • SupportWebApplications - Set this parameter to Enable="Yes" if you are using web applications.
  • ClearRemoteDesktopUsers - For security reasons, the hardening stage clears the Remote Desktop Users group. The Remote Desktop Users group should include maintenance users that are not administrators or if, ActiveX is used, PSM local users. If you use ActiveX it is recommended to leave the ClearRemoteDesktopUsers parameter set to "No" and manually delete users from remote desktop users group after running the script.
2. Runs post hardening tasks
  • Block Internet Explorer developer tools,
  • Hide PSM local drives in PSM sessions
  • Block the Internet Explorer context menu
Default: Enabled = Yes
For details, see, After running the hardening script.
3. Run AppLocker rules
To create a hardened and secure PSM environment, the system must limit the applications that can be launched during a PSM session. To do this, the PSM uses the Windows AppLocker feature, which defines a set of rules that allow or deny applications from running on the PSM machine, based on unique file identities. These rules specify which users or groups can run those applications.
Default: Enabled = Yes
For details, see Run AppLocker rules
4. Automatic hardening in 'Out of Domain' deployments
Runs 'Out of Domain' PSM server including:
  • Imports an INF file to the local machine
  • Applies advanced audit
  • Manually Adds User Changes for Installation
  • Set time limit for active but idle RDS sessions
Default: Enabled = No
Set to Yes if you are using the PSM server out of domain.
For in domain deployments, see Automatic hardening in 'In Domain' deployments.
For configuration details, see Configure 'Out of Domain' PSM servers.
5. Harden TLS Settings
  • Disables SSL/TLS versions earlier than TLS 1.2.
  • RemoteApp requires a connection broker and a session collection to be associated with it. When PSM is installed, the RD Connection Broker is installed on the machine. This step installs SQL Server Express and configures RD Connection Broker to work with SQL Server Express.
Default: Enabled = Yes
Open a PowerShell window and run the following command:
 
CD “<CD-Image Path>\InstallationAutomation”
.\Execute-Stage.ps1 “<CD-Image Path>\Installation automation\Hardening\HardeningConfig.XML

Change PSM Server ID

  1. First, login to the PVWA, browse to Administration, System Configuration, Options, Privileged Session Management, Configured PSM Servers and select the PSM Server you need to change from the list of servers. In the properties pane, set the value of the ID property to the new Server ID, click Apply and OK. 
  2. Next, edit the basic_psm.ini file located on the PSM server in the PSM root directory and update the PSMServerlD parameter with the new Server ID, save the file and restart the "CyberArk Privileged Session Manager" service on the PSM server.
















References







via Blogger https://ift.tt/2Xbo07R
July 31, 2020 at 10:26PM CyberArk
0 Comments

CyberArk Service/Dependent Accounts Studying Notes

7/29/2020

1 Comment

 
CyberArk Service/Dependent Accounts Studying Notes

What are dependent accounts?

Dependent accounts are accounts that represent resources, such as Windows Services or Windows Scheduled Tasks, that are accessed from a target machine, and require the same credentials as the target machine. Dependent accounts may also be referred to as usages or service accounts.


When changing a password, the CPM synchronizes the target account password with all other occurrences of that password in the related dependent accounts. The following dependent accounts are supported:
  • Windows Services
Windows IIS Directory Security (Anonymous Access)
  • Windows Scheduled Tasks
Configuration Files
  • Windows Registry
Database String
  • Windows IIS Application Pools
Web Application Accounts
  • Windows COM+ Applications
Private SSH Keys
Here is CyberArk Doc's CPM Managing Service Account flow:

Create a dependent account



After you create a target account, you can created related dependent accounts for it.
To create a dependent account:
  1. In the PVWA, on the Accounts page, select the target account to which you want to add the dependent account.
  2. On the Account Details page, in the right pane, select the relevant dependency type, and then click Add.
There are following service tabs available to add dependent account(s):
  • Windows Service
  • Scheduled Task
  • IIS Application Pool
  • Windows Registry
  • COM+Application
  • IIS Anonymous User





  1. On the Add Dependent Account page, enter the required information, and then click Save.

How CPM Managing Service Accounts

Here is a good explanation found from Reddit which they are talking about how the process CPM  change service/dependent accounts works. I found it is helpful and copied here for my reference. 


CyberArk has two main offerings for service-type accounts (maybe Three if we consider Conjur separately.) - the "Push" and the "Pull" password options.
  • PUSH - Out of the box, CyberArk can use the CPM to connect to target machines, and update the passwords on certain types of service accounts. For example: Windows Scheduled Tasks (which it can restart after the change), Windows Services, text files, registry files, IIS app users. There are certain limitations here, and risks.
    • For example, if I remember correctly, you can only have 100 of these "usages" per a single managed account.
    • It takes time for the CPM to reach out to each target machine running such a service, something like 3 at a time, so there is a possibility that accounts can get locked, or services can fail.
    • You basically want to use this for non-critical service accounts, or at least service accounts that have some tolerance for how quickly the password is updated in the service account's definition.
  • PULL If you have certain business systems, specific applications which have been built to work with the CyberArk vault, or custom applications you can update, or applications that can get passwords using SOAP calls, then you can use the CyberArk "pull" mechanisms to pull passwords straight from the vault, which are grouped together as "AIM". For the most part it requires a separate license per device that needs these passwords, and you either install a CyberArk service on those devices can talk directly to the Vault, or implement code which can querry the CCP (Central Credential Provider) for a password, whenever the service needs it. The benefit here is that each service runs independently, and they can all be updated concurrently.
Now to answer your other question about the logon accounts. In the case of the "push" mechanism, if you need to change the actual password, but the account cannot change it's own password, you need a reconcile account. If you need to update the new password on the target service (for example on a Windows Scheduled Task), but the account doesn't have the permissions to log into the system and do it, then you need a logon account.













via Blogger https://ift.tt/39BnHIg
July 29, 2020 at 08:16AM CyberArk
1 Comment

CyberArk PSMP (PSM for SSH Proxy) Administration and Troubleshooting

7/27/2020

0 Comments

 
CyberArk PSMP (PSM for SSH Proxy) Administration and Troubleshooting
Here are some administration tasks for PSMP servers.
  • Add Remote SSH User to PSMP server
  • PSMPAPP_ account Authentication Failure and PSMP disconnected


Control PSMPSRV service


/etc/init.d/psmpsrv {start|stop|restart|status} [{psmp|psmpadb}]



Add Remote SSH User to PSMP Server

By default, only root user can log in from console. Other users will trigger PSMP service to log in remote server as show following screenshot.


Here are simple steps to enable a new user to log into PSMP server remotely to do administration work.

1 In the /etc/ssh directory, open the sshd_config configuration file for editing.


2 Add the following parameter to the file:
PSMP_MaintenanceUsers <username>,<username>

This example will allow the following administrative users: user1, all users that end with "user2", all users that starts with "user3" and all users that include "user4".
PSMP_MaintenanceUsers <user1>,<*user2>,<user3*>,<*user4*>


3 Save the changes and close the sshd_config configuration file. 

4 Create a new user and assign it to wheel group
useradd root1
passwd root1
usermod -aG wheel root1

5 Restart the sshd service for these changes to take affect:
/etc/init.d/sshd restart 
5 After logged in with root1, Sudo -i to switch to root account.

Note: https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Administrating-the-PSMP.htm?Highlight=PSMP%20administration


PSMPAPP_ account Authentication Failure and PSMP disconnected





[root@psmp conf]# vi /etc/opt/CARKpsmp/conf/basic_psmpserver.conf
[Main]
PSMPServerVaultFile="/etc/opt/CARKpsmp/vault/vault.ini"
PSMPServerCredFile="/etc/opt/CARKpsmp/vault/psmpappuser.cred"
PSMPServerGWCredFile="/etc/opt/CARKpsmp/vault/psmpgwuser.cred"
LogsFolder="/var/opt/CARKpsmp/logs"
LocalParmsFileFolder="/var/opt/CARKpsmp"
TempFolder="/var/opt/CARKpsmp/temp"
PSMPConfigurationSafe="PVWAConfig"
PSMPConfigurationFolder="Root"
PSMPPVConfigurationFileName="PVConfiguration.xml"
PSMPPoliciesConfigurationFileName="Policies.xml"
PSMPServerId="PSMPServer"
PSMPTempFolder="/var/opt/CARKpsmp/temp"

We will need to reset psmpappuser.cred file and vault psmpapp_psmp password.
C:\CyberArk\Password Vault Web Access\Env>CreateCredFile.exe psmpappuser.cred
Vault Username [mandatory] ==> PSMPAPP_psmp
Vault Password (will be encrypted in credential file) ==> *********
Disable wait for DR synchronization before allowing password change (yes/no) [No
] ==>
External Authentication Facility (LDAP/Radius/No) [No] ==>
Restrict to Application Type [optional] ==>
Restrict to Executable Path [optional] ==>
Restrict to current machine IP (yes/no) [No] ==>
Restrict to current machine hostname (yes/no) [No] ==>
Restrict to OS User name [optional] ==>
Display Restrictions in output file (yes/no) [No] ==>
Use Operating System Protected Storage for credentials file secret (Machine/User
/No) [No] ==>
Command ended successfully

C:\CyberArk\Password Vault Web Access\Env>CreateCredFile.exe psmpgwuser.cred
Vault Username [mandatory] ==> PSMPGW_psmp
Vault Password (will be encrypted in credential file) ==> *********
Disable wait for DR synchronization before allowing password change (yes/no) [No
] ==>
External Authentication Facility (LDAP/Radius/No) [No] ==>
Restrict to Application Type [optional] ==>
Restrict to Executable Path [optional] ==>
Restrict to current machine IP (yes/no) [No] ==>
Restrict to current machine hostname (yes/no) [No] ==>
Restrict to OS User name [optional] ==>
Display Restrictions in output file (yes/no) [No] ==>
Use Operating System Protected Storage for credentials file secret (Machine/User
/No) [No] ==>
Command ended successfully

C:\CyberArk\Password Vault Web Access\Env>

WINSCP to upload those two files to PSMP server to replace those at /etc/opt/CARKpsmp/vault/






PSMP_ADB_psmp suspended




[root@psmp conf]# cat /etc/opt/CARKpsmpadb/conf/basic_psmpadbridge.conf
[Main]
AppProviderParmsSafe="PSMPADBridgeConf"
AppProviderVaultParmsFolder=Root
AppProviderVaultParmsFile="main_psmpadbridge.conf.linux.11.04"
AppProviderVaultFile="/etc/opt/CARKpsmp/vault/vault.ini"
AppProviderCredFile="/etc/opt/CARKpsmpadb/vault/psmpadbridgeserveruser.cred"
LogsFolder="/var/opt/CARKpsmpadb/logs"
LocalParmsFileFolder="/var/opt/CARKpsmpadb"
TempFolder="/var/opt/CARKpsmpadb/tmp"
AdvancedFIPSCryptography="No"
PIMConfigurationSafe="PVWAConfig"
PIMConfigurationFolder="Root"
PIMPVConfigurationFileName="PVConfiguration.xml"
PIMPoliciesConfigurationFileName="Policies.xml"

Activate user PSMP_ADB_psmp and update it password.



C:\CyberArk\Password Vault Web Access\Env>CreateCredFile.exe psmpadbridgeserveru
ser.cred
Vault Username [mandatory] ==> PSMP_ADB_psmp
Vault Password (will be encrypted in credential file) ==> *********
Disable wait for DR synchronization before allowing password change (yes/no) [No
] ==>
External Authentication Facility (LDAP/Radius/No) [No] ==>
Restrict to Application Type [optional] ==>
Restrict to Executable Path [optional] ==>
Restrict to current machine IP (yes/no) [No] ==>
Restrict to current machine hostname (yes/no) [No] ==>
Restrict to OS User name [optional] ==>
Display Restrictions in output file (yes/no) [No] ==>
Use Operating System Protected Storage for credentials file secret (Machine/User
/No) [No] ==>
Command ended successfully


[root@psmp vault]# cp /home/root1/psmpadbridgeserveruser.cred .
cp: overwrite ‘./psmpadbridgeserveruser.cred’? y
[root@psmp vault]# /etc/init.d/psmpsrv restart
Stopping PSM SSH Proxy....
PSM SSH Proxy was stopped successfully.
Starting PSM SSH Proxy...
PSM SSH Proxy was started successfully.
PSMP ADBridge is already stopped.
Starting PSMP ADBridge...
PSMP ADBridge was started successfully.
[root@psmp vault]#


It also can use registration tool to overwrite the environment created in the vault:
https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/PSMP_EnivromentManager.htm
It is recommended to change the default PSMAppUser and PSMPGWUser parameter values to unique values to prevent overwriting previous installations.
 
/opt/CARKpsmp/bin/envmanager "CreateEnv" -AcceptEULA "Y" -CredFile "/tmp/user.cred" -PSMPAppUser "PSMPAppUser_PSMP1" -PSMPGWUser "PSMPGWUser _PSMP1"









via Blogger https://ift.tt/2D81BBh
July 27, 2020 at 01:47PM CyberArk
0 Comments

    Categories

    All
    Architecture
    Blog
    Checkpoint
    Cisco
    Cloud
    CyberArk
    F5
    Fortigate
    Guardium
    Juniper
    Linux
    Network
    Others
    Palo Alto
    Qualys
    Raspberry Pi
    Security
    SIEM
    Software
    Vmware
    VPN
    Wireless

    Archives

    March 2024
    February 2024
    January 2024
    December 2023
    November 2023
    October 2023
    September 2023
    August 2023
    July 2023
    June 2023
    May 2023
    April 2023
    March 2023
    February 2023
    January 2023
    December 2022
    November 2022
    October 2022
    September 2022
    August 2022
    July 2022
    June 2022
    May 2022
    April 2022
    March 2022
    February 2022
    January 2022
    December 2021
    November 2021
    October 2021
    September 2021
    August 2021
    July 2021
    June 2021
    May 2021
    April 2021
    March 2021
    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    October 2019
    September 2019
    June 2019
    July 2018
    May 2018
    December 2017
    August 2017
    April 2017
    March 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015

    Print Page:

    RSS Feed

    Email Subscribe
Powered by Create your own unique website with customizable templates.
  • Blog
  • Sitemap
    • Categories
  • Contact
  • About
  • Resources
  • Tools
  • 51sec.org