Our customers trust Tricorn with findings, photos and reports about the sites they assess. This page describes how we protect that data today.
Tricorn runs on Amazon Web Services (AWS) in the United States, in the us-east-2 region. Production, development, security logging and backups each run in their own AWS account.
The application and the database run in private networks and have no public address. Traffic reaches the application only through Amazon CloudFront.
Database backups are copied to a separate AWS account in a second United States region (us-west-2).
We use AWS GuardDuty for threat detection, together with AWS Security Hub. Container images are scanned for vulnerabilities on every build.
Tricorn has written security policies approved by leadership, and staff complete security awareness training.
We are preparing for a SOC 2 Type II audit. We have not completed an audit yet, and we will update this page when we do.
The providers that process customer data, and what each one receives, are listed on our Subprocessors page.
If you believe you have found a security issue in Tricorn, email security@gotricorn.com. Please include the steps to reproduce it.