New Capability: Privileged Task Automation!

Description

:bangbang: SailPoint Privileged Task Automation helps organizations enhance IT operations’ efficiency, security and governance by automating and delegating the execution of repeatable privileged tasks.​

Privileged Task Automation enables your organization to:

  • Automate complex IT and privileged processes across systems
  • Reduce the need for specialized technical knowledge and manual intervention.
  • Enhance security by removing standing privileges.

Problem

Common privileged tasks performed by users require access to a credential or endpoint to complete the task. This can introduce human error and increase risks to your organization. Organizations may wish to automate common privileged tasks as a way to reduce risks and improve efficiency.

Solution

Privileged Task Automation helps organizations enhance IT operations’ efficiency, security and governance by automating and delegating the execution of repeatable privileged tasks with the following new capabilities:

  • Utilizes Identity Security Cloud’s (ISC) Workflows and Forms Engine
  • Integrates with ISC’s Credential Provider to retrieve secrets when Tasks are executed
  • New Privileged Task Automation specific out-of-the-box Workflow templates
  • Introduces the Interactive Trigger, Interactive Form, Interactive Message, Active Directory Action and Windows Server Action in Workflows.
  • Introduces Launchers and Launchpad where Tasks are executed by non-admin users
  • Uses ISC’s Entitlement model to enable built-in Governance
  • Introduces the Privileged Gateway which is a new type of virtual appliance that enables Privileged Tasks to interact with on premises and SaaS targets.

Interactive Click-through Demo

Click to explore: Privileged Task Automation

Who is affected?

Privileged Task Automation is available for Identity Security Cloud Business and Business Plus customers.

Action Required

Before using Privileged Task Automation, a Privileged Gateway needs to be deployed. The Privileged Gateway is a new type of virtual appliance that enables Privileged Tasks to interact with on premises and SaaS targets. Also, Privileged Task Automation uses Identity Security Cloud’s Credential Provider capability. Privileged Tasks use the Credential Provider to access secrets when they are launched.

Important Dates

Privileged Task Automation will begin rolling out to customer tenants mid-October, 2024.

Additional Resources

Privilege Task Automation Documentation

4 Likes

Hello @joutlaw, this feature was announced for Mid-October but we still not have it on our sandbox environment (at least). When is deployement planned ?

1 Like

Is there a plan/schedule to implement additional credential providers, such as Delinia?

@joutlaw
Are Launchers available to all license models including Standard?
I do see them available to use (in a Standard tenant), but it’s unclear if it’s included.

All Suites customers will have access to the Interactive Trigger and Launchers.

Privileged Task Automation specific Actions (currently Active Directory and Windows Server) and the Privileged Gateway are only available in Business and Business Plus Suites.

1 Like

Delinea Cloud will be the first one to be supported. Tentatively planned for Q1 25 and then followed by Delinea On-prem.

1 Like

Privileged Task Automation should be able to all Business and Business Plus Suites customers as of 11/19/2024.

@joutlaw Can you please share the sample workflow JSON (including the launcher details) that was used in this initeractive demo?

Hi,

Can you please guide me to the documentation around enabling debug logs for PAG? I enabled it in the VA screen but don’t seem to get any additional information on the error that I am debugging.

Thanks!

Hello, i think this is very useful, but is it possible to use this capability with a default cluster?
we have an AD connected and i am not sure why do we need to have 2 clusters connected to the same VA, one for communications and the other one for the PTA feature.

Regards,
Pablo

HI Pablo,
I had the same scenario and did not want to mess up my AD and AAD connected VA but does not look like we can use the same VA for both purpose as mentioned in this post.