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

Introducing the Wallarm AI Control Platform: One closed loop for AI security and API security.

TL;DR- AI deployment has outpaced AI governance. Most enterprises running AI on AWS cannot answer…

5 days ago

What Your Board Gets Wrong About AI Security

Editor's note: This article was originally published by Craig Riddell on LinkedIn. It has been…

3 weeks ago

Extending Security to MCP Servers: Closing a Critical Gap

The Model Context Protocol (MCP) is a de facto standard for providing structured access to…

4 weeks ago

Introducing Wallarm Middle East Cloud: Built for Data Residency Compliance

As API and AI adoption grows across the Middle East, so do the expectations around…

1 month ago

6 Lessons Security Leaders Must Learn About AI and APIs

Most organizations treating AI security as a model problem are defending the wrong layer. Security…

1 month ago

The Governance Gap: How the EU AI Act Makes API Security a Compliance Imperative

Your legal team just handed you a 400-page document and said "figure out compliance." The…

2 months ago