Hi Martin,
Using event 4672 I don't know if it is the best option, but I do think it is a good option.
According to Microsoft documentation: https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4672
Event Description:
This event generates for new account logons if any of the following sensitive privileges are assigned to the new logon session:
SeTcbPrivilege - Act as part of the operating system
SeBackupPrivilege - Back up files and directories
SeCreateTokenPrivilege - Create a token object
SeDebugPrivilege - Debug programs
SeEnableDelegationPrivilege - Enable computer and user accounts to be trusted for delegation
SeAuditPrivilege - Generate security audits
SeImpersonatePrivilege - Impersonate a client after authentication
SeLoadDriverPrivilege - Load and unload device drivers
SeSecurityPrivilege - Manage auditing and security log
SeSystemEnvironmentPrivilege - Modify firmware environment values
SeAssignPrimaryTokenPrivilege - Replace a process-level token
SeRestorePrivilege - Restore files and directories,
SeTakeOwnershipPrivilege - Take ownership of files or other objects
An example event:
LogName=Security