We hope you've seen our announcement introducing Barracuda Cloud Generation Firewall capabilities. We're excited to be adding this new functionality to our Barracuda Web Application Firewall (WAF) and Barracuda NextGen Firewall (NGF). In this blog post I'd like to take you through what this means and how it can help you.
Visit us at AWS re:Invent booth #1533 to demo the Barracuda Cloud Generation Firewall
Why Cloud Generation Firewalls?
Let's start with some background on cloud adoption. Multiple Barracuda surveys have revealed that although companies are migrating to the cloud, there is still concern and confusion over public cloud security. Developers are also concerned about the security of the applications they are building in the cloud, and many organizations are simply unsure of how to deploy their existing security strategies to a cloud or hybrid environment. Budget considerations also require usage and licensing planning, and this can be a daunting task for people who are new to concepts like meshed connectivity and metered billing.
Barracuda Cloud Generation Firewalls are engineered to help customers overcome these challenges and fully embrace the potential of the public cloud.
What does Cloud Generation mean?
Firewalls have been designed to protect data centers or central offices, and distributed networks with multiple locations are dependent upon other pieces of the network in some way. This often leads to lower scalability options and higher costs. One of the benefits for companies moving to the public cloud is that they can embrace a loosely coupled architecture, where there is no backhauling or other interdependence on dispersed locations. These companies can then leverage metered billing, automated deployments, horizontal (elastic) scaling, and other features that are native to the fabric of the public cloud. But to do that, they need cloud generation firewalls that support these functions.
More specifically, a cloud generation firewall will:
- Leverage cloud-native management and monitoring tools
- Take advantage of cloud-native architectures for automated deployment and scaling
- Offer API integration to use traditional Agile development tools in the cloud environment
- Offer consumption-based pricing as well as traditional firewall pricing for business flexibility
Barracuda Cloud Generation Firewalls provide all this functionality and more.
New Cloud Generation
What does this mean for you?
There are so many benefits here that it's hard to pick just a few. Probably the most obvious benefit of Barracuda cloud generation firewalls is that they are best in class security solutions for networks and applications, regardless of the deployment model. These solutions can protect your entire infrastructure, whether it is based at your premises, in the public cloud, or distributed across both. There's no need for any gaps in your security, whether you are migrating a workflow or moving your data storage or spinning up new servers for app development. Barracuda Cloud Generation Firewalls cover it all.
Another clear benefit is that these firewalls support the new consumption models of the public cloud. Because cloud applications must meet variable workload demands, it can be difficult to predict resource usage accurately. IT is expected to meet performance requirements at peak activity, regardless of usage levels at other times. In an on-premises infrastructure, this usually means sizing and licensing for the highest demands and absorbing the costs of unused licensing and capacity during non-peak times. Because the public cloud is designed to support fluctuating workloads, customers can take advantage of metered billing. This is a usage-based billing that responds to workload scaling. In short, customers can match the cost of infrastructure to the cost of consumption. Performance levels are met as expected, quality of service levels are maintained, and there are no wasted licensing costs.
- Barracuda Cloud Ready Initiative
- Barracuda Public Cloud Solutions
- Barracuda NextGen Firewalls
- Barracuda Web Application Firewalls
This article was originally published here.