Hrithik.Security.AuditLogging 1.0.0

🔐 Hrithik.Security.AuditLogging

Compliance-grade, tamper-evident audit logging for .NET applications

Hrithik.Security.AuditLogging provides a secure, append-only audit logging framework designed for financial, fintech, and enterprise systems where audit trails must be immutable, verifiable, and trustworthy.

✨ Key Features

✅ Append-only audit logs

🔗 Cryptographic hash chaining (tamper-evident)

🧱 Storage-agnostic design

🧩 Pluggable audit stores

🕵️ Correlation-ID aware

🏦 Banking & compliance friendly

This library is not general application logging. It is designed for security events, financial actions, and regulatory audits.

📦 Installation dotnet add package Hrithik.Security.AuditLogging

🎯 When Should You Use This?

Use Hrithik.Security.AuditLogging to record:

Authentication & authorization events

Security violations (signature failure, replay attack)

Financial operations (payments, settlements)

Administrative actions

Sensitive data access

Typical industries:

Fintech

Banking

Trading systems

Regulated SaaS platforms

🧠 Core Concepts 🔹 AuditEvent (What Happened)

Represents a high-level security or compliance event.

var auditEvent = new AuditEvent( EventType: "SECURITY", Action: "SIGNATURE_FAILED", Actor: "client-123", Resource: "/payments", Success: false, Timestamp: DateTime.UtcNow, CorrelationId: Guid.NewGuid().ToString() );

🔹 Audit Log Integrity (How It’s Protected)

Each audit entry is cryptographically linked to the previous entry:

Hash(n) = SHA256(Hash(n-1) + Payload + Timestamp)

✔ Any modification breaks the chain ✔ Tampering becomes detectable ✔ Meets audit-trail integrity requirements

⚙️ Getting Started 1️⃣ Register Services using Hrithik.Security.AuditLogging;

services.AddAuditLogging();

This registers:

IAuditLogger

Default in-memory audit store (for development/testing)

2️⃣ Log an Audit Event var auditLogger = serviceProvider.GetRequiredService<IAuditLogger>();

await auditLogger.LogAsync(new AuditEvent( EventType: "AUTH", Action: "LOGIN_SUCCESS", Actor: "user-42", Resource: "/login", Success: true, Timestamp: DateTime.UtcNow ));

🧩 Architecture Overview Application ↓ IAuditLogger ↓ Hash-Chained AuditLogEntry ↓ IAuditStore (Pluggable)

🗄️ Storage Providers

The library ships with:

InMemoryAuditStore (default)

Planned / user-implemented stores:

SQL Server

MongoDB

Azure Blob Storage

Elasticsearch

Production systems should implement their own durable store.

🔐 Security Guarantees Guarantee Description Immutability Logs are append-only Integrity Hash chaining prevents tampering Traceability Correlation-ID support Isolation Audit logging is decoupled from app logging ⚠️ Important Notes

Do not store raw PII in audit metadata

Mask or tokenize sensitive fields

Use UTC timestamps only

Persist audit logs in write-once or restricted storage

📌 Versioning & Stability

Semantic versioning

Stable public abstractions

Breaking changes only in major versions

📜 License

MIT License

👤 Author

Hrithik Kalra .NET | API Security | Fintech Systems

📧 Email: hrithikkalra11@gmail.com

If you find this package useful, consider supporting its development:

• ☕ Buy Me a Coffee: https://www.buymeacoffee.com/alkylhalid9
• ❤️ GitHub Sponsors: https://github.com/sponsors/hrithikalra

Support is entirely optional and helps sustain ongoing development and maintenance.

🔗 Related Packages

This package is part of the Hrithik.Security ecosystem:

• Hrithik.Security.ApiKeyManagement
  API key generation, storage, and scope-based authorization

• Hrithik.Security.RequestSigning
  HMAC-based request signing for tamper-proof APIs

• Hrithik.Security.ReplayProtection
  Short-window replay attack prevention

• Hrithik.Security.RateLimiting
  Flexible, API-key–aware rate limiting for ASP.NET Core APIs

• Hrithik.Security.Idempotency Idempotency-key–based protection for safe retries in financial APIs

• Hrithik.Security.Jose JWT and JWS utilities for secure token handling and message signing

  Together, they form a complete API security framework.

These packages are independent and can be used together or individually.