
Web Application Firewall. Says no. And tells you why.
Rule sets maintained by Link11 stop SQL injection, cross-site scripting and the rest of the OWASP Top 10.
- Less rule maintenance
- Controlled roll-outs
- Every block traceable

Web Application Firewall. What it is and what it does.
The Web Application Firewall is part of the Link11 WAAP platform. Managed rule sets for the OWASP Top 10 and your own policies per application inspect every request at the edge — headers, cookies and arguments, not just address and port.
Attacks change daily. Your rules should keep up.
- 24/7 SupportSecurity threats don’t wait for business hours, and neither do we. Our specialists are available around the clock to help you when needed.
- GDPR-compliantLink11’s European location ensures your content remains compliant with strict GDPR regulations and EU data protection laws.
- Fully managed serviceOur fully managed solution, maintained by security experts around the clock, ensures your protection is always up to date, 24/7, 365 days a year.
Attacks don’t wait for your maintenance window. The WAF holds the gap until the patch ships.
Three situations where an application stands alone without a firewall in front of it.
Link11 watches for new vulnerabilities and updates your platform’s rules without you lifting a finger.
Headers, cookies and arguments of every request are inspected — not just address and port.
Monitor, allow, block — three separate actions available to the same rule.
Less firefighting, more planning. How teams work with the WAF.
Some 19,000 pharmacies and more than 50 manufacturers use the pharma mall platform. A failure would hit all of them.
Pharma mall tested the WAF and Web DDoS Protection for several months. When it reorganized its data center, the switch was flipped at 10 p.m. on a Friday night: it went smoothly right away.
Case study: pharma mallBot scans and crawlers kept growing at a life-science SaaS provider, while GDPR and FDA CFR 21 require all traffic to stay within its own compute resources.
Link11 processes all traffic in a Virtual Private Cloud under the customer’s own account.
Small bot attacks bypassed Quipu’s native cloud protection. Lowering rate limits stopped the bots, but also locked out legitimate customers.
A dedicated Link11 engineer adapted the protection to Quipu’s infrastructure. Its security posture shifted from reactive to resilient.
Case study: Quipu


No block stays a mystery. You see which rule fired, and why.
Which requests were inspected, which rule fired, what the request looked like.
One request, checked in sequence. All in one pass at the edge.
Before you connect. The technical details.
- Deployment: DNS change, reverse proxy
- Coverage: OWASP Top 10 plus custom rules
- Rule actions: Monitor, allow, block
- Part of: The WAAP platform, one interface
- Deployment
- Six steps: backend service, certificate, security policy, server group, DNS change, publish. Upload certificates or renew them via Let’s Encrypt.
- What we operate
- Maintenance of rule sets and signatures; updates when new vulnerabilities appear.
- What you provide
- Control over your DNS and an origin reachable from our edge. Optionally your existing certificates.
- Rule sources
- Link11-maintained rule sets for the OWASP Top 10, plus your own rules per application and path.
- Rollout
- The Monitor action tags a request without responding to it. The events log shows what a rule would catch.
- Change safety
- Changes are saved and only take effect on “Publish”. Any earlier configuration can be restored.
- Where it ends
- Only traffic that runs through the platform is filtered.
- Not a replacement for patching
- The firewall buys time. It only knows patterns someone has described.
That’s the first thing I do when I open my laptop in the morning — I look at the Link11 dashboards.

Questions before you decide. Answered directly.
What happens when a new vulnerability becomes known?
Link11 monitors new vulnerabilities and updates your platform with the matching protection — without any action on your side. Application allowlisting also admits only traffic that matches the rules defined for your application, so protection applies even before a signature exists.
What if legitimate users get blocked?
You see why. The platform shows all traffic, not just blocks — the events log lists which rule fired for every request. Many blocks on the same URL from different sources are a typical sign of a false positive; you then adjust the rule or set it to “Monitor”.
How does onboarding work?
In six steps: define the backend service, add the certificate, derive a security policy from the default policy, create a server group, point the A record at the WAAP and go live with “Publish”. Until then everything sits in staging and can be tested.
Can we feed events into our SIEM?
Yes. Log exporters stream the latest events every few seconds to a destination of your choice, such as a SIEM — configurable per server group. Traffic data can also be queried via the platform API.
What does the WAF cost?
The WAF is part of the WAAP platform. Packages start with Core (see pricing), booked through sales; larger setups get an individual quote based on scope and operating model.
Let’s talk
Your business stays online. We’ll show you how.



