Security, in brief

A check before money or a customer record changes

Written for executives and the risk or technology lead beside them. This is the public summary. The detailed security pack for a product is shared under a non-disclosure agreement (NDA) when we work together.

Request a demo Report a vulnerability

What you can rely on

Before money or a customer record changes, Aegis and Atlas check who is asking and whether the change is allowed. Where the path needs a risk decision, Sentinel decides and can ask Aegis to confirm the person again. If a required check cannot be made, the change stops.

A sensitive change is checked by Aegis (who is asking), then Atlas (is it allowed), then, where a risk check applies, Sentinel (is it safe). Sentinel can ask Aegis for a step-up. If any required check fails or cannot be made, the change stops. If all pass, it proceeds.
  • Who is asking, and are they allowed? Aegis is where people sign in and where identity is checked. Atlas decides what they are allowed to do, including an emergency stop.
  • No check, no change. When a platform moves money or changes a customer record, and the architecture says those checks are required, the change does not go through if the check cannot be made.
  • A trail a reviewer can follow. On retail account opening, TeKYC records the customer-check decision and passes a reference to Titan. A reviewer can see who decided, and which customer record was created.
  • Your duties stay yours. We help client banks meet their duties. Trudi is not a deposit-taking institution and does not claim a BSP or AMLC license. The Privacy page covers this website only.

Where each duty sits

A risk lead can use this in a first meeting. Each platform page says how that system connects.

One owner for each duty. The list below is the text version.
  • Sign-in and the security log sit in Aegis.
  • Permission, including an emergency stop, sits in Atlas.
  • The customer-identity decision sits in TeKYC. The accepted decision is passed to Titan as a customer reference.
  • The official customer file and the ledger sit in Titan.
  • Risk decisions and risk cases sit in Sentinel. Documents, retention, and legal hold sit in Scribe.
  • The reports the bank prepares for regulators are assembled in Ledgerhall, and data quality checks run in Argus. The institution remains the regulated entity.

What we will not put on this page

This page does not show registration numbers, ISO or SOC badges, penetration-test scores, or a client security attestation. The detailed product security pack is shared under an NDA.

Reporting a vulnerability

Email [email protected]. Describe the page or system, what you observed, and how to reproduce it. This site does not publish a bug-bounty program. The machine-readable contact is security.txt.

Want the detailed security pack?

It is shared under an NDA when we work together. Ask for a demo, or read how the platforms fit on Architecture.

Request a demo Get in touch