Security
Built for sensitive financial workflows.
This page describes the security architecture DATAMASON Ledger is designed to. We describe it openly, and we will publish independent attestations here only once they exist.
Principles
Four rules the design follows.
- 01Least privilegeAccess starts at nothing and is granted by role.
- 02Isolation by defaultWorkspaces are separated; nothing is shared unless configured.
- 03Everything recordedAccess, changes and approvals leave an audit event.
- 04Secrets are shown onceCredentials and keys are never displayed again after entry.
Controls
Enterprise security architecture.
Each control carries a status. Architecture target means the design commitment we are building to. Planned means on the roadmap.
Encryption
Financial data is designed to be encrypted in transit and at rest, with keys managed separately from application data.
Architecture targetSecure credentials
Source credentials are stored encrypted, scoped to one connector and never displayed again after entry.
Architecture targetRole-based access
Roles for viewers, operators, approvers and administrators, with least privilege by default.
Architecture targetAudit logs
Access, changes and approvals are recorded with the actor, the time and the previous value.
Architecture targetAPI security
Scoped API keys per workspace and environment, rate limits, idempotency and signed webhooks.
Architecture targetWorkspace isolation
Each workspace’s data is logically separated, with no cross-workspace queries by design.
Architecture targetMFA
Multi-factor authentication for user accounts, enforceable per workspace.
PlannedSSO-ready architecture
Identity is designed to sit behind SAML or OIDC single sign-on for enterprise workspaces.
Planned
Data flow
Where trust boundaries sit.
Credentials never cross the connector boundary in readable form, and nothing reaches the application without validation.
- 01Your source
- 02Connector (credential boundary)
- 03Ingest and validate
- 04Encrypted store
- 05API and application
Shared responsibility
Who does what.
Compliance
No badges we haven’t earned.
Responsible disclosure: a dedicated security contact will be published here before launch. In the meantime, use the contact form and choose “Security review”.
Make every financial transaction explainable.
Connect your financial systems, reconcile transactions automatically, and build a reliable source of financial truth.