Tags and data classification in audit log

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
As part of the many incident on file transfer solution (moveit,...), it's great that nextcloud has already some tagging+data classification and audit log capacity but those are disjoined.
Meaning if I review the audit logs of file transfers, I currently have no data classification, user tags, system tags or else visible in the log.
Example from /var/snap/nextcloud/common/nextcloud/data/audit.log:

{"reqId":"3HpGp1uTpcxGc43T18fr","level":1,"time":"2023-01-02T12:03:45+00:00","remoteAddr":"x.y.z.1","user":"USEREMAIL","app":"admin_audit","method":"GET","url":"/nextcloud/index.php/apps/files/ajax/d
ownload.php?dir=DIR3&files=05&downloadStartSecret=XYZ","message":"File accessed: \"NEXTCLOUD_FILEPATH\"","userAgent":"Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox
/112.0","version":"25.0.6.1","data":{"app":"admin_audit"}}

Describe the solution you'd like
I would want audit log to include information when available, including data classifications and user tags.
system tags would probably be nice.
In some environment data classification would probably rely on custom user tags (like FIRST TLP https://www.first.org/tlp/) and some extras like phi, pii, internal, customer or whatever.
There may be some case where we don't want tags to be in audit log. Not sure if want to have a configuration setting to say what should be or not be in audit.log

Feature is supporting security and privacy reporting, along compliance and security incident response.

Describe alternatives you've considered
At this point, I believe that one would need to extract tags from database and merge with audit logs manually to get a clear picture of transfer per classification type.
Or enforce a folder structure that makes classification easy to recognize and parse.
Or maybe some reporting option with or without plugin.

Additional context
N/A

Start by reviewing the admin_audit audit.log example and how file-transfer events are represented. Determine which data classifications, user tags, and system tags should be included and whether configuration is needed to control them. Done means the audit log exposes the agreed metadata without violating the stated privacy requirements.