Consent-API: Tamper-proof audit log

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: High
    • 3.14
    • Affects Version/s: None

      What this is
      A record of every consent action that nobody can change later.

      Steps

      1. Write an entry to cm_audit_log for every consent action: action, patient, purpose, status, who did it, source IP.
      2. Link each entry to the one before it (prev_hash and entry_hash), so any change can be spotted.
      3. Do not allow the application database user to update or delete the audit log.
      4. When the DPO exports records for an audit or regulator request, include the consent history, proof details and an audit-log integrity check.

      Done when

      • Every consent action has an audit entry.
      • The application cannot change or delete an entry.
      • A changed entry is detected by the integrity check.

      Source: DPDPA Compliance Proposal v14, sections 3.2.1, 5, 6 (C24)

              Assignee:
              Vanitha S
              Reporter:
              Shivani Garg
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: