audit-backend

Create a tamper-proof audit trail by configuring an EF Core SaveChangesInterceptor to automatically generate append-only, immutable AuditEntry logs for tracked data changes. This enforces UTC timestamps and resilient, non-blocking writes for compliance.

Capture HTTP request context for compliance logging by implementing audit middleware that records user identity, IP addresses, and correlation IDs alongside user actions. This provides governance reviews with the necessary forensic request details.

Yes, the .NET audit trail implementation supports GDPR, SOC2, and HIPAA compliance requirements by enforcing immutable, append-only records, capturing user actions, and redacting sensitive fields like passwords and tokens to protect PII.

The best way to redact sensitive fields in .NET audit logs is to apply built-in redaction rules that mask passwords, tokens, and PII before writing to the append-only AuditEntry storage, ensuring sensitive data is excluded from compliance records.

Yes, you can use EF Core interceptors for non-blocking audit trail writes in .NET. The implementation features resilient, non-blocking writes that ensure audit logging does not degrade application performance during data changes.