What should I use for consent records and audit trails?

For consent records and audit trails, use systems that are:

• Tamper-evident
• Versioned
• Time-stamped
• Immutable or append-only
• Searchable and exportable
• Access-controlled

Good options for consent records

Use a dedicated consent management system or a database table designed for immutable event logging. Each consent record should include:

• User/patient/customer ID
• What they consented to
• Exact wording shown at the time
• Timestamp
• Channel/source
• Version of the policy/notice
• Revocation status and timestamp
• Proof of capture, if relevant

Good options for audit trails

Use an append-only audit log in a centralized logging system, SIEM, or compliance-grade event store. Each audit entry should include:

• Actor
• Action
• Timestamp
• Resource affected
• Before/after values or change summary
• Source IP / device / session
• Outcome status

Common tools/patterns

• Relational DB with append-only tables for consent metadata
• Event sourcing or immutable event logs
• Cloud audit services like AWS CloudTrail, Azure Monitor, Google Cloud Audit Logs
• Log platforms like Splunk, Datadog, Elastic, or Sentinel
• WORM storage or object-locking for high-integrity retention
• SIEM for security/compliance auditing

Avoid

• Storing consent only in a mutable user profile field
• Overwriting records without history
• Relying only on application logs
• Keeping audit trails in places users/admins can edit

Practical recommendation

If you’re building this yourself:

• Store consent in a dedicated consent_events table
• Store audit trail entries in an audit_events table
• Send both to a centralized, append-only logging platform
• Back them up to immutable storage

If you want, I can suggest a specific schema for consent and audit tables or recommend tools based on your stack.