Security, in brief
A check before money or a customer record changes
This page is written for an executive and for the risk or technology lead beside them. It is the public summary. The detailed security pack for a product is shared under a non-disclosure agreement when we work together.
What you can rely on from this page
- Aegis is where people sign in and where identity is checked. Atlas decides what they are allowed to do, including an emergency stop.
- 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.
- 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.
- 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 describes this website. Product security beyond this summary is shared under NDA.
Where each duty sits
A risk lead can use this list in a first meeting. The platform pages say how each system connects.
- Sign-in and the security log sit in Aegis.
- Permission, including an emergency stop, sits in Atlas.
- The customer-identity decision sits in TeKYC, and the accepted decision is passed to Titan as a customer reference.
- The official customer file and the ledger sit in Titan.
- Risk cases sit in Sentinel. Documents, retention, and legal hold sit in Scribe.
- The reports the bank prepares for regulators are assembled in Ledgerhall. 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 a non-disclosure agreement.