According to our status page.
Encryption in transit
Encryption at rest
All our user data (including passwords) is encrypted using battled-proofed encryption algorithms in the database. Additionally, the synchronized data of our users are encrypted using End-to-end-encryption.
We provide the option for customers to delete data after their subscription ends. All data is then completely removed from the dashboard and server. Every user can request the removal of usage data using the account page or by contacting support.
Read more about our privacy settings at https://termius.com/privacy-policy.
Our systems have 99.99% uptime according to our status page.
We use security headers to protect our users from attacks. You can check our grade on this security scanner for termius.com, api.termius.com, and account.termius.com.
We use security automation capabilities that automatically detect and respond to threats targeting our apps.
All of our services run in the cloud. We don't host or run our own routers, load balancers, DNS servers, or physical servers. Our service is built on Amazon Web Services. They provide strong security measures to protect our infrastructure and are compliant with most certifications. You can read more about their practices here.
Our network security architecture consists of multiple security zones. We monitor and protect our network, to make sure no unauthorized access is performed using:
A virtual private cloud (VPC), a bastion host, or VPN with network access control lists (ACL's) and no public IP addresses.
A firewall that monitors and controls incoming and outgoing network traffic.
IP address filtering.
We use Distributed Denial of Service (DDoS) mitigation services powered by an industry-leading solution.
We develop the following security best practices and frameworks (OWASP Top 10, SANS Top 25). We use the following best practices to ensure the highest level of security in our software:
Developers participate in regular security training to learn about common vulnerabilities and threats.
We review our code for security vulnerabilities.
We regularly update our dependencies and make sure none of them has known vulnerabilities.
We use Static Application Security Testing (SAST) to detect basic security vulnerabilities in our codebase.
We rely on yearly third-party security experts to perform penetration tests of our applications.
