Mercurial > prosody-modules
view mod_audit/README.md @ 5016:964de9997552
mod_admin_blocklist: Fix traceback due to misplaced parenthesis
get_jids_with_role() throws an exception when 'host' is nil since
Prosody trunk rev 7ca5645f46cd
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sat, 27 Aug 2022 15:39:38 +0200 |
parents | 530d116b7f68 |
children | dc058fcc3fe3 |
line wrap: on
line source
--- summary: Audit Logging rockspec: {} ... This module provides infrastructure for audit logging inside Prosody. ## What is audit logging? Audit logs will contain security sensitive events, both for server-wide incidents as well as user-specific. This module, however, only provides the infrastructure for audit logging. It does not, by itself, generate such logs. For that, other modules, such as `mod_audit_auth` or `mod_audit_register` need to be loaded. ## A note on privacy Audit logging is intended to ensure the security of a system. As such, its contents are often at the same time highly sensitive (containing user names and IP addresses, for instance) and allowed to be stored under common privacy regulations. Before using these modules, you may want to ensure that you are legally allowed to store the data for the amount of time these modules will store it. Note that it is currently not possible to store different event types with different expiration times.