In a discussion about auditing moderator/admin activity related to user data (specifically email and IP address), aram seeks to understand whether actions like viewing user data via User Admin or exporting user lists are logged. RGJ adds that data explorer queries and database backups are also potential vectors for accessing user data, cautioning that if trust in moderators is lacking, auditing alone won’t solve deeper governance issues. aram clarifies that trust and audit are separate concerns and notes the user_exports table is empty, suspecting rows are purged over time. simon confirms that exporting user lists does generate a log entry under Staff Actions with action name “export entity” and subject like “user_list” or “user_archive.” not-ethan provides a direct link to filter staff action logs for user list exports, noting that if no exports occurred, the log would be empty. RGJ reiterates that since admins can backup and restore databases offline — potentially erasing audit trails — no audit system can offer complete assurance, and may even create a false sense of security. The thread underscores the limitations of logging systems when high-privilege users have full database access.
I’m looking for any and all information about how we might audit moderator & admin activity associated with user data (in particular, email and IP Address). I believe there are at least 2 activities to consider here (but interested to understand if there are others):
show email/ip address via User Admin
exporting a list of users (which would include these 2 fields).
My question is: is there any auditing/logging for these 2 activities (and other relevant actions)? I’ve found Staff Activities perhaps covers the first one (are there other/better sources?), but having trouble finding audit data on the second.
Trust and audit requirements are 2 different things
Any guidance on the queries to run? I’ve found that the the user_exports table is unfortunately empty (I’m guessing rows are purged here after some time?).
This will create an entry on the Staff Actions page. The action will be set to “export entity” and the subject set to what was exported, for example, “user_list” or “user_archive.”
Given the possibility (at least for an admin) to backup/restore, which allows for inspecting the database and erasing any traces offline, an audit will never give you a complete picture and maybe even a false sense of security.