Mr.PlanB Logo

    Newsletter

    Subscribe our newsletter

    Get new infrastructure guides, comparison reports, and migration notes in your inbox.

    Infrastructure notes, guides, and new tools. Unsubscribe anytime.

    Back to Blog
    Proxmox
    Compliance
    Audit
    Sysadmin

    Proxmox Audit Trail in 2026: Who Changed /etc/pve, and What Auditors Actually Ask For

    November 18, 2026
    6 min read

    Proxmox VE has no built-in audit log of configuration changes. To show an auditor who changed /etc/pve and when, you combine three things: the pveproxy access log on every node for the user and time, a versioned copy of /etc/pve for the old and new values, and your change tickets for the approval. Each source covers a different part of the question, and two gaps remain.

    What auditors ask to see

    Whether it is ISO 27001, SOC 2 or a customer security questionnaire, the auditor asks for a control, not a product. They want to see who made a change, what changed, when it happened, and that someone approved it first. Any tool that produces that evidence is fine; a SIEM plus file integrity monitoring is fine too, if it covers the points above.

    On Proxmox the hard part is "what changed". If someone raises the memory of a VM or adds a bridge in the web interface, the change applies at once and the config file shows only the new value. The approval part sits outside Proxmox anyway: a ticket or change record, as in my post on an auditable change management process.

    The Proxmox evidence map

    The Proxmox cluster file system (pmxcfs) is what you see under /etc/pve. The Proxmox admin guide describes it as a database-driven file system, stored in SQLite at /var/lib/pve-cluster/config.db, replicated to all cluster nodes in real time using corosync, with a size limit of 128 MiB. It holds the current configuration and nothing else. This is where each piece of evidence lives:

    SourceWhere it livesWhoWhenOld/new valuesGap
    /etc/pve (pmxcfs)replicated to all nodes, SQLite at /var/lib/pve-cluster/config.dbnofile times onlycurrent values onlyno history, no actor
    /var/log/pveproxy/access.logper node: the node that served the GUI or API sessionyesyesno (method and API path only)no values; root shell edits never appear
    Task log (pvesh get /cluster/tasks)cluster-wide listyesyesnoonly operations that create tasks (start, backup, migrate)
    Versioned copy of /etc/pve (git commit on a timer)wherever you keep itnocommit timeyes (diff)misses a change and revert inside one interval; user has to be matched from access.log

    The task log is the first place people look, and it misses most config edits. On the Proxmox forum in October 2026 a long-time member put it plainly: operations that result in tasks can be listed with pvesh get /cluster/tasks, and changes that don't create a task are not logged explicitly.

    The access log: who and when

    Every change in the web interface is an API call. pveproxy writes each request to /var/log/pveproxy/access.log on the node that served the session, with the user, the time, the HTTP method and the API path. A reply in the same forum thread gives the filter for changes only:

    grep -E '"(POST|PUT|DELETE) ' /var/log/pveproxy/access.log
    

    A VM config change shows up as a request to /api2/json/nodes/<node>/qemu/<vmid>/config. That tells you who touched which VM and when. It does not tell you whether they changed memory, a VLAN tag or a disk, because the log does not record the new values.

    The catch in a cluster: the log is per node. If one admin works through node1 and another through node2, the evidence is split across two files. Ship the access log from every node to your log server, or you will be collecting it by hand on audit day. pmxcfs replicates /etc/pve, so one node's copy covers the configuration; the access logs do not replicate.

    A versioned copy of /etc/pve: what changed

    For the old and new values, copy /etc/pve on a timer into a directory outside the cluster file system and commit it to git. Don't put the repository inside /etc/pve: the admin guide says pmxcfs does not support symbolic links and does not allow renaming non-empty directories, and only root can write there (group www-data can read).

    The diff then shows the change, for example on a VM config:

    --- a/nodes/pve-01/qemu-server/104.conf
    +++ b/nodes/pve-01/qemu-server/104.conf
    -cores: 2
    +cores: 4
    

    Put the commit next to the access log line from the same time window and you have who, when and what.

    The two gaps to tell the auditor about

    The first gap is the interval. A copy taken every hour, or every five minutes, shows the state at that moment. If someone changes a firewall rule and puts it back inside one interval, git sees nothing. The access log still shows two requests, so you know something happened, but not what.

    The second gap is the root shell. An edit made with a text editor on a node writes to /etc/pve directly and never passes through pveproxy. Your git copy will show the change, and no access log line will say who made it. You can narrow this with SSH logs and by giving people named accounts in the web interface instead of shared root, but on stock Proxmox the change itself carries no user.

    Say both gaps out loud in the audit. Auditors deal with known limits and a compensating control (ticket review, SSH session logs) much better than with a gap they find themselves.

    Where Proxmox itself stands

    In January 2026 a contributor opened a thread on the pve-devel mailing list about building an auditing system, referring to Proxmox bug 4244. The post lists what regulated users are asked for under PCI, NIST 800-53 and HIPAA: success and failure auditing for elevated privileges and changes to users, groups, domains and ACLs, in a standard log format. The ideas include a hook in the API request handler and a separate daemon named pveauditd. It is a design discussion. I don't know if or when anything ships, so plan with what exists today.

    What I would run

    Keep the nodes lean and move the evidence off them. Forward /var/log/pveproxy/access.log from every node to a syslog or SIEM host, so the record also sits outside the node it describes. Run the /etc/pve copy and commit on a short timer, from a job you can show the auditor. Give every admin a named Proxmox account and keep shared root for emergencies, so most changes go through pveproxy with a name on them. Then tie each change to a ticket.

    If you are new to running Proxmox in production, my book Proxmox for Everyone covers clusters, backups and permissions step by step.

    If an audit or a customer questionnaire is coming and you want someone to check your setup first, my written second opinion is $149 for a 2-page assessment of what is fine, what will bite and what to change first.

    Frequently Asked Questions

    Does Proxmox VE have a built-in audit log for configuration changes?

    No. Proxmox VE keeps the current configuration in /etc/pve, logs API requests per node in /var/log/pveproxy/access.log and lists tasks, but nothing records the old and new values of a config change. A pve-devel thread from January 2026 discusses an auditing system; it is a design discussion, not a shipped feature.

    Where are Proxmox GUI and API actions recorded?

    pveproxy writes each API request to /var/log/pveproxy/access.log on the node that served the session, with the user, time, method and API path. Operations that create tasks (start, backup, migrate) also appear in the cluster task list, which pvesh get /cluster/tasks prints.

    How do I see what a Proxmox config change actually changed?

    Keep a versioned copy of /etc/pve outside the cluster file system, for example a timer that copies it into a git repository and commits. The diff gives the old and new values; the access log entry at the same time gives the user.

    Why do root shell edits not show a user in the Proxmox logs?

    An edit made from a root shell writes to /etc/pve directly and never goes through pveproxy, so there is no access log line for it. A versioned copy of /etc/pve still shows the change, with no user attached.