Skip to content
SECURITY

Platform security

Security is part of the architecture and the operations, not an add-on. Below is a concise overview of the controls we apply in financial-services projects.

Back to Trust & Compliance
01

Data protection

Encryption in transit and at rest. Key management aligned with the client's policy — with HSM integration as an option.

  • TLS for all outbound and internal communication
  • Encryption of volumes and backups
  • Data classification and retention policy
  • Data masking in DEV/UAT environments
02

Identity and access control

RBAC/ABAC model based on business roles, integrated with the client's identity provider (SSO/MFA).

  • Single Sign-On and multi-factor authentication
  • Separation of operator, auditor and administrator privileges
  • Full access and permission-change log
03

Business continuity (BCP/DR)

RTO and RPO agreed with the client's team. Recovery tests and incident runbooks are part of operating procedures.

  • Architecture resilient to a single-component failure
  • Backup policy with a recovery test
  • Runbooks for typical incident scenarios
  • Tested crisis communication procedures
04

Secure development lifecycle (SDLC)

Code review, dependency scanning, security testing and secrets handling are mandatory in our pipeline.

  • Dependency and container image scanning
  • Static and dynamic code analysis
  • Centralised secrets management (no secrets in code)
  • Patching and pen-testing policy
05

Subprocessors and third-party risk

We provide the list of subprocessors and their role under procurement. Third-party risk management is aligned with DORA.

Specific controls and their scope are agreed individually within each institution's procurement and security review. This page is informational.