Governance

  • Append-only audit trail

    Actions are written to an audit trail that the database itself refuses to update or delete. It doesn’t rely on the application behaving correctly.

  • Maker-checker exemptions

    Excluding an account from monitoring needs two people: the person who proposes the exemption can’t approve it.

  • Recorded decisions

    Alerts can’t be closed without a disposition, and case outcomes go to the MLRO for approval.

Access control

  • Role-based access

    Five roles (Admin, Compliance Officer, MLRO, Analyst and Auditor) determine what each person can see and do.

  • Two-factor authentication

    Users can protect their accounts with an authenticator app, with recovery codes for lost devices.

  • Login protection

    Repeated failed sign-ins lock the account temporarily, and integrations use separate service-account tokens rather than personal credentials.

Deployment

  • Your infrastructure

    TXN-Monitor is deployed on your own Kubernetes cluster. Each deployment serves a single institution. Encryption in transit and at rest is configured through your infrastructure, under your control.

  • Hardened containers

    Services run as non-root users on read-only file systems, and every release image is scanned for known vulnerabilities before it ships.

We’re happy to take your security and IT teams through the architecture in detail as part of a demo.