audit-backend

Adds immutable, append-only auditing to .NET backends via EF Core interceptors and HTTP middleware.

Updated Mar 28, 2026

Search Tags:#security #logging #audit #compliance #dotnet #audit-trail #ef-core

Ready to run

npx skills add https://github.com/congiuluc/my-awesome-copilot --skill audit-backend

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-backend
Source: https://github.com/congiuluc/my-awesome-copilot/tree/main/skills/audit-backend
Command: npx skills add https://github.com/congiuluc/my-awesome-copilot --skill audit-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Immutable, tamper-resistant auditing protects data integrity and supports regulatory compliance by recording who performed what action and when. It enables governance reviews and forensic analysis across systems.

Core Features & Use Cases

AuditEntry model and append-only storage for immutable records.
EF Core SaveChangesInterceptor automatically creates audit logs for tracked changes.
Audit middleware captures HTTP request context (IP, correlation IDs, user) for action auditing.
Redaction of sensitive fields to protect passwords, tokens, and PII.
Designed to support GDPR, SOC2, HIPAA compliance and governance reviews.

Quick Start

Configure the EF Core interceptor and audit middleware in your .NET project to begin capturing audit data.

Frequently Asked Questions about audit-backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a tamper-proof audit trail for EF Core entity changes in a .NET 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.

How can I capture HTTP request context like user and IP address for .NET compliance logging?▼

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.

Does this .NET audit trail implementation support GDPR, SOC2, and HIPAA compliance requirements?▼

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.

What is the best way to redact sensitive fields and PII in .NET audit logs?▼

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.

Can I use EF Core interceptors for non-blocking audit trail writes in .NET?▼

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.