It is understandable that SysAdmins, DevOps, and most in the IT and Security Departments involved want to ensure all load balancers are fully patched and protected, given that our product plays an important role in their topology.
The only real reason for separate network ports is physical redundancy. Because the other primary reason (security segregation) can be easily implemented using VLANs.
At Loadbalancer.org, our heroes are open source. And for good reason. Open source software plays an intrinsic part in our company, products, and services.
Customers with manually configured, custom client authentication deployments (rare) or using “re-encrypt to backend” to communicate with untrusted third-party servers (very rare) may be impacted.
As you know, we get excited about solutions, not semantics, so I'm going to go against the grain here and say 'Application Acceleration' is one of those buzzwords that's about as useful as all that designer water that's out there these days.
Many things in tech are over-complicated for no reason, and iRules are a prime example of that.
The topic of hardware replacement, trade-in, and upgrade options is rife with opinions, bad habits, and rules of thumb. It gets even more complicated when you consider how your choices are affected by your vendor's randomly changing end-of-life policies.
For the uninitiated, layer 4 DR mode is a high performance load balancing method available on our appliances. It works by having all response traffic flow from the servers straight back to the clients.
Load balancers are built to help scale up your back end servers, to allow for the growth of users. But what if the load balancer could also grow with you?
We get a lot of customers asking to buy a single load balancer. Understandably. One is cheaper than two. But here's why you might want a pair.
A local privilege escalation vulnerability was found on polkit's pkexec utility. It is a critical vulnerability because it gives full root privileges to any local user or attacker.
We love complex rules. Although, we have seen some pretty scary config files.
All WAF vendors and services using ModSecurity are affected by this vulnerability (unless they have the vulnerable piece of code disabled, by chance).
Network Security devices such as firewalls, WAF, SWG, IPS etc. are often deployed inline with bridge mode., which has two major problems.
A WAF isn't a magic bullet, but, as part of a defense in depth strategy, a properly configured WAF should catch and stop common, everyday attacks.
A recent visit to Southampton Solent University.
!!WARNING!! This blog contains the generic phrase "IT modernization" which some of our readers may find distressing.
All Secure Web Gateways require client IP transparency in order to implement any proper kind of security and authentication. Which can be a real pain if you have a load balancer in the middle.
The Apache Log4j utility is commonly used for logging requests by millions of Java applications to log error messages. However, recently the critical vulnerability CVE-2021-44228 was discovered in the Apache Log4j library.
Fast forward to a post-Covid-world (if we can call it that) and in many ways the pandemic has helped us all go back to basics and appreciate what’s important in life.
The pain experienced by your support and professional service teams is enormous. Not least because every customer experiences this issue at the same time!
There are a number of different types of virtual desktops; two of which rely on virtualization software.
For each application, will you 'lift and shift' or rebuild specifically for the cloud? Which applications can't or shouldn't be moved? Do you want separate applications in separate clouds
Object storage has usurped structured data storage as the superior storage architecture solution. And for good reason.
The increased appetite for digital lending and credit solutions has led to an explosion in financial software, algorithms, and applications.