Skip to content

security(backend): make audit records tamper-evident and queryable #127

Open

Description

@arisu6804

Problem

Sensitive transfer investigations are unreliable if audit records can be changed silently or cannot be correlated to a request.

Objective

Deliver a production-quality improvement to transfer and administrative audit storage that creates measurable value for correctness, security, reliability, performance, or maintainability.

Implementation scope

  • Add append-only or hash-chained integrity metadata; include actor, scope, target, correlation ID, outcome, and redacted changes; restrict queries.

Acceptance criteria

  • Tampering is detectable; every privileged mutation has one outcome event; authorized operators can filter without exposing secrets.

Required validation

  • Integrity-chain, redaction, duplicate-event, query authorization, and correlation tests.
  • Existing tests and CI remain passing.
  • Add regression coverage for the original failure mode.
  • Do not weaken, delete, or skip unrelated tests to obtain a green build.

PR quality bar

  • Keep the PR focused and explain design tradeoffs, compatibility impact, and test evidence.
  • Avoid typo-only, documentation-only, cosmetic-only, or unrelated refactor submissions.

Out of scope

  • Broad rewrites not required by the acceptance criteria.
  • Changes to unrelated services, contracts, or user flows.

Activity

  1. added
    enhancementNew feature or request
    GRANTFOX OSSOpen-source issue tracked by GrantFox
    MAYBE REWARDEDThis issue may carry a reward
    priority:highHigh implementation priority
    on Aug 21, 2026
  2. rupesh-kumar-sah commented on Sep 14, 2026

    @rupesh-kumar-sah

    Hello @maintainers,

    I would love to take this on. My planned approach:

    • Structure backend handlers for security(backend): make audit records tamper-evident and queryable with strict input validation, proper HTTP error codes, and idempotent execution.
    • Cover implementation with end-to-end integration tests for standard and edge-case inputs.

    Looking forward to contributing—please feel free to assign!

  3. guptakumarranjeet150 commented on Oct 3, 2026

    @guptakumarranjeet150

    Greetings,

    I would like to work on this issue.

    Implementation approach:

    1. Audit storage layout and state invariants ensuring strict auth guards.
    2. Implement deterministic state transitions with safe checked arithmetic.
    3. Add hermetic unit and regression tests covering authorized, unauthorized, and boundary edge cases.
    4. Profile instruction and CPU/gas limits under Soroban host environment.

    Please assign this to me if the plan looks good. Thanks!

  4. woahwhattheheck commented on Oct 6, 2026

    @woahwhattheheck

    /claim #127
    PR: #142

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    GRANTFOX OSSOpen-source issue tracked by GrantFoxMAYBE REWARDEDThis issue may carry a rewardThird CampaignThird Campaign contributionenhancementNew feature or requestpriority:highHigh implementation priority

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions