

Why you shouldn't lose sleep over the commercial end-of-life of ModSecurity
The ModSecurity web application firewall (WAF) engine is set to go end-of-life (EOL) on 1 July 2024.
The ModSecurity web application firewall (WAF) engine is set to go end-of-life (EOL) on 1 July 2024.
The ModSecurity web application firewall (WAF) engine is set to go end-of-life (EOL) on 1 July 2024.
Cloud may be a developers best friend, but it can also be a programmer's worst enemy.
F5 recently announced a critical security vulnerability, allowing an attacker to bypass its iControl REST authentication, and execute commands such as creating or deleting files and disabling services.
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.
All WAF vendors and services using ModSecurity are affected by this vulnerability (unless they have the vulnerable piece of code disabled, by chance).
A recent visit to Southampton Solent University.
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.
In this example, I’m going to add a new transformation function to ModSecurity to calculate the Scrabble score of a variable. This will allow us to block HTTP requests containing query string parameters with a Scrabble score above a chosen threshold.
In early June 2021, I identified a request body bypass vulnerability in the OWASP ModSecurity Core Rule Set (CRS). Loadbalancer.org appliances themselves are unaffected.
In a world where tech is constantly evolving, it’s impossible to predict all future issues/glitches that might arise.
Should you invest in a proprietary load balancer from one of the market leaders like F5? Or should you take a chance on open source load balancing software?
Control how HAProxy will be started, stopped, restarted, reloaded, or monitored.
At the end of the day open source is really about having access to the source code for your tools and programs, to do whatever you want to do with it.
In the world of web application security, it can be invaluable to consider a user's behaviour across the entire duration of their web app session.
The X-Forwarded-For Header is a simple yet powerful solution to a very common problem. I'm not sure why, but for some reason it also seems to cause a lot of confusion.
We’re always keen to give back to the community that writes such great software – our new SNMP agents and MIBs for HAProxy make monitoring your Virtual Services and Real Servers a breeze.
Dealing with bugs and vulnerabilities is quite common in the tech space. Aaron West, the head of Solutions at Loadbalancer.org shares some insights about our approach of tackling such issues, and more.
Want to configure a load balancer for VMware's AirWatch Mobile Access Gateway (MAG) and Secure Email Gateway (SEG)? Let's help you out.
A critical vulnerability in HAProxy’s HTTP/2 HPACK decoder in versions 1.8 and above has been discovered. This does not impact the majority of Loadbalancer.org customers.
We were delighted last week to host Smoothwall for a day with our team. Fuelled by coffee and Krispy Kreme doughnuts, our discussions helped us learn from one another so that we can work together even more effectively.
Normally when using a load balancer, you want the connections to be evenly distributed among real servers. However, an even distribution of connections won't always determine an evenly balanced workload within the cluster.
Loadbalancer.org were the original sponsors of the external health check mechanism in HAProxy. We think it's an invaluable tool when you need something a bit special.
An incorrect frame length check could result in a read-past-bound which can cause a crash.
It’s no big secret that a single processor can only handle so much processing in a given time. So what happens when you reach the limits of what a single processor can handle? Simple, you add more processors.