Security

SSL Encrpytion: All communication between you and our website is encrypted and protected in the same way as your online banking activities. This type of encryption is the worldwide trusted standard for secure transmission of information. HTTPS Wikipedia

Browser identification: An identification token from your browser is registered with CAVIRTEX to prevent unauthorized browsers from using your account. This token is sent to your e-mail address. An attacker would need to know your CAVIRTEX username and password as well as your e-mail address and password to compromise your account.

2 Factor Authentication: You can use a smartphone app such as google authenticator to generate a security token required for login.

No MD5s here: The MD5 hashing algorithm is known to be weak for storing password hashes. We do not use MD5 to hash your password. Nor will we be using something equivalently insecure. Even if our database was stolen, the attackers would need to decrypt your password hash.

Hourly Backups: We send encrypted backups of our entire database and live wallet keys off site to backup locations on standby. If needed, we can also rollback our database. This allows us to cancel suspicious trading activity and do our best to restore accounts and fund balances to the values prior to any attacks and resume operations with minimal downtime.

SQL injection: Our systems have been programmed to prevent SQL injections.

Outage action plan: In the unlikely event of any outage or attack, we will remain in contact with you via your registered e-mail address on your CAVIRTEX account and provide a new web address for continued operations if required. Our cold storage policy will ensure that the majority of your funds will be safe and available when we resume operations.

Trusted people and limit groups: Our admin is handled by trusted people who have been with us from the beginning. We use cold storage and admin layers to limit large transactions as well as multi-signature systems that require 4 people in separate cities to authorize large withdrawals.

Regular Security Auditing: A third party security firm regularly audits and tests our code for vulnerabilities as well as keeping up to date on the new security threats. This auditing team works with our developers implementing hot fixes and patches as necessary.