Web Application Security

Wallarm Kong WAF. Better Protection for Micro-services and API.

Thousands of companies from startups to Fortune 500 enterprises use Kong as their API gateway. With a blazingly fast performance, it comes with a perfect feature set for everyone who manages microservices, APIs or serverless stack.

Today, we’re thrilled to be a launching partner of Kong Hub. Kong Hub is a marketplace of plugins and modules created by the open-source community and commercial partners that was launched and announced today at the very first Kong Summit. Wallarm comes as one of the trusted partners in the Security domain alongside other modules that provide Authentication, Traffic Control, Analytics and Monitoring, Logging and other functionality.

Wallarm web application firewall (NG-WAF) module seamlessly integrates with Kong API Gateway. Easy to deploy, it provides full visibility on malicious traffic (what API methods are abused and how) and real-time protection of APIs against OWASP Top 10, account takeover, bots and application abuse. If required, it also provides active scanner checks with a DAST module to identify actual vulnerabilities (such as XXE or SQL injections) in APIs.

Just a reminder, that any security solution for APIs and microservices should address:

  • Support for XML / JSON and nested formats. As dumb as it sounds, most products process HTTP request as it’s just a string, without understanding the structure of it and parsing through the nested formats. When there is a JSON or XML request that contains a Base64 encoded field, they are not able to parse JSON/XML and decode the data in that field. A malicious payload within this parameter stays invisible for the WAF and reaches the application. Not fun.
  • No performance degradation. Latency and any overhead introduced by additional request analysis that can affect customer experience or conversion rates (ouch!). Wallarm Kong WAF module was initially developed for NGINX/NGINX Plus and written in pure C. It conducts a single-run operation to apply all the parsers and attack detection mechanisms in a matter of a few milliseconds.
  • Readiness for CI/CD. Using APIs and Microservices is inevitably accompanied with frequent code updates. Be sure that security module will not introduce false-positives or require exhausting manual rule tuning every time developers push new code to production (read: every day).

Useful links:

Recent Posts

From Shadow APIs to Shadow AI: How the API Threat Model Is Expanding Faster Than Most Defenses

The shadow technology problem is getting worse.  Over the past few years, organizations have scaled…

4 days ago

Inside Modern API Attacks: What We Learn from the 2026 API ThreatStats Report

API security has been a growing concern for years. However, while it was always seen…

5 days ago

CISO Spotlight: Craig Riddell on Curiosity, Translation, and Why API Security is the New Business Imperative

It’s an unusually cold winter morning in Houston, and Craig Riddell is settling into his…

2 weeks ago

The Myth of “Known APIs”: Why Inventory-First Security Models Are Already Obsolete

You probably think the security mantra “you can’t protect what you don’t know about” is…

2 weeks ago

Why API Security Is No Longer an AppSec Problem – And What Security Leaders Must Do Instead

APIs are one of the most important technologies in digital business ecosystems. And yet, the…

3 weeks ago

7 Reasons to Get Certified in API Security

API security is becoming more important by the day and skilled practitioners are in high…

1 month ago