Skip to main content

There is sizing, and then there is right sizing

When it comes to firewall upgrades or refreshes, you need to know your:

  • Current traffic volumes and mixture
  • Session counts
  • Number of users
  • Current and future Internet or private connection pipes
  • Current and future throughput requirements (VPN, SSL Inspection and decryption, etc...)
  • Current and future unified threat management (UTM) needs
  • Interface requirements 
  • Number of IP devices
  • LAG requirements 
  • Future growth 
I am sure you can come up with more variables and compare it to the vendors specification sheet in order to come up with an accurate size or model of a security appliance.  However, nothing beats a real/live test with a traffic generator.  

When I usually size a box based on the customer's requirements, I also factor in real life examples, previous firewall implementations and what the Internet/application traffic trends. I have heard so many "oh we are not going to use such and such application" or "we will never use SSL inspection".

So when your SE comes back with a bigger box, don't immediately shoot him/her down and think he is trying to up sale you. 
Labels:

Comments

Post a Comment

Popular posts from this blog

MPLS vs VPN (Internet Connection) and power

This topic has been covered extensively by experts. What has not been covered in my opinion, is the underlying and fundamental change of transport infrastructure and specially power. The traditional WAN transport mechanisms are solid in terms of power normalization all through the last mile.  With the new (or not so new) shift towards commercially available Internet connections (namely DSL and Cable), customers need to watch out for excessive power coming through those lines and the respective modems and into their edge devices. There are surge protectors out there with "ethernet in/out" ports which could be used to mitigate this problem. Happy conversation out there...
Post a Comment
Read more

SD-WAN? Let's talk

I am sure at this point, you all have caught up on with this SD-WAN craze.  Some early vendors are now bought by industry giants.  Some have really cool cloud provisioning and management dashboards. Some claims that your edge has never been this simple to set up before. However, there are still a few concerns I have: VPN technology is a mature one by now.  There are vendors out there who can offload IPsec tasks and processes onto a hardware based processor.   Would these new "SD-WAN" providers give me the same throughput/granularity? How scalable is the solution? Applications - There are vendors out there who did WAN Optimization for living and have a very rich application signature database.  What about the pure play vendors? Same goes for routing.  can you handle complex routing? can you offload or optimize those touting decisions? What if I already have that infrastructure (VPN/Routing) in place? would your solution be a tunnel in ...
Post a Comment
Read more

Training!

As a SE, I see successful roll outs and adoptions as well as botched ones.  When I go through post-roll out analysis and lessons-learned efforts, most of the time, I see the culprit right away.  Lack of knowledge and going through the project/roll out blind, usually sinks the ship. There are many reasons some customers skip training.  The first reason always points to budget.  I hear "We don't have budget for training" or "our engineers will figure it out" or the best one yet, "we don't see any benefit in wasting our engineers' time with training". The second reason is "ego".  I know we are all engineers and have been around security or networking products for a long time.  But implementing a new security platform in an enterprise will take some time to correctly configure, optimize and utilize.   a new centralized management system which requires some scripting knowledge alone  is an formidable undertaking. By blindly going throu...
Post a Comment
Read more