At blendingbot, security is deeply important to us. You deserve to have your personal and financial information protected using the best industry standards. We take our responsibility seriously and want you to know some of the extensive measures we've taken to protect you from online criminals.
The first step in online security is minimizing the impact of a security breach. We collect and store only the minimum amount of information necessary to provide our customers with the best experience and protect ourselves and you from malicious users.
When you follow our Setup Guide to create your Poloniex API keys, we'll only have permission to issue loans on your behalf. At no time can we make trades or withdraw funds from your Poloniex account. This means your coins can't be transferred out of Poloniex even in the unlikely event that blendingbot experiences a full system breach. The worst that an attacker could do is issue loans on your behalf.
When it comes to security, it's best to prepare for the worst, so we don't stop here. We still take great care to protect your API keys and lending details.
You may not think of physical security when it comes to your online activities, but the physical security of the servers that store your information, loan out your cryptocurrencies and serve up this webpage to you is foundational to online security.
Blendingbot is hosted entirely within Amazon Web Services (AWS). AWS is trusted by thousands of companies including even Amazon itself. AWS is audited regularly and maintains compliance with a number of U.S. and international regulations. Check out their compliance page for more details. You can also check out the AWS Security Whitepaper (pdf) for an in-depth look at what Amazon does to protect their systems.
Using AWS doesn't guarantee security by any means. It's important to configure AWS resources using industry best practices and secure all administrative access, as well as develop secure applications.
Our network has multiple layers of security with firewalls positioned strategically to protect systems from attackers, malware and unauthorized employees. None of our application servers are directly accessible via the Internet. Backend systems, including our database and those running our customers' bots, are not accessible from our DMZ. None of our production networks have any wireless access points, and all administrative access requires at least two-factors of authentication.
All sensitive data like our customers' API Secrets are encrypted at the application layer using AES-256-CBC using a 256-bit key and a unique initialization vector (IV) per record. If an attacker gained full access to the database, they would still need access to the data encryption key to view sensitive data. The data encryption key is handled securely and encrypted using a hardware security module (HSM) backed key encryption key before it is persisted anywhere. The key is rotated regularly and whenever an employee who may have had knowledge of the key leaves the company.
Web applications are developed with careful consideration of the OWASP Top 10 (pdf) web application security risks. This helps protect our customers from the top security vulnerabilities facing websites today.
Passwords are hashed using Bcrypt with a cost factor of 12. This makes our customers' passwords unreadable even in the unlikely event of a database breach.
All administrative access follows the principle of least privilege. Employees only have access to the minimum set of systems required to perform their jobs.