Are you currently experiencing an attack?
Are you currently experiencing an attack?
Labguru (labguru.com) is the flagship product from BioData. It is a secure web based ELN [Electronic Lab Notebook] platform for designing, performing, and managing projects in the life sciences.
Labguru’s customers include a wide variety of biochemical research laboratories, both in academia and industry. As such, it has a number of unusual requirements for web security. “Initially we had a basic service from CloudFlare, plus we had implemented a lot of security within our platform’s code. But as we began to acquire some large customers from industry, we discovered that we needed a better solution to secure the endpoints that we make publicly accessible. There was a growing amount of bot scans, crawlers, and other suspicious traffic that we wanted to eliminate,” said Johai Kadosh, BioData’s DevOps and Production Manager. BioData evaluated a number of security solutions, including AWS WAF. Although it has a number of good features, it isn’t meant to be a comprehensive solution, and BioData needed much more.
The company also evaluated Imperva Incapsula and Reblaze. “We eliminated Incapsula early, because their prices were way over our budget. Then we looked closely at Reblaze.” BioData knew that its security solution had to fulfill a list of strict requirements. Some requirements could be evaluated before purchase, including compliance, customer privacy, and customization. Others could be anticipated before purchase, but needed to be verified after the deployment occurred. Those requirements included high reliability, minimal latency, and minimal cost.
Unlike many other cloud security solutions (which decrypt and often store customer data on their own infrastructure), Reblaze performs all its traffic processing exclusively on the customer’s resources.
Mr. Kadosh was surprised by the minimal overhead required for Reblaze. He said, “I would expect the WAF to add much more latency to the application than it actually does.
For all the processing Reblaze does, and all thevalue we are getting from it, I’m seeing less than three milliseconds added.
When asked about his favorite parts of Reblaze, Mr. Kadosh said, “Its compute requirements are awesome. I’m putting all my traffic through Reblaze, from multiple environments.
The machines I’m using are the lowest that Amazon provides. Reblaze’s cost efficiency is one of its greatest features.
The information that the dashboards and the logs provide is priceless.
Scrubbing incoming traffic in the cloud while adhering to strict compliance requirements for customer data privacy
Customizing web and API traffic processing according to very complex requirements, varying on a per-customer and a per-endpoint basis
Blocking hostile traffic with minimal latency
Achieving all the above with minimal added expense
Hostile traffic is blocked, and compliance is maintained; all processing occurs within BioData’s AWS resources
Compute resource requirements are minimal. Added latency is less than three milliseconds