What a Proxmox access audit checks

Access to a Proxmox cluster comes through user accounts, API tokens and the permissions attached to them. An audit answers four questions: who has an account, who has two-factor turned on, which API tokens exist and how risky they are, and who holds administrator rights. The Proxmox user management documentation describes all of these in detail.

  1. Userspveum user list
  2. Two-factorpvesh get /access/tfa
  3. API tokenspveum user token list
  4. Admin rightspveum acl list
  5. Loginsjournalctl -u pvedaemon
Five checks that together show who and what can get into Proxmox.

Step 1: List every user

pveum user list --full 1

Look at each account's enable, expire, groups and tokens fields. Accounts nobody uses should be disabled, not left active:

pveum user modify someone@pve --enable 0

Step 2: Find accounts without two-factor

pvesh get /access/tfa

This lists users who have two-factor set up. Any user from step 1 who is not in this list has none. An empty result means nobody has it. You can turn it on in the web interface under Datacenter, then Permissions, then Two Factor.

Step 3: Review API tokens

pveum user token list root@pam
pveum user token list someone@pve

Each token shows tokenid, expire and privsep. Two values matter:

When you create a token, set both on purpose. This example expires in 90 days:

pveum user token add someone@pve reports --privsep 1 --expire $(date -d '+90 days' +%s)

Step 4: Check who has admin rights

pveum acl list

Look for the Administrator role on the path /: that is the whole cluster. Reporting and monitoring tools rarely need more than the built-in PVEAuditor role, which is read-only.

Step 5: Look at logins

journalctl -u pvedaemon --since "7 days ago" | grep -i "authentication failure"
journalctl -u pvedaemon --since "7 days ago" | grep -i "successful auth for user"

A few failures are normal. Many from one address, or a successful login from somewhere you do not recognize, deserve attention.

How often to repeat it

Weekly is a good rhythm for a cluster that other people or tools use, and any time you add a user, create a token or change permissions. Done by hand, that is easy to forget.

Doing it every week without remembering

Pontavia's Access Audit ($49) is an n8n workflow that sends a weekly report of who can get into your Proxmox: accounts without two-factor, tokens that never expire, tokens without privilege separation, admin rights on the whole cluster, root and failed logins. It checks daily for new high-risk changes and alerts you when something new and risky appears. It uses a read-only token. It is also in the $89 Ops 3-Pack with the Patch & Reboot Report and the VM Lease Manager.

Frequently asked questions

What does privilege separation mean for a Proxmox API token?

With privilege separation on (the default), the token only has the permissions you assign to it. With it off, the token inherits every permission of the user it belongs to.

What does an expire value of 0 mean on a Proxmox token?

It means the token never expires. That is convenient but risky, so set an expiry on tokens you can easily renew.

Should tools use the root@pam account for the Proxmox API?

It is safer to create a dedicated user and a token with only the permissions the tool needs. Reporting tools usually only need the read-only PVEAuditor role.

Where do I turn on two-factor authentication in Proxmox?

In the web interface under Datacenter, then Permissions, then Two Factor. Each user adds their own second factor.

Questions about your own setup? Send a message or book a free 15-minute call.