Overview
The Audit Logs system provides a comprehensive, immutable record of all platform administrative actions. This is essential for security monitoring, regulatory compliance, and investigating issues.Accessing Audit Logs
Navigate to/admin/audit-logs to view the audit trail:
Audit Log Schema
Audit logs capture detailed information about each action:Logged Actions
All administrative actions are automatically logged:Dashboard Access
User Management
KYC Actions
KYC_APPROVEDKYC_REJECTEDKYC_REQUIRES_UPDATEVIEWED_KYC_MANAGEMENT
Revenue Management
Security Management
Blue Ticket Verification
Logging Implementation
The audit logging function is comprehensive:Audit Statistics
The audit logs page displays comprehensive statistics:Total Actions (30 days)
Active Admins
Last 24 Hours
Failed Actions
Action Breakdown
Recent Activity Table
The main audit log table displays:Dashboard Integration
Recent security events appear on the admin dashboard:Compliance & Retention
Audit logs are designed for regulatory compliance:Key Compliance Features
- Immutable Records: Logs cannot be edited or deleted
- 7+ Year Retention: Minimum retention period for regulatory requirements
- Complete Audit Trail: Every admin action is logged
- Timestamp Accuracy: UTC timestamps with timezone support
- IP Tracking: IPv6 support for complete address logging
- Error Logging: Failed actions are captured with error messages
Export Functionality
- External auditing
- Compliance reporting
- Long-term archival
- Data analysis
Metadata Tracking
Detailed context is stored in the metadata field:- Related entity IDs
- Previous and new states
- Rejection/approval reasons
- Custom action-specific data
Security Monitoring
Use audit logs to detect:-
Unusual Activity Patterns
- Multiple failed actions from same admin
- Actions outside normal working hours
- Rapid succession of high-risk actions
-
Unauthorized Access Attempts
- Failed authentication events
- Access from unexpected IP addresses
- Geographic anomalies
-
Policy Violations
- Actions without proper justification
- Suspicious patterns in KYC approvals
- Unusual data access patterns
Error Handling
The logging system is resilient:- Primary Log Attempt: Write to database
- Error Capture: If primary fails, log the error itself
- Console Fallback: Critical errors logged to console
- Non-Blocking: Logging failures donβt break admin operations
Best Practices
- Regular Review: Check audit logs daily for anomalies
- Failed Action Investigation: Immediately investigate failed actions
- Export for Compliance: Regular exports for external auditing
- Pattern Recognition: Monitor for unusual activity patterns
- Retention Compliance: Ensure 7-year minimum retention
- Access Control: Limit audit log access to senior administrators
- Correlation: Cross-reference with application logs for investigation