Major update for Wallarm UI

We’ve just released a couple of features we’re really excited about

Live Threat Verification results

The Active Threat Verification component was always a unique feature of Wallarm. Having the ability to replay the attack/payload against the application (or its staging environment) gives our customers unique insights into critical events when an attacker identifies exploitable security issues.

With this new improvement to the UI, you can now see a real-time view of the process of threat verification.

No need to check attacks manually as Wallarm will do it automatically and report if there is a security incident

We show whether each attack is:

  • scheduled for verification, or;
  • already checked with a scanner and considered to be safe (not exploiting any issues), or;
  • validated as a security incident (confirmed to be targeting actual application’s security issues).

Vulnerability to Incident correlation

Now for every security incident, there is a quick link to the vulnerability affected. You can jump directly to the description and a how-to-fix instruction.

Blacklist

Blacklist is another new feature appearing in the UI. Although most attacks can be mitigated request by request, we still need a blacklist of IP addresses to block bots and mitigate behavioral-based attacks such as application abuse, brute force, and dirbusting.

For every banned IP address, we give an explanation. For instance, a customer might be informed that 63.128.163.26 was blocked because of a series of XSS, SQLi and XXE attacks.

You can see a list of the IP addresses that were banned, and the reasons why. You can quickly unblock any IP address, or change the time when it will be unblocked automatically. You can add an IP address or a whole subnet to the list, if you want them blocked.

Remember that requests are not blocked by IP address on the NGINX/Wallarm layer, so you have to set up integration with your load-balancer or firewall, as described in the documentation.

The introduction of Blacklist is accompanied by a new dashboard metric called Blocked IPs.


Looking forward to hearing your feedback. And let us know if you need a live demo of the new features.

Recent Posts

The CISO’s Dilemma: How To Scale AI Securely

Your board wants AI. Your developers are building with it. Your budget committee is asking…

2 weeks ago

Agent-to-Agent Attacks Are Coming: What API Security Teaches Us About Securing AI Systems

AI systems are no longer just isolated models responding to human prompts.  In modern production…

2 weeks ago

Everyone Knows About Broken Authorization – So Why Does It Still Work for Attackers?

Broken authorization is one of the most widely known API vulnerabilities.  It features in the…

3 weeks ago

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…

1 month 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…

1 month 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…

1 month ago