Security at Cura

How we protect the sensitive portfolio and investment data you keep in Cura.

Last updated
November 12, 2026

Certifications

We're entering our observation period, and expect to have our SOC 2 Type II certification by H1 2027. If you need a letter of engagement for your own review, ask us and we'll provide one.

Infrastructure security

Cura runs on AWS and Vercel, both SOC 2 Type II providers, and we check our cloud configuration automatically.

  • Encryption at rest

    Customer data is encrypted at rest with AES-256.

  • Key management

    Encryption keys are kept separate from the data they protect and can be rotated at any time. Credentials for your connected integrations get an extra layer of encryption within our application.

  • Network protection

    Cura is reachable only over HTTPS, and our web application sits behind a web application firewall.

  • Threat detection

    Network traffic and activity in our cloud accounts are monitored continuously for signs of attack or unauthorized access.

  • Infrastructure monitoring

    Automated checks watch our cloud accounts for misconfigurations and unrecognized resources.

  • Physical security

    Our servers run in our cloud providers' data centers, which are physically secured and independently audited.

Data protection

Your portfolio data stays private to your firm.

  • Tenant isolation

    Each customer's data is kept in its own isolated environment, so no customer can see another's.

  • Encryption in transit

    All traffic to Cura is encrypted with TLS 1.2 or higher.

  • Encrypted backups

    Backups are encrypted, stored across multiple regions, and kept for 30 days.

  • Data deletion

    If you ask us to delete your data, we remove it from production within 30 days and from backups within 90.

  • Production data stays in production

    Customer data is never copied into development or test environments.

Access control

Only the people who need access to Cura's systems have it.

  • Multi-factor authentication

    Required on every internal system.

  • Least-privilege access

    Employees get only the access their role needs.

  • Audited access to customer data

    Access to customer data is granted only when needed, for a specific customer, scope, and length of time. Every access is logged and audited.

  • Regular access reviews

    We regularly review who has access and remove anything no longer needed.

  • Offboarding

    Access is revoked promptly when someone leaves.

Secure development

Every change to Cura is reviewed and tested before it ships.

  • Code review

    Every change is reviewed before release, and security-sensitive changes require approval from our security team.

  • Automated testing

    Every change must pass our automated test suite before it ships.

  • Protected releases

    No one can push code to production without going through review.

  • Vulnerability management

    Our code and dependencies are scanned for known vulnerabilities, which we fix on defined timelines.

Organizational security

Everyone at Cura shares responsibility for keeping your data safe.

  • Background checks

    Everyone is background checked when they join.

  • Security training

    Everyone completes security training when they join and every year after, and agrees to our security policies.

  • Device security

    Work devices are encrypted, password-protected, and kept up to date.

  • Code of conduct

    Employees and contractors acknowledge our code of conduct when they join and every year after.

  • Password policy

    We use single sign-on wherever possible. Other passwords are generated by a password manager, unique to each system, and never shared.

  • Asset inventory

    We keep an inventory of our production systems, checked automatically against our cloud and code platforms.

  • Asset disposal

    Company devices are wiped before they're reused or disposed of, and company data is removed from devices when someone leaves.

  • Office security

    Office access is controlled, and visitors follow our visitor procedures.

Risk and governance

We manage security as an ongoing program, not a one-time project.

  • Continuous monitoring

    Our security controls are checked automatically, every day.

  • Risk assessment

    We assess the risks to Cura and your data every year.

  • Vendor management

    Every vendor is reviewed before it gets access to any data, and reviewed again regularly.

  • 24/7 on-call

    Automated alerts for security and availability issues reach an on-call engineer around the clock.

  • Incident response

    We have a documented plan for security incidents, and we'll notify you promptly if one affects your data.

  • Cyber insurance

    We carry cyber liability insurance.

We don't train AI on your data

Cura doesn't train AI on customer data, and neither do our AI providers. OpenAI and Anthropic both contractually agree not to use API inputs or outputs for training.

Policies

Our legal commitments, and where to find the providers we use:

  • Privacy PolicyHow we handle personal data, including data we process for customers.
  • Terms of ServiceThe terms that govern your use of Cura.
  • Trust CenterSecurity documentation, compliance status, and subprocessor details.

Contact

Have a question about our security practices, or need documentation for a review? Email sharan@cura.inc.