Security

Security at Tudovu

Tudovu asks for access to your AWS account and your GitHub repositories. This page explains exactly what that access is, how changes reach your account, and how the platform that uses it is run.

Tudovu's own policies and compliance documents are available on request through our Trust Center, hosted by Thoropass.

How changes reach your account

Tudovu proposes. Your pipeline deploys.

Tudovu proposes infrastructure changes as pull requests. Nothing reaches your account until your team merges and your own pipeline deploys it; Tudovu then re-runs the check to confirm the fix landed.

  1. Read and check

    Tudovu reads your account through a role you create and runs its security checks against it.

  2. Propose a pull request

    Fixes arrive as CloudFormation in your repository, with the check they satisfy named in the pull request.

  3. You merge, your pipeline deploys

    The product does not merge pull requests. Deploys run in your GitHub Actions under a role only that workflow can assume.

The platform

How we run Tudovu.

Hosting and data

  • Runs on AWS in us-east-1, in private subnets behind AWS WAF
  • Multi-AZ PostgreSQL database, encrypted at rest, with automated backups
  • Evidence files in an encrypted, versioned S3 bucket with public access blocked and short-lived download links

Accounts and secrets

  • Platform secrets kept in AWS Secrets Manager
  • Passwords hashed with bcrypt; session and API tokens stored only as hashes
  • Sign in with email and password or Google, with optional authenticator-app MFA

Our own delivery

  • Production releases must pass secret scanning, static analysis, container scanning, and dynamic scanning
  • Our own infrastructure is defined in CloudFormation and deployed through CI/CD
  • Tudovu's policies are documented in our Trust Center