chapter 10 Flashcards

1
Q

Privileged Session Management
Provides 3 Main Benefits:
1. (blank) - separate endpoints from critical target systems to prevent lateral movement
2. (blank) - detect and track suspicious activities in privileged sessions and events in real time
3. (blank) - support forensic analysis and audit with detailed records of privileged activity

A

isolation

monitoring

recording

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

When we talk about PSM, the (blank), we are usually referring to the PSM installed on a Windows server.
You can think of this as the “Universal PSM” because you can
connect through it practically from
any device to any device.

A

Privileged Session Manager

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The (blank) enables
organizations to secure,
control, and monitor privileged access to network devices
* It creates detailed session audits and video recordings of all IT administrator privileged
sessions on remote machines
* Sessions on the target
systems are fully isolated and the privileged account credentials are never exposed to the end-users or their client
applications and devices

A

PSM

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

what is this?

  1. Logon through PVWA
  2. Connect to PSM using RDP/TLS
  3. Fetch credential from Vault
  4. Connect using native protocols
  5. Logs forwarded to SIEM and PTA
  6. Store session recording
A

psm flow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Enable the PSM in the (blank) Policy for all platforms or for
specific platforms by use of exceptions

A

master

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

By default, Platforms are associated
with the first installed PSM server

A

blank

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

(blank) - define the
configuration settings for using a given third
-party client to
connect to a target platform.
A few common ones are: * SQLPlus
* RDP
* Putty
* WinSCP

A

Connection Components
(aka Connectors)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Connection Components
(aka Connectors)

There are many connection components available out of the box
* Additional connection
components can be found in the (blank)
* Organizations can also
build and add custom
connection components to the PAM solution

A

CyberArk
Marketplace

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

To enable the use of a particular third-party client to connect to a
given account, the appropriate Connection Component needs
to be assigned to the (blank) that manages that account

A

Platform

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

The new interface accelerates and simplifies Vault administration by allowing admins to import (blank) connectors and link them to Platforms, all from one
location

A

psm

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

The (blank) framework facilitates the creation of custom connection components using a (relatively) simple, freeware programming language called AutoIT

A

Universal Connector

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

With an (blank),
users can connect securely to any machine supported by the
PSM if they know the password
* Main use cases:
⎼ Connecting with accounts that are not stored in the CyberArk
Vault
⎼ Connecting with personal accounts
* Provides all the benefits of PSM: isolation, monitoring, and recording

A

Ad-Hoc Connection

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

how to enable ad-hox connections?

The (blank) Platform must be activated
* Privileged session
monitoring and isolation
must be enabled for the
PSM Secure Connect
platform. This can be done either globally or via an exception to the Master policy

A

PSM Secure Connect

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

when launching an ad-hoc connections the Users will need to specify all the account details when they connect:
* The (blank) they want to use on the PSM
* Target system Address
* Username
* Password, etc.

A

client

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Many organizations block RDP client connections from end-users’ machines for security
reasons or regulatory requirements.
* RDP is a Microsoft protocol, so in order to use it in Linux, Unix, or MAC environments,
users must install a 3rd-party client in order to connect to the PSM.
* The HTML5 Gateway tunnels the session between the end user and the PSM proxy
machine using a secure WebSocket protocol (port 443). This solution eliminates the need
to open an RDP connection from the end user’s machine. Instead, the end user only
requires a web browser to establish a connection to a remote machine through PSM.
* Secure access through HTML5 requires integrating an HTML5 gateway on a Linux server
(can be co-hosted with PSM for SSH). The Gateway is based on Apache Guacamole.

A

blank

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

HTML5 Gateway: Flow

A
  1. Logon through PVWA and click on Connect
  2. Connect to HTML5 GW using WebSocket
  3. Connect to PSM using RDP
  4. Fetch credential from Vault
  5. Connect using native protocols
  6. Logs forwarded to SIEM and PTA
  7. Store session recording
17
Q

The HTML5 GW is enabled at the
system level for each (blank) server

18
Q

Users can be given the option to connect either an HTML5-based or RDP-file connection method when connecting to the
remote server
* This setting is applied at the (blank) level

A

Connection Component

19
Q
  • Users connect directly from their desktops with an RDP-compliant client to the PSM, which then connects to the target host using the protocol appropriate to that host: SSH, RDP, etc.
  • There is no need to go through the PVWA.
  • Users can launch the RDP client and sign in into CyberArk using single- or multi-factor authentication (for example, LDAP with RADIUS).
    ⎼ The RDP client application must include the ability to configure run “Start Program”
    for the RDP connections.
    ⎼ Connections can be made from Unix / Linux / Mac / Windows end user machines.
  • PSM continues to provide complete isolation of the target systems, ensuring
    that privileged credentials never reach users or their devices
20
Q

PSM for Windows: Flow

A
  1. Connect to PSM using RDP/TLS
  2. Fetch credential from Vault
  3. Connect using native protocols
  4. Logs forwarded to SIEM and PTA
  5. Store session recording
21
Q

RDP Client
Settings

A

PSM IP
* Vault user
* Activate Start Program
* Program path:
⎼ Privileged Account name
⎼ Target address
⎼ Connection Component

22
Q

Preconfigured
RDP Files

You can also configure
individual RDP files to
connect through the (blank)
* It is possible to configure connections with or without
providing the target system details

23
Q

PSM for SSH: Overview

  • The average enterprise manages hundreds
    of Unix servers and network devices
  • Systems are usually critical, but access to
    them is uncontrolled
  • Network and Unix teams are reluctant to
    change their existing workflows and tool sets
  • PSM for SSH (previously PSM SSH Proxy or
    PSMP) is designed to provide a native
    Unix/Linux user experience when connecting
    to any SSH target system
24
Q

PSM for SSH
Client Settings

The connection settings for PSM for SSH resemble those of PSM for Windows.
* Connections are not
launched via the (blank),
but through a special
connection string.

25
PSM for SSH: Flow
1. User opens SSH session to the PSM server 2. PSM retrieves privileged account password from the vault 3. Open SSH session to the target using the privileged account 4. Logs forwarded to SIEM and PTA 5. Store SSH session audit
26