AppTrana
Getting Started
Frequently Asked Questions
Product Details
API Discovery Feature
API Request to Purge CDN Data
API Scan Coverage for OWASP Top 10
ASN based IP Whitelisting
Advanced Behavioral DDoS
Analysis page - Access Trend Visualization
Analysis page - Attack Trend Visualisation
Asset Discovery
BOT Protection
Browser Protection
Configure Custom Error Pages in AppTrana
Configuring Custom Error Page in AppTrana
Configuring Custom Error and Maintenance Pages in AppTrana WAAP
Custom Bot Configuration
Customize Application Behavior with Bot Score
DNS Management
Enable and Configure Single Sign-On
Enabling SIEM Integration
False Positive Analysis Report on WAAP
Malware Scanning for File Uploads
Manage WAAP Email Alerts
Origin Health Check Mechanism
Restricted Admin User
Self Service Rules
SwyftComply
WAF Automated Bypass and Unbypass
Whitelist Vulnerabilities on the AppTrana WAAP
Product User Guide
Indusface WAS
Getting Started
Product User Guide
API Security Audit
Application Audit[AA]
Asset Monitoring
Dashboard
Malware Monitoring[MM]
New Reporting Structure
Reports
Settings
Summary
Vulnerability Assessment[VA]
Frequently Asked Questions
Feature Summary
API Key Based - Scan Log Export
AcuRisQ – Risk Management with Advanced Risk Scoring
SIEM Integration with Sumo Logic
WAS Consulting License
WAS Defacement Checks
Indusface WAS Scanned Vulnerabilities
Indusface Newsletter
Indusface Product Newsletter - August 19
Indusface Product Newsletter - February 2023
Indusface Product Newsletter - June 20
Indusface Product Newsletter - March 2022
Indusface Product Newsletter - October 19
Indusface Product Newsletter - October 2021
Indusface Product Newsletter- April 2021
Indusface Product Newsletter- October 2022
Indusface Product Newsletter-January21
Product Newsletter of February 18
Product Newsletter of January 18
Product Newsletter of January 19
Product Newsletter of July 18
Product Newsletter of March 18
Product Newsletter of March 19
Product Newsletter of May 18
Product Newsletter of May 19
WAF Portal Revamp June 18
Zero Day Vulnerability Reports
Vulnerabilities Detected in 2023
Vulnerability Report of April 23
Vulnerability Report of August 23
Vulnerability Report of December 23
Vulnerability Report of February 23
Vulnerability Report of January 23
Vulnerability Report of July 23
Vulnerability Report of June 23
Vulnerability Report of March 23
Vulnerability Report of May 23
Vulnerability Report of November 23
Vulnerability Report of October 23
Vulnerability Report of September 23
Vulnerabilities Detected in 2016
CRS Vs Zero Day Vulnerabilities - August 2016
CRS vs Zero Day Vulnerability - September 2016
CRS vs. Zero Day Vulnerability - December 2016
CRS vs. Zero Day Vulnerability - November 2016
CRS vs. Zero Day Vulnerability - October 2016
Vulnerabilities Detected in 2017
Vulnerability Report of April 17
Vulnerability report for Apr 3rd - Apr 9th 17
Vulnerability report for April 17th - Apr 23rd 17
Vulnerability report of April 10th - April 16th
Vulnerability Report of March 17
Vulnerability report for 27th Feb - 5th Mar
Vulnerability report for Mar 13th - Mar 19th
Vulnerability report for Mar 20th - Mar 26th
Vulnerability report for Mar 27th - Apr 2nd
Vulnerability report for Mar 6th - Mar 12th
Vulnerability Report of February 17
Vulnerability Report of January 17
Vulnerability Report of August 17
Vulnerability Report of December 17
Vulnerability Report of July 17
Vulnerability Report of June 17
Vulnerability Report of May 17
Vulnerability Report of November 17
Vulnerability Report of October 17
Vulnerability Report of September 17
Vulnerabilities Detected in 2018
Vulnerability Report of April 18
Vulnerability Report of August 18
Vulnerability Report of December 18
Vulnerability Report of February 18
Vulnerability Report of January 18
Vulnerability Report of July 18
Vulnerability Report of June 18
Vulnerability Report of March 18
Vulnerability Report of November 18
Vulnerability Report of October 18
Vulnerability Report of September 18
Vulnerability Reports of May 18
Vulnerabilities Detected in 2019
Vulnerability Report of April 19
Vulnerability Report of August 19
Vulnerability Report of December 19
Vulnerability Report of February 19
Vulnerability Report of January 19
Vulnerability Report of July 19
Vulnerability Report of June 19
Vulnerability Report of March 19
Vulnerability Report of May 19
Vulnerability Report of November 19
Vulnerability Report of October 19
Vulnerability Report of September 19
vulnerabilities Detected in 2020
Vulnerability Report of April 20
Vulnerability Report of December 20
Vulnerability Report of February 20
Vulnerability Report of January 20
Vulnerability Report of July 20
Vulnerability Report of June 20
Vulnerability Report of March 20
Vulnerability Report of May 20
Vulnerability Report of November 20
Vulnerability Report of October 20
Vulnerability Report of Sep 20
Vulnerabilities Detected in 2021
Vulnerability Report of April 21
Vulnerability Report of August 21
Vulnerability Report of December 21
Vulnerability Report of February 21
Vulnerability Report of January 21
Vulnerability Report of July 21
Vulnerability Report of June 21
Vulnerability Report of March 21
Vulnerability Report of May 21
Vulnerability Report of November 21
Vulnerability Report of October 21
Vulnerability Report of September 21
Vulnerabilities Detected in 2022
Vulnerability Report of April 22
Vulnerability Report of August 22
Vulnerability Report of February 22
Vulnerability Report of January 22
Vulnerability Report of July 22
Vulnerability Report of June 22
Vulnerability Report of March 22
Vulnerability Report of May 22
Vulnerability Report of November 22
Vulnerability Report of October 22
Vulnerability Report of September 22
Zero-Day Vulnerability Report - December 2022
Vulnerabilities Detected in 2024
Vulnerability Report of April 2024
Vulnerability Report of August 2024
Vulnerability Report of February 2024
Vulnerability Report of January 2024
Vulnerability Report of July 2024
Vulnerability Report of June 2024
Vulnerability Report of March 2024
Vulnerability Report of May 2024
Vulnerability Report of October 2024
Vulnerability Report of September 2024
Security Bulletin
Vulnerabilities 2024
CVE-2024-1071 – Critical Vulnerability in Ultimate Member WordPress Plugin
CVE-2024-4577 – A PHP CGI Argument Injection Vulnerability in Windows Servers
CVE-2024-4879 & CVE-2024-5217 Exposed - The Risks of RCE in ServiceNow
CVE-2024-8517 – Unauthenticated Remote Code Execution in SPIP
Critical Apache OFBiz Zero-day AuthBiz (CVE-2023-49070 and CVE-2023-51467)
Hotjar's OAuth+XSS Flaw Exposes Millions at Risk of Account Takeover
ScreenConnect Authentication Bypass (CVE-2024-1709 & CVE-2024-1708)
Adobe ColdFusion Vulnerabilities Exploited in the Wild
Apache Struts 2 Vulnerability CVE-2023-50164 Exposed
Apache log4j RCE vulnerability
ApacheStructs_VG
CVE-2024-8190 – OS Command Injection in Ivanti CSA
CVE-2024-9264 - Grafana’s SQL Expressions Vulnerability
HTTP/2 Rapid Reset Attack Vulnerability
Multiple Moveit Transfer Vulnerabilities
Oracle WebLogic Server Deserialization
Remote Unauthenticated API Access Vulnerabilities in Ivanti
Unpacking the Zimbra Cross-Site Scripting Vulnerability(CVE-2023-37580)
Table of Contents
- All Categories
- AppTrana
- Product Details
- Custom Bot Configuration
Custom Bot Configuration
Updated by Rama Sadhu
AppTrana WAAP's BOT Protection module blocks or allows requests based on the BOT score of the request source IP. Get more insights on Bot Protection.
Here, the enhancement aims to add flexibility to the BOT module within AppTrana. It will empower the user to customize the custom rules based on the bot score assigned to the request source.
The new capabilities to bot actions are available in Self-Service Rules with newly added parameters and rule actions.
Follow the demo steps to access the custom rules under Self-service Rules:
AppTrana WAAP -> Settings-> “WAF" tab - > Custom Rule Categories-> Create Custom Rules
What’s New!
Request Parameter
Bot score (Source)- Enables users to customize actions based on the bot score of incoming requests. Refer to the "Customize Application Behavior with Bot Score" walk-through for detailed information on bot scores.
Under Rule Action
Captcha | If the rule condition matches, generates a captcha. If the captcha is not solved, the user will continue to see captcha challenges until it is solved. |
Drop | If the request and client meet the rule's conditions, the request isn't sent to the origin server, and the WAF doesn't respond. Each drop is logged and contributes to the anomaly-based scoring mechanism of the bot. |
Crypto Challenge | If the request and client parameters match, a Crypto challenge is presented to the end-user. Like the captcha, the client must solve the crypto challenge to proceed.
This action adds load to the CPU, so it is implemented as a delay mechanism.
|
Increase Bot Score | If the request and client parameters match the conditions defined in the rule, the user is permitted to increase the bot score with a fixed rate – either drastic or marginal.
|
Use Cases for Bot Mitigation
Example 1
You notice that certain user registration requests show patterns indicative of bot activity, such as rapid submissions from the same IP address within a short time frame.
Select the Bot score under the request parameter to set up a custom rule based on the bot score.
Moderate Bot Activity
Condition- Medium bot score range (61 to 80) for suspicious login attempts.
Action - Show CAPTCHA
Login attempts with medium bot scores indicate a moderate likelihood of bot traffic. By displaying a CAPTCHA, you can verify the authenticity of the user before granting access to the platform.
High Bot Activity
Condition: Bot scores indicate a high likelihood of bot traffic (above 90%).
Action: Drop the request or present a Crypto Challenge
With such a high bot score, the traffic is probably from bots. You can prevent potentially malicious activity on your site by dropping the request or presenting a Crypto Challenge.
Example 2
You observe an unusually high volume of requests from the "/home" URL path, which doesn't align with typical user behavior or expected traffic patterns.
Condition: URL matches "/home."
Action: Drop the request.
Example 3
You notice that requests from a specific URL page display abnormal behavior, with a notably high bot score.
Condition: URL is "/api/data" and the bot score falls within the High range
Action: Show Crypt Challenge
Example 4
You notice a surge in suspicious activity originating from requests to a specific URL on your website, indicating potential bot traffic. Follow these steps to set up this URL as bot-generated and take appropriate action:
Condition 1: URL matches "/api/data."
Condtion 2 : Add another match for HTTP methods as a request parameter.
Operate: Equal to "POST" (indicating non-GET requests).
Comparing Value: Options (for any available HTTP methods)
Action: Increase Bot Score.
Threshold: Marginal increase in score (+5).
You can also set up rules for a drastic increase in bot score (+10) for more severe cases of suspicious activity.