[Feature]: Centralized Cryptographic Audit Logging & Immutable Trails - #2076
Merged
Dev1822 merged 1 commit intoAug 31, 2026
Merged
Conversation
@ErebAsh is attempting to deploy a commit to the Dev's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implemented Cryptographic Audit Logging to ensure enterprise-grade data integrity and compliance (SOC2, GDPR). This update cryptographically chains every audit log entry to the previous one, making it mathematically impossible to alter historical financial or HR data without breaking the chain and leaving tamper-evident trails.
Changes Made
cryptoAudit.jsto handle deterministic SHA-256 payload hashing and HMAC signing using a system secret.audit.service.jsto fetch the previous log's hash, compute the new cryptographic sequence, and apply the HMAC signature securely with a retry mechanism to mitigate concurrent insertion conflicts.AuditLogMongoose schema to trackcurrentHashandsignaturefor strict integrity tracking.auditIntegrity.service.jsto rebuild and verify a tenant's complete audit chain from the genesis block, detecting any signs of database tampering.verifyAuditTrailIntegrityendpoint in the audit controller to generate integrity reports on demand.Checklist