At Tres, we know that your data in Tres is critical for your business, and we make sure that it’s safe and readily available. In the event of a disaster, you can take comfort in knowing that your data is safe.
- Protocols
- Browser-based Application
- No local applications need to be installed.
- No local servers/systems needed – access from anywhere you have internet connectivity.
- Connectivity to the server is encrypted via HTTPS.
- MFA via Microsoft authentication.
- Cloud-Based
- Service-based
- Server applications run as app services in Azure; app services are redundant and scalable.
- Underlying database architecture (Azure Sql, based on SQL Server) is automatically updated with no effort on our part.
- Fault-tolerant within a region and across regions.
- Initially, we’ll have redundancy within our current region (US West).
- Browser-based Application
- Security
- Credit Card Tokenization
- Credit card data is not stored locally; instead, we store a token that is managed in a separate system (Tokenex).
- Data is tokenized when added/updated and de-tokenized as needed.
- Tokenization reduces PCI scope and simplifies audits.
- Credit Card Tokenization
- Backups
-
- Run automatically and do not require any configuration or administration by users.
- Are fully encrypted.
- Are immutable (preserved), meaning the backups, once created, cannot be modified.
- Are stored in multiple regions (Western/Eastern US).
- Types of backups
- Short-term backups run continuously and allow for point-in-time recovery going back 14 days.
- Long-term backups run weekly, monthly, and yearly and are kept for up to 3 years.
- Tres can provide customers with a complete backup copy of agency data upon request on an as-needed basis.
-
Replicas
-
Tres data is also replicated constantly to other regions to allow quick recovery in the case of a primary server failure.
- Replicas are read-only and can be used for additional queries that don’t write data to off-load some work from the primary.
-
-