[GEN-1859] Audit logging system with enums and db migrations

[Jossec101]

Stacked PRs:

• [GEN-1859] Add audit logging for authentication events #473
• [GEN-1859] Audit + paginated retrieval for wallet withdrawal requests #472
• [GEN-1859] Audit logging to user management, wallet setup, swaps #470
• [GEN-1859] Audit logging to API tokens, nodes and channel operations #469
• [GEN-1859] Audit trail page with comprehensive filtering and search #468
• [GEN-1859] Add audit log cleanup job with configurable retention policy #467
• ->[GEN-1859] Audit logging system with enums and db migrations #465

---

[GEN-1859] Audit logging system with enums and db migrations

• Add AuditLog model with tracking for user actions and system events
• Define AuditActionType, AuditEventType, and AuditObjectType enums
• Include Entity Framework configuration and database migrations
• Support for user identification, IP tracking, and detailed event logging

[RodriFS]

flawless

[imclvr]

@Jossec101 one question, are we gonna use a separate DB instance for storing audit logs, or are we going to use same NG Postgres?

I think that ideally this should be apart, so it could have its own RBAC, logging and in case main DB is compromised, this one is isolated and hopefully not affected.

[Jossec101]

@Jossec101 one question, are we gonna use a separate DB instance for storing audit logs, or are we going to use same NG Postgres?

I think that ideally this should be apart, so it could have its own RBAC, logging and in case main DB is compromised, this one is isolated and hopefully not affected.

I dont think we need that complexity right now, the main use case is to capture logs via stdout and use a SIEM, the audit logs view + db is for nodeguard standalone as OSS project (easy audit trails) or for non technical users such as Finance Managers.