Data safekeeping: Security
Data security is more important than ever. With breaches in the news daily, extra care and vigilance is required to keep data safe and the service in good condition.
With Whally, you’re in good hands (fins?). Extensive effort and care have gone into the design of Whally to ensure it follows the latest best practices in information and systems security, to keep the data safe and the bad guys out. The Whally engineering team brings deep experience in secure design and operations from years of academic training and experience in military environments.
Security is a very technical subject. We welcome a conversation with anyone interested in reviewing the specifics of our techniques and protections. We think you’ll find that Whally is perhaps even over-engineered for security compared to its peers. This includes all the standard things like encryption and authentication, but also enterprise-grade security features and infrastructure including granular access controls and auditing.
Some aspects contributing to our security posture include:
- All communications with Whally are encrypted with modern cryptography, always
- Requests to Whally are protected by authentication that uniquely identifies users and their permissions
- Device pairing is performed via cryptographic token exchanges
- Database operations derive from a securely bound identity to ensure isolation of customer data
- Granular role-based access control allows specifying custom permissions for any combination of data access to groups or individuals
- All data operations produce an audit history that can be used to identify “who, what and when” for every change
- Sessions are maintained with secure HTTP-only cookies, the best practice in web security
- Customer data is backed up regularly and stored in multiple geographic regions for isolated restoration
- Operational systems are protected with two-factor authentication by Whally engineers
Questions? Contact Us
If you have a question about Whally security or believe you’ve found a problem, please let us know: firstname.lastname@example.org