Skip to main content
Audit logs are centrally stored and retained. All security-relevant events (authentication, authorization, admin actions, API calls, configuration changes) are written as structured logs with timestamp, user/service ID, source IP, and action/result.
Audit logs are centrally stored and retained. All security-relevant events (authentication, authorization, admin actions, API calls, configuration changes) are written as structured logs with timestamp, user/service ID, source IP, and action/result. Logs are stored in a centralized logging stack separate from production databases and retained for at least three years. Logs are append-only; application users and standard admins cannot modify or delete them. Access to the log platform is restricted to designated security personnel with MFA. Logs are streamed in real time to the centralized SIEM for correlation, alerting, and forensic analysis. Learn more: Xoxoday Help Centre — Technical requirement

Are audit logs reviewed on a regular basis for security events?

Security-relevant events, including individual user traceability (date, time, user ID), both successful and failed login attempts, activities by…

Are audit trails and logs maintained for network/system/application events...

Audit trails/logs maintained for network, system, and application events including authentication, access, configuration changes, and admin actions…