Just-In-Time Permission Elevation

A Just-In-Time Permission Elevation option is designed to promote increased security using the principle of no standing trust.

This design also limits the time a privileged account exists on a critical system, especially with enabled special access.

The goal is not just about limiting time, but to have a zero standing privilege strategy on users and servers.

Just-In-Time (JIT) Permission Elevation helps customers implement these strategies and reduce the number of privileged accounts in their network and control access to active privileged accounts.

Prerequisites:

Just-In-Time Permission Elevation is supported ONLY for Windows Hosts.

Create Just-In-Time Permission Elevation Record Type

Step 1. Create a new PAM record

  1. Login to PAM as a System Administrator.

  2. Navigate to Administration > Record Types.

  3. Click on the New Record Type button.

  4. Enter a unique name for this new record type, select in the first field: Session Manager > RDP. Leave the second field Hidden Field unchecked (blank).

  5. Click Save in the top right corner.

  6. JIT-Permission-Elevation.png

Step 2. Add Just-In-Time (JIT) Record type

The fields of this Just-In-Time (JIT) Record type will need to be added.

  1. Click the Add Field button towards the bottom of this page and add the minimum required fields: Host, Port, User and Password.

    If other fields for the Just-In-Time (JIT) record type are required per your configuration, please also add those fields as well during this step.

    JIT-Permission-Elevation2.png

    JIT-Permission-Elevation3.png

    JIT-Permission-Elevation4.png

    JIT-Permission-Elevation5.png

  2. As a minimum requirement now the record type should look as below:JIT-Permission-Elevation6.png

Step 3. Add Tasks

  1. Next, click on the Tasks button to add the required tasks to perform the Permission Elevation against the host.

  2. Click Add Task and add the following tasks:

    • Script: Windows Local Account Permission Elevation Post-Access with Policy: After Expire

    • Script: Windows Local Account Permission Elevation Pre-Access with Policy: After Approval

  3. Once added the tasks page should now be set as shown below:

  4. JIT-Permission-Elevation7.png

Step 4. Create your record

  1. Navigate to a location in the Records vault where you wish to create the record and select Add Record > Windows Host JIT Permission Elevation.

  2. Use this guidance to create your record:

    Name enter a name for your record
    Description *optionally, enter a description for your record
    Host enter the host for the endpoint where the Permission Elevation will be required
    Port enter the port that will be used for connectivity
    User enter the username that will get Permissions Elevated
    Password enter the password of the user
  3. Click Save and Return.

Step 5. Configure the Task

Configure the Task that performs the Permission Elevation process.

  1. In your new created record, click Manage > Tasks.

  2. For the Shadow Account, select an existing record that contains the credentials of an account that can assign and remove user roles on this endpoint.

    For example, in a Windows domain, this could be a record that contains the credentials of a Domain Administrator account.

    • read-only: if the Shadow Account field is read-only, that means it is set to inherit this Shadow Account from the record type. In this situation, you will need to navigate to Administrator > Record Types and add this Shadow Account directly to the Tasks list of this type. This will require your System Administrator account again. Alternatively, you can click the Make Unique button to break inheritance from the Record Type.

    • read/write: if the Shadow Account field is read/write enabled, then enter the name of the record that contains the credentials of an account that can create local accounts on this endpoint.

  3. Once you have the Shadow Account configured, save your change and return to the record.

Step 6. Configure the Workflow

Next, configure the Workflow, whose approval and subsequent expiration, will trigger the creation and ultimate removal of the Permission Elevation.

Here is the help article about Workflows as well as a table of contents on the right-hand side about other Workflow related knowledge articles.

  1. In the Record field select Manage > Workflows to configure a workflow binding.

  2. On the Workflow Bindings page, you will create a new workflow binding that will be used to request access and once approved, the permission of the user in the record will get elevated to Administrator on the end point host.

  3. Create the Workflow Binding as needed and click the Save button to complete the process.

  4. That completes the configuration of the Just-In-Time Permission Elevation process.

    In the next section, we will illustrate the User experience from workflow request through the workflow expiration when the Permission Elevation is removed from the host.

The Just-In-Time Permission Elevation Process

  1. Login to PAM with the user account that was bound by the workflow created in the previous section.

  2. Navigate to this Ephemeral Account record and click the Request Connect button.

  3. Fill out the request access form as required and submit it when completed.

    During testing, we would recommend requesting a short amount of time (i.e. 5 minutes) so that you do not have to wait too long for the workflow to eventually expire.

  4. If the submitted workflow was not configured for automatic approval, Approve the submitted request to continue.

  5. Once approved, PAM will begin the Permission Elevation process. Depending on the PAM queue, this process may take a few seconds or a few minutes to complete. You can follow the process by monitoring the Job History tab of this record.

  6. After the Permission Elevation is successfully completed, the user’s Connect Requested button will change to Connect indicating that the user may now connect to the Host with the Permission Elevation as an Administrator on the host.

  7. Click Connect to create your remote session. The User on the Record which is used to connect to the host is now an Administrator.

    JIT-Permission-Elevation8.png

  8. Finally, after the workflow’s approved time expires PAM will execute the task to remove the Permission Elevation of Record User. The PAM user’s Connect button will change back to Request Connect and the Permission Elevation on the host will be removed.

    JIT-Permission-Elevation9.png