PingOne Privilege

Configuring Human Privilege

This section provides guidance for administrators on configuring Human Privilege. Which configuration steps you need depends on the resources your organization uses and how users connect to them. Find your scenario in the following topics, then follow the linked pages in the order shown.

If you’re securing AI agent access instead of human access, see Configuring Agent Privilege. The multi-factor authentication and User Vault topics in this section also apply to Agent Privilege deployments.

Access cloud resources directly

Choose this path if your users need just-in-time (JIT) access to cloud resources, such as AWS, Azure, or Google Cloud. No gateway is required.

Access Kubernetes clusters

Choose this path if your users need just-in-time access to Kubernetes clusters. Onboard the cloud account first; the Kubernetes setup depends on it.

If the cluster is in a private VPC with no inbound internet access, also deploy a gateway or relay. Learn more in Gateways.

Access on-premise servers and databases

Choose this path if your users need access to resources on a private network, such as on-premise servers, databases, or applications. These resources are reachable only through a gateway, so configure the network infrastructure first.

Add MFA challenges

Choose this path if you want to challenge users with multi-factor authentication (MFA) when they connect to PingOne Privilege or escalate privileges.