Notifications to your Microsoft Teams channel are now available.
Get updates for security and system events:

• Vulnerabilities detected
• Scope changed: updates in hosts, services, and domains
• Exceeded threshold of attack, hit, or incident number
• Newly added users
• Deleted or disabled integration

Read more about setting up the integration with Microsoft Teams on our documentation portal.

Now rule conditions can be configured faster. It is enough to specify a request address in the newly added URI constructor form, and we will automatically convert it to a variety of conditions for each request point. The conversion result can be extended in the advanced edit form you used before.

The URI constructor accepts regular expressions and several other formats. For more information, check our documentation.

Reduce the number of false positives by using the following rules:

• Disable base64 parser for parameters with unencoded values
• Allow file upload and binary data transfer in parameters
• Disable search some attack types for specific endpoints, such as SQL injection, in posts on the DBA forum

With other rule types, you can also add headers to the server response or control the mode of the Active threat verification module. For the detailed description of the new rules, check our
 documentation.

P.S. If our support team has already created these rules, they will be displayed in the Rules section.

Should your customers come from data centers? Not typically. It could be helpful to exclude some of the traffic sources to improve the security of applications and APIs.

With Wallarm, you can block traffic originated from a specific country based on compliance requirements ,or block Tor exit nodes and popular proxy servers frequently generating a lot of malicious requests.

Wallarm also identifies and displays in the Wallarm Console the IP address sources, i.e countries, data centers, VPN, and residential proxies.

Read more about the new blocking features on our documentation portal.

We rely on the data from 3rd party providers including IP2Location which is a partner of Wallarm.

We are pleased to announce the general availability of the Wallarm Node 3.2. This is a major update recommended to install.

Highlights

• Support for new filtration mode, safe blocking
• Management of IP address whitelist via the Wallarm Console
• Ability to whitelist, blacklist, or greylist a subnet, Tor network IPs, VPN IPs, a group of IP addresses registered in a specific country or data center
• Ability to whitelist, blacklist, or greylist request sources for specific applications
• New module API Discovery that automatically identifies the application API structure based on real traffic analysis
• The number of requests originated from blacklisted IPs is now displayed in the statistic service output, in the new parameter blockedbyacl and in the existing parameters requests, blocked

How to upgrade

Upgraded packages of Wallarm node are already available for installation from the repositories, AWS AMI and GCP VM images. The migration guide is available on the docs portal.

What do you know about your APIs? Why are the vulnerable v2 and v3 still exposed if they are deprecated for almost a year? What else is exposed, and you don’t even know? Are Swagger specs up to date? (Teaser: Surely not). A lot of questions, right? Meet Wallarm’s latest feature for API Discovery and Observability to better understand and protect your APIs.

Wallarm API Discovery identifies all APIs including shadow and zombie APIs and gives you up-to-date specs — based on the actual API usage.

So how where exactly can API Discovery help? There are two major ways:

• Firstly, API inventory. The larger the company, the fewer the people that actually know what you have exposed. Different endpoints are owned by different teams. Add here multiple versions of APIs — some that are already deprecated and some still maintained — and this very soon becomes a total mess. You can easily have some outdated (and vulnerable) version of the API method exposed — and nobody will even know! It’s called a Shadow API. The only way to get full visibility is to see what APIs are actually used and how they are used, based on the traffic.
• Secondly, up-to-date API specs. We bet you wouldn’t be surprised that specs are very often behind. It’s a life after all and docs are rarely properly updated. But you would be amazed by how significant the difference between docs and reality can be. For some APIs, you can have no Swagger at all. Or, you can have docs that clearly say that /checkout method has five parameters. Meanwhile, real traffic can show that there are plenty of requests that actually have six parameters, with one of them optional. Think of it as Swagger / OpenAPI specs generated based on the traffic.

Join the early access program by sending a note to request@wallarm.com and read a blog post for more details.

Now we have a Wallarm service status page available at https://status.wallarm.com. The page displays live and historical data on the availability of the Wallarm Console and Wallarm API services for each Wallarm Cloud.

You can use Subscribe to updates to receive a notification when a service status changes via Email, Slack, SMS, Webhooks, and other methods.

On this page, we also post planned maintenance announcements and a description of which parts of the service may not be available during maintenance.

We have expanded the set of rules for detecting LFI attacks (Local File Inclusion) and new RCE attacks (Remote Code Execution) against Symphony.

We have also added new scanner extensions to detect the following vulnerabilities:

• Remote code execution in ExacqVision Web Service - CVE-2020-9047
• Remote code execution in HP LinuxKI 6.01 - CVE-2020-7209
• LFI in Spring Cloud Config Server - CVE-2020-5410
• JFrog Artifactory Authentication Bypass - CVE-2019-9733
• Remote code execution in Apache Unomi - CVE-2020-13942

A new type of integration is available in the Wallarm Console - Webhook. Webhook is a widespread technology for integrating web services with each other based on callback technology.

The modern approach in information security is the use of specialized tools that are closely integrated with one another. Therefore, one of Wallarm’s priority areas is the support of modern security tools.

You can now send Wallarm WAF events to Webhook or configure conditions and filters for the Trigger to send a particular message to Webhook when conditions are met.

For setting up Webhook integration, only the API URL is required. You can find more details in our documentation.

With the growing complexity of new applications, technology stacks, and evolving attack techniques, we can implement regular improvements in how the Wallarm WAF detects attacks. This month we have added new Scanner rules to detect:

• Open access to the Consul UI web interface. Read the details on our blog
• Server-Side Template Injection in SEOmatic plugin for Craft CMS - CVE-2020-9757
• Reflected Code Injection in Citrix ADC and NetScaler Gateway - СVE-2020-8194
• Remote code execution in WebLogic Server - CVE-2020-14882
• Remote code execution in Liferay CE Portal - CVE-2019-11444

We have also improved the detection of Bash command injection and path traversal attacks in Wallarm WAF.