netscaler-web-application-and-api-protection
netscaler-web-application-and-api-protection
API Protection
Contents
Get started with CWAAP 3
Basic operation 7
CWAAP dashboard 7
Notification management 8
Access management 10
Audit logging 11
System configuration 11
Bot configuration 22
Policy configuration 28
Asset configuration 36
SSL certification 38
Analytics 41
Alerts 42
Routed 43
Assets 44
WAF 46
Enrichment 50
Violation logs 55
Bot 58
Bot dashboard 58
Bot logging 60
Events 62
FAQ 63
NetScaler Web Application and API Protection (CWAAP) is a comprehensive and easy‑to‑use cloud
service that offers protection against security attacks.
CWAAP, is cloud service with 14 points of presence (PoPs) across the world, CWAAP
offers a consistent security posture across all clouds and private
data centers, with a low latency and application responsiveness.
Built on NetScaler Web App Firewall and enhanced with volumetric DDoS protection and expanded
machine learning capabilities, the service allows IT to:
• Define application and API‑specific security to safeguard against the OWASP’s top 10 and zero‑
day attacks.
• Apply one of the largest scrubbing networks to protect applications from large DDoS attacks.
• Reduce security configuration errors and simplify visibility and governance across multi‑cloud
environments.
• Configure rules and policies and adjust them as application security requirements change.
• Secure applications fast wherever they are deployed without more infrastructure or operational
complexity.
• Scale in minutes with simple license upgrades.
The cloud‑based solution keeps your applications safe as you migrate workloads from on‑premises
to cloud or among public clouds.
Note:
If you are a new user, you can request for a CWAAP trial or demo. Please contact your Citrix
account manager, or see our NetScaler Web Application and API Protection product page.
Benefits
NetScaler Web Application and API Protection service offers the following benefits to customers:
NetScaler Web Application and API Protection is simple to deploy and easy to configure across multi‑
cloud environments—all from a single pane of glass. Protect any application, anywhere, with a holis‑
tic security approach that provides volumetric DDoS protection with the NetScaler Web App Firewall
solution.
CWAAP DDoS and WAF protection for web applications and APIs
CWAAP provides security protection against the following WAF and DDoS attacks.
• SQL injection
• Cross‑site scripting (cross‑site scripting)
• Cross‑site request forgery (CSRF)
• Buffer overflow
• Form/hidden field manipulation
CWAAP mitigates attacks and protects your Web Server and Web Services
• SYN floods
• NTP Amplification
• SSDP Amplification
• DNS Amplification
• Chargen Amplification
• SNMP Amplification
• Memcached Amplification
Understanding NetScaler Web Application and API Protection and its features
CWAAP portal is a cloud‑based analytics solution that enables you to monitor and troubleshoot se‑
curity incidents. The solution provides personalized experience, greater automation, and real‑time
analytics that you can quickly act upon. Following are the features available on the CWAAP portal:
CWAAP features are available under four categories, basic operations, system configuration, analytics,
and events.
Basic operations. You can access CWAAP either using the API or GUI. Once you log on to the portal, you
can access the Account Information module on the left pane to set up user accounts, manage existing
accounts, manage user notifications. For more information, see CWAAP Basic Operation topic.
System configuration. You can access the Configuration module on the left pane for system configu‑
rations such WAF policies, network assets, and associate SSL certificates. For more information, see
CWAAP System Configuration topic.
Analytics. The Analytics module enables you to monitor data related traffic scrubbed, traffic routed,
traffic violations, and asset configuration. For more information, see CWAAP Analytics topic.
Events. Displays events triggered when CWAAP detects security attacks. When using different event
logs generated by hosts, devices, applications, and databases, network traffic and its vulnerabilities,
the CWAAP capability provides deep visibility and analytics to address the most demanding security
requirements. For more information, see CWAAP Events topic.
For a quick demo, see NetScaler Web Application and API Protection demo.
Basic operation
The following sections enable you understand the basic system operations that you can perform on
CWAAP cloud service.
• Access management
• Notification management
• Audit logging
CWAAP dashboard
The dashboard page provides a snapshot view of your traffic analyzed by CWAAP. You can specify the
time window you want to view (1 hr, 3 hr, 1 day, 7 day, 30 day, 90 day). Also, you can view this traffic
in real‑time by enabling the Real‑Time Data flag on the top right corner of the chart.
The dashboard displays the following data points for your user account:
• Packets/Sec In – Total traffic directed to the SiteProtect NG Platform in Packets Per Second
These data points are represented in a circular chart displaying the Maximum (outer ring), ninety‑fifth
Percentile (middle ring), Average (inner ring). This data is also displayed in a line chart which can be
configured to display any or none of these data points by clicking the labels in the legend below the
chart.
Notification management
You can configure notifications on the CWAAP portal so that you can stay informed about various
events via Email, Slack, or Webhook.
Note:
The account level notifications are typically used to send notifications to a SOC, NOC, or other
distribution lists and also for sending emails to individuals.
1. Click your user name and select Management from the drop‑down menu.
2. From the Account Management page, click Notifications, and then select Configure.
3. The Configure Notifications page is separated into Email, Slack, and Webhooks allowing you
to customize the types of notifications you want to receive per notification type.
1. click your user name in the upper right‑hand corner, and then select Your Profile from the drop‑
down menu.
Or
1. If you are still on the Account Management ‑> Configure Notifications section, click edit your
profile link at the top of the screen.
2. The Edit Profile page has a section for Email Notifications similar to the Account Level Con‑
figurations section, where you can use the toggle On/Off buttons to enable or disable specific
notifications are sent to your email address (that is listed at the top of the screen).
3. click Save.
• Email Addresses ‑ Provide a valid email address or provide multiple valid emails addresses
separated by a comma.
• Slack ‑ Enter the Slack Webhook URL and Slack Channel to receive notifications.
• Webhooks ‑ To configure Webhook notifications, see the CWAAP Portal Notification Webhooks
page.
Each notification method lists the various types of notifications that you receive when you enable
the On/Off toggle button. Following is a list of different notification types you can enable for your
account.
• D&A Alert (High) ‑ A notification sent when high alert is triggered. You receive one notification
per alert.
• D&A Alert (Medium) ‑ A notification sent when a medium alert is triggered. You receive one
notification per alert.
• D&A Alert (Low) ‑ A notification sent when low alert is triggered. You receive one notification
per alert.
• D&A Flow Up/Down ‑ A notification is sent when flow records are not received from one of your
routers. You receive notification per router when flow is down, and notification per router when
flow resumes.
• Proxy Certificate Expiration ‑ A notification sent when one of your SSL certificates are expiring
soon. You receive one notification per expiring SSL certificate.
• Event Start ‑ A notification sent when mitigation begins. You receive one notification per attack.
• Event End ‑ A notification sent when mitigation ends. You receive one notification per attack.
Once you have selected all of your desired Notification methods and types, click Save at the bottom
of the screen.
Access management
After you have logged into the portal, click CWAAP from the dashboard. Then, click <Your Name
> from the upper‑right corner of the page. Select Management from the drop‑down menu.
Note: Only account administrators and CWAAP administrators can modify a user account.
From the Account Management screen, select Users from the left navigation bar. The Users list page
appears.
From the Account Management page, select the user you want to update. A highlight of the user profile
will be displayed on the right side of the screen. The profile identifies the user, the roles they have for
each product, and a short list of the user’s activity history. At the top of the profile, there are two
action buttons (Send Email and Edit). The Send Email allows you to contact the user directly through
the portal. To make updates to the user account information, you can use the edit option.
Note:
To log in to the portal, third party cookies must be enabled. Please instruct new users to disable
third party cookies. It is necessary for users to enable cookies to access the portal.
From the Account Management screen, click Users from the left navigation bar. The user list displays.
Select <User’s Name> you want to update. A details message box appears on the right side
of the screen. Select <Edit Icon> and update the status of the user by using the toggle
switch to enable or disable. When you are done, click Save.
Audit logging
System configuration
• Select one of the Proxy configurations by clicking the associated Configure WAF Profile. The
WAF Policy Editor will be displayed.
• assigns the policy options you want to create for your profile. Details for the policies are shown
in the tables below.
• Once you have provided all the policy information, click the submit button at the bottom right
of the screen.
From the WAF Profile page, click “Edit” next to the host name field of the configuration you want to
update. The update configuration screen will be displayed. Here you can make any changes you want
make and click Save to submit the updated configuration. From this screen, you can also Delete the
configuration by selecting the “Delete” button at the top right of the screen.
Enable WAF
Before you can create and configure your Web Application Firewall (WAF) Policies, you must first en‑
able WAF for your account, and select the type of WAF Policy you want to configure.
From the Edit Account page, navigate down to the Services section. For WAF to be enabled for the
account, the Proxy settings have to be Enabled. If they are Disabled, the options to configure and
customize the basic WAF settings will be removed.
• Disabled
• Basic Application Security (Basic WAF)
• Advanced Application Security
Once you have selected the WAF type, the WAF Signatures default to 3, unless you select another
option. You can opt to enable any other Proxy and WAF settings, but click the Save button when you
are done.
To access the Web Application Firewall (WAF) Profile, select Configuration from the left‑hand naviga‑
tion panel, and then click Policies, and then click WAF Profile tab.
If there are no WAF Policies configured, or you want to create a WAF Policy, you must first configure a
Proxy. To find more details on how to configure a Proxy, please use the following help file DNS Proxy
Configuration.
The WAF profile page has security checks available under three categories ‑ Core, Advanced, and XML.
The core security checks apply to any aspect of web security that either does not involve content or
is equally applicable to all types of content.
1. HTML SQL Injection. The CWAAP HTML SQL Injection check provides special defenses against in‑
jection of unauthorized SQL code that might break the security. If CWAAP detects unauthorized
SQL code in a user request, it either transforms the request, to render the SQL code inactive, or
blocks the request.
2. HTML cross‑site scripting. The HTML Cross‑Site Scripting (cross‑site scripting) check examines
both the headers and the POST bodies of user requests for possible cross‑site scripting attacks.
If it finds a cross‑site script, it either modifies (transforms) the request to render the attack harm‑
less, or blocks the request.
3. CSRF Settings. The Cross Site Request Forgery (CSRF) settings check each web form sent by
a protected website to users with a unique and unpredictable FormID, and then examines the
web forms returned by users to ensure that the supplied FormID is correct. This check protects
against cross‑site request forgery attacks. This check applies only to HTML requests that contain
the web form, with or without data. It does not apply to XML requests.
4. Buffer overflow. The Buffer Overflow check detects if there is buffer overflow on the web server.
If CWAAP detects a URL, cookies, or header are longer than the configured length, it blocks the
request because it can cause a buffer overflow
The advanced security checks examine web form data to prevent attackers from compromising your
system by modifying the web forms on your websites or sending unexpected types and quantities of
data to your website.
1. Cookie consistency. The Cookie Consistency check examines cookies returned by users, to ver‑
ify that they match the cookies that your website set for that user. If you modify a cookie, the
cookie is ripped from the request before it is forwarded to the web server. You can also con‑
figure the Cookie Consistency check to transform all of the server cookies that it processes, by
encrypting the cookies, proxying the cookies, or adding flags to the cookies. The check applies
to requests and responses.
2. Field consistency. The Form Field Consistency check examines the web forms returned by users
of your website, and verifies that web forms were not modified inappropriately by the client.
This check applies only to HTML requests that contain the web form, with or without data. It
does not apply to XML requests.
3. Field format. The Field Formats check verifies the data that users send to your websites in web
forms. It examines both the length and type of data to ensure that it is appropriate for the form
field. If the Web App Firewall detects inappropriate web form data in a user request, it blocks
the request.
4. Content type. Web servers add a Content‑Type header with a MIME/type definition for each
content type. Web servers serve many different types of content. For example, standard HTML
of type text/html MIME. JPG images are assigned content types. A normal web server can
serve different types of content, all defined in the Content Type header by type MIME/type.
5. HTTP RFC profile. NetScaler Web App Firewall inspects the incoming traffic for HTTP RFC com‑
pliance and drops any request that has RFC violations by default. However, there are certain
scenarios, where the appliance might have to bypass or block a non‑RFC compliance request.
In such cases, you can configure the appliance to bypass or block such requests at global or
profile level.
6. Deny URL. The Deny URL check examines and blocks connections to URLs that hackers com‑
monly access. This check contains a list of URLs that are common targets of hackers or mali‑
cious code and that rarely if ever appear in legitimate requests. You can also add URLs or URL
patterns to the list. The Deny URL check prevents attacks against various security weaknesses
known to exist in the web server software or on many websites.
7. POST body limit. Limits the request payload (in bytes) inspected by Web Application Firewall.
The XML Protection checks examine requests for XML‑based attacks of all types.
The XML security checks are as follows:
1. XML SQL Injection. The XML SQL injection check examines the user requests for possible XML
SQL Injection attacks. If it finds injected SQL in XML payloads, it blocks the requests.
2. XML cross‑site scripting. The XML Cross‑Site Scripting check examines the user requests for
possible cross‑site scripting attacks in the XML payload. If it finds a possible cross‑site scripting
attack, it blocks the request.
3. XML format. The XML Format check examines the XML format of incoming requests and blocks
those requests that are not well formed or that do not meet the criteria in the XML specification
for properly formed XML documents.
4. XML SOAP fault. The XML SOAP fault check examines responses from your protected web ser‑
vices and filters out XML SOAP faults. The detection prevents leaking sensitive information to
attackers.
5. Web service interoperability. The Web Services Interoperability (WS‑I) check examines both re‑
quests and responses for WS‑I standard, and blocks those requests and responses that are not
in compliance with WS‑I. The purpose of the WS‑I check is to block requests that might not in‑
teract with other XML appropriately. An attacker can use inconsistencies in the interoperability
to attack your XML application.
1. From the Edit Account page, select Disabled to clear your WAF.
a) Turning the Proxy setting OFF will also disable WAF, but we do not recommend this
method.
2. Click the Save button.
3. You will no longer be able to access the Web Application Firewall section of your account when
attempting to access it.
To re‑enable WAF
1. From the Edit Account page, select either Basic or Advanced Application Security from the
drop‑down menu.
2. The WAF Signatures displays the default value of 3.
3. Click Save.
4. Navigate to the Configuration option on the left‑hand navigation panel, select Security, and
then Web Application Firewall.
5. Click pencil icon to edit the WAF policy.
6. Click enable (“lock” icon).
a) All of your previously saved configurations will be applied.
7. Click Save Changes.
Given the sheer volume of traffic CWAAP examines, it is critical for our customers to understand the
traffic patterns and types that they are experiencing. Enabling certain counter measures or features
can actually be detrimental to a customer by creating false positives, which might require manual
research and review. By enabling the CWAAP Learning feature, a complete traffic
pattern can be analyzed, which then makes creating a Relaxation Rule that would prevent
specific traffic patterns from being blocked painless and manageable.
Once the Learning behavior is actively monitoring traffic for the specified Protection Type, a compre‑
hensive list of rules with its count appears. Once you have reviewed the list, if there are any entries
that must not be blocked, or are not malicious, you can add them to the Relaxation section to prevent
them from being blocked in the future.
The core selection of the counter measures is the most commonly recommended and applied collec‑
tion of counter measures to apply to your WAF policy.
When expanding the HTML SQL Injection counter measure, the following features and customization
options will be available.
• Learning ‑ When set to On, traffic patterns are analyzed which can enhance the Relaxation Rules,
or identify reoccurring threats.
• Alert Threshold ‑ A configurable threshold (value) level that once reached (or exceeded), will
begin to send alerts for the violations being triggered.
When expanding the HTML XSS Counter measure, the following features and customization options
are available.
• Check Complete URLs ‑ You can turn this feature On or Off to require the counter measure to
check the full URL of the offending traffic.
• Relaxation Rules ‑ Relaxation rules can be manually created by clicking the Add button or di‑
rectly added from the Learning section.
• The checkmark icon allows for the multi‑selection of configured Relaxation Rules, which can
then be removed in bulk.
• Learning ‑ When set to On, traffic patterns are analyzed which can enhance the Relaxation Rules,
or identify reoccurring threats.
• Alert Threshold ‑ A configurable threshold (value) level that once reached (or exceeded) begins
to send alerts for the violations being triggered.
CSRF Settings
When expanding the HTML cross‑site scripting counter measure, the following features and customiza‑
tion options are available.
• Alert Threshold ‑ A configurable threshold (value) level that once reached (or exceeded), will
begin to send alerts for the violations being triggered.
• Relaxation Rules ‑ Relaxation rules can be manually created by clicking the Add button or di‑
rectly added from the Learning section.
• The checkmark icon allows for the multi‑selection of configured Relaxation Rules, which can
then be removed in bulk.
• Learning ‑ When set to On, traffic patterns are analyzed which can enhance the Relaxation Rules,
or identify reoccurring threats.
Buffer Overflow
In contrast to the additional features and customization options of the HTML SQL Injection counter
measure, the Buffer Overflow has a more simplistic configuration setup.
• Max URL Length ‑ Configure the maximum URL length that can be allowed before triggering a
violation.
• Max Cookie Length ‑ Configure the maximum Cookie string length that can be allowed before
triggering a violation.
• Max Header Length ‑ Configure the maximum (raw) Header Length that can be allowed before
triggering a violation.
• Alert Threshold ‑ A configurable threshold (value) level that once reached (or exceeded), will
begin to send alerts for the violations being triggered.
Each counter measure is slightly unique in the customization and configuration setup that can be set.
The Counter measures section of the WAF Profile provides a collection of custom counter measures
that can quickly and easily be applied to your policy.
Each counter measure has a quick access bar that allows you to select from three options to determine
how your policy must implement the selected counter measure.
• None ‑ The default setting for any new policy, which indicates the specified counter measure is
not being implemented.
• Log ‑ If a violation is detected, the action (traffic) is allowed, but the incident is logged and saved
for review.
• Block and Log ‑ If a violation is detected, the action (traffic) is denied, and the details of the
incident is saved for review.
The advanced counter measures feature require more knowledge of your traffic patterns and config‑
uration methods.
The XML counter counter measures require more knowledge of your XML traffic patterns and configu‑
ration methods.
XML SQL Injection An XML SQL attack injects source code into a
web application, often causing it to be
interpreted and run as a valid SQL query, which
is then able to perform a database operation
with malicious intent. The XML SQL Injection
countermeasure reviews XML payloads for
inappropriate or injected SQL content.
XML XSS The XML cross‑site scripting (cross‑site
scripting) countermeasure is designed to
prevent cross‑site scripting In essence, this bot
protection counter measure prevents scripts
from accessing or modifying content on a
server in which they are not natively located.
XML Format The XML Format bot protection counter
measure checks the XML format of incoming
requests and blocks those requests that are
not well‑formed, or that do not meet specific
pre‑configured criteria for what a well‑formed
XML request must be.
XML SOAP Fault The XML SOAP Fault counter measure is
designed to check the responses from your
protected web services and filters out XML
SOAP faults. This counter measure can prevent
the leak of sensitive information.
Web Service Interoperability The Web Service Interoperability counter
measure is designed to examine requests and
responses against the WS‑I standard, and then,
block those requests and responses that do
not adhere to the standard.
Bot configuration
To begin the setup for CWAAP bot configuration, you must first have an asset, and a policy configured
to the asset.
1. Select Configuration > Policies.
2. Select a policy and click Edit (pencil and paper).
3. Navigate to Bot Profile tab.
The CWAAP bot profile consists of bot protection techniques and bot signature configuration.
• Protection. List of bot protection techniques that you can configure as part of CWAAP bot con‑
figuration and associate bot actions to it.
• Signatures. A list of counter measures that protect your web application against bot attacks.
Bot signatures help in identifying good and bad bots based on request parameters such as user‑
agent in the incoming request.
The CWAAP bot protection provides a list of bot techniques that you can configure and then enable or
disable it for policy configuration.
Once you have configured your bot technique, you must first enable the technique for it to take effect
on the policy.
Following are the list of bot protection techniques that CWAAP bot configuration supports:
• Allow list
• Block List
• Bot Trap
• Reputation
• Device Fingerprint
• Rate Limiting
• Transactions Processing System (TPS)
• CAPTCHA
Allow list
A customized list of IP addresses, subnets, and policy expressions that can be bypassed as an allowed
list for your bot policy.
Note:
You can configure up to 32 bindings as part of the allow list configuration in a bot profile.
1. Click Add.
2. In the Add to Allow List Bindings page, set the following parameters:
3. Click Commit.
Block list
A customized list of IP addresses, subnets, and policy expressions that must be blocked from accessing
your web applications. The configured traffic is blocked only when you enable the block list feature.
Note:
You can configure up to 32 bindings as part of the block list configuration in a bot profile.
Configure block list bot protection technique by using the CWAAP GUI:
1. Click Add.
2. In the Add to Block List Bindings page, set the following parameters:
3. Click Commit.
Bot trap
The CWAAP bot trap protection technique randomly or periodically inserts a trap URL in the client
response. You can also create a default trap URL and add URLs for that. The URL appears invisible
and not accessible if the client is a human user. However, if the client is an automated bot, the URL
is accessible and when accessed, the attacker is categorized as bot and any subsequent request from
the bot is blocked. The trap technique is effective in blocking attacks from bots.
3. Click Commit.
IP reputation
The CWAAP protection technique detects if the incoming bot traffic is from a malicious IP address. As
part of the configuration, we set different malicious bot categories and associate a bot action to each
of it.
• Botnets
• DoS
• IP
• Mobile Threats
• Phishing
• Proxy
• Reputation
• Scanners
• Spam Sources
Each threat type can either be set to one of the following response types.
• Action and Log – Log the violation details, and take the configured Action type.
• Log – Capture and log any traffic matching the configurations, but take no Action.
• None – Take no action if a match occurs.
After setting the response type, you can configure any one of the following bot actions.
1. Drop
2. Mitigation
3. Redirect
4. Reset
Device fingerprint
The CWAAP bot technique detects if the incoming bot traffic has the device fingerprint ID in the in‑
coming request header and browser attributes of an incoming client bot traffic. The attributes are
examined to determine whether the traffic is a Bot or a human. In this technique, the HTTP request
header “User Agent” is the determining factor.
If the URL is already provided and it matches with the ADC list, then the domain name lookup occurs.
If a matching domain name is identified, the traffic is considered good.
If, however, the domain name returned does not match what the ADC has, then the traffic is dropped
and considered bad.
If a user agent search is completed and a match is found, then the traffic is dropped and designated
bad.
Rate limiting
The CWAAP rate limiting protection technique examines the time frame in which a request is received
from a Client IP Address, Session ID, or configured resource (incoming URL).
Note:
You can configure up to 32 bindings as part of the rate limiting configuration in a bot profile.
Configure rate limit bot protection technique by using the CWAAP GUI:
2. In the Add to Rate Limit Bindings page, set the following parameters:
d) Rate: Configure the Rate value, which determines the number of requests allowed for a
specified time Period
e) Period: Configure the Period value for the selected Rate value in milliseconds (in multiples
of 10)
f) Response: Select the Response Type and if applicable, the associated Action type.
3. Click Commit.
The CWAAP Transaction Processing System (TPS) protection technique examines the number of re‑
quests and percentage increase in requests for a configured time interval to determine if the traffic is
coming from a bot.
Configure Transaction Processing System (TPS) protection by using the CWAAP GUI:
c) % Threshold: Provide the % Threshold value, which will determine the maximum percent‑
age of requests increases allowable within a 30 minute time span.
d) Response: Select the Response type from the drop‑down menu.
i. Action and Log – Log the violation details, and take the configured Action type.
ii. Log – Capture and log any traffic matching the configurations, but take no Action.
iii. None – Take no action if a match occurs.
e) Action: Select a bot action.
3. Click Commit.
CAPTCHA
CAPTCHA is an acronym that stands for “Completely Automated Public Turing test to tell Computers
and Humans Apart”. CAPTCHA is designed to test if an incoming traffic is from a human user or an
automated bot. CAPTCHA helps to block automated bots that cause security violations to web appli‑
cations. In CWAAP, CAPTCHA uses the challenge‑response module to identify if the incoming traffic is
from a human user and not an automated bot.
Note:
Only one binding is allowed per URL. If a binding exists for a URL, and another binding is config‑
ured for the same URL, the previous binding information is removed. You can configure only up
to 30 bindings per bot profile.
3. Click Commit.
Policy configuration
Before you configure Web Application Firewall (WAF) policies, you must first create a WAF policy.
The Responder Policies section provides more flexibility to customers, but does require more de‑
tailed and in‑depth knowledge of your traffic configurations to properly use and incorporate. When
properly used however, the Responder Policies can inspect on any of the fields (values) and operands
and then run a selected action.
1. From the Policy Configuration screen, select the Responder Policies tab.
2. Click the Start button to add a Responder Policy.
3. Provide a Name for the Policy.
4. Select the Action type from the drop‑down menu.
a) Drop
b) Log
c) Redirect To
d) Respond With
5. The Response field will be determined by the Action you selected.
a) Drop. Response is N/A as the traffic are dropped.
b) Log. Response is N/A as the traffic are stored in your log file.
c) Redirect To. Provide the URL to be redirected. The URL must start with a backslash (/).
d) Respond With. Provide the text to display for the response.
6. Select the arrow next to the Matches section to configure exact specifications for your policy.
Complete the following fields
a) Field. Select the field type from the drop‑down list of options.
b) Operand. Select the operand type for the field from the drop‑down menu.
c) Value. Provide the value associated to the Field and Operand combination.
Network controls
The Network Controls section of the Policy allows for Geographical (GEO) blocking of traffic by coun‑
try type. If however, you want to block an entire country, but allow a specific IP address through, you
can configure the Network Controls to do so.
Click the Add button to indicate if an IP / CIDR address should be blocked or allowed. Click the Com‑
mit button when done.
The Network Controls section of the Policy allows for Geographical (GEO) blocking of traffic by coun‑
try type. If however, you want to block a country but allow a specific IP address through, you can
configure the Network Controls to do so.
1. From the Policy Configuration screen, select the Network Controls tab.
2. Click the Add button to configure an IP address that you want to either block, or allow through
3. Provide an IP Address, and then select Not Blocked (allow the IP Address through) or
Blocked (prevent all traffic from the IP Address). Click the Commit button when finished
4. To select an entire country to block traffic from, click in the Blocked Countries drop‑down menu.
Select all of the countries that you want to block traffic from. Click out of the drop‑down menu
when you are finished making your selections
5. To allow list an IP Address from a blocked country, first select the Country to block, and then
add the IP address from that country to allow through, and select the Not Blocked option. The
allow list action happens before a block action is applied.
6. Click Save.
Alert threshold
The Alert Thresholds section allows you to configure a threshold value, that once reached, will send
alerts for the violations occurring for a configured rule.
To configure an Alert Threshold, click the Add button. Select the Dimension from the drop‑down
menu, and then configure the corresponding fields.
To further clarify, alerts will not be sent until the Occurrence count has been exceeded within the time
frame specified. For example, if the occurrence rate was 3, and the timeframe was 60 seconds, alerts
would not be sent until a fourth violation occurred within the 60‑second timeframe.
A pop‑up help window appears with an explanation of a selected Dimension from the drop‑down
menu.
The Alert Threshold section allows you to define a threshold that must be reached before Alerts are
sent for violations that are relevant to your configured rules.
Alert Thresholds are set by Dimension, a KEY, and a designated Count or amount. The threshold alerts
can be synced to SLACK, with a link provided directly to the alert page of the Portal, and being sent
out in email format. The alert notifications will also be displayed on the UI Portal under the bell (no‑
tifications) icon.
It is important to note that Alert Thresholds are also set on the WAF Profile section, per bot protection
techniquesmeasure.
1. From the Policy Configuration screen, select the Alert Thresholds tab.
2. Click Add.
3. Select the Dimension from the list of drop‑down menu options. Each dimension selection pro‑
vides a brief explanation at the top of the pop‑out window.
a) More fields are determined by the Dimension type you select.
4. Complete any additional fields that appear based on the Dimension type selected.
5. Select the number of Occurrences. This determines the threshold limit that must be reached
for a violation to occur, and a notification to be sent.
6. The Timeframe by default stays at 60 seconds.
7. Click the Commit button when you are finished customizing the Application Security Threshold.
8. Click the Save button when you are done adding Alert Thresholds
Trusted sources
The Trusted Sources section helps to configure a list of IPs that can be reliably used for learning traf‑
fic data and generate recommendations for relaxation. If Trusted Sources are not configured, traffic
from all the sources will be used for learning and not providing appropriate recommendations for
relaxation.
1. Click Add to configure a new Trusted Source. Select whether the Trusted Source is going to be
Enabled or not, and then provide the IP Address/CIDR. The Description field is an optional field
that can be filled using free text.
2. Click Commit when you are done.
3. Click Save.
Assets
The Assets tab displays any asset that this policy is currently assigned to. If there are any associated
assets, you can remove them which will cause each asset to undergo a provisioning process in which
rules and configurations might be temporarily disabled.
If no Assets are associated with your policy, the Associated Assets drop‑down menu displays “0 Se‑
lected”. Select an Asset to associate with your policy.
To remove an associated Asset, hover over the drop‑down menu and click the Minus button next to
the Asset you want to remove, or, click in the drop‑down menu and click a highlighted Asset to remove
it.
The counter measures section provides a list of common protection types and methods for users to
select from.
1. Expand each bot protection techniquesmeasure to configure the required values. Each bot pro‑
tection techniquesmeasure can be set to one of the following statuses.
a) Relaxation Rules – You can manually enter the values that allow traffic matching the cri‑
teria through. If Learning was enabled, you can click the + (plus) Icon next to an entry to
apply it directly to the Relaxation Rules.
b) Learning – Learning must be enabled for each bot protection techniquesmeasure before
data can begin to be captured. Once traffic is actively being monitored, a list of blocked
rules will be returned that you can review for accuracy.
3. To configure the Relaxation Rules, click the Add button, and then complete the fields that ap‑
pear in the pop‑up window. Click Commit when finished.
4. To enabled Learning, select the OFF / ON option for your desired configuration.
5. Click Save.
Signatures
The Signatures section allows you to designate specific, configurable rules to simplify the task of pro‑
tecting your websites against known attacks. A signature represents a pattern that is a component of a
known attack on an operating system, web server, website, XML‑based web service, or other resource.
Standard signatures
The Standard Signatures section displays a preconfigured set of literal and Perl Compatible Regular
Expressions (PCRE) keywords and special strings used to protect against common web vulnerabilities.
These configured signatures cannot be edited as they are our default configurations.
1. Select the Signatures tab, and then select the Standard Signatures option.
2. The Configured Signatures section displays any Signatures that have been selected or added to
the WAF Profile Policy you are currently viewing or creating.
a) For a new policy, this section is empty.
3. In the Signatures Pool section, you see the list of pre‑configured signatures that we have created
for you. You can use the arrows or page number options to view more signatures, or use the
Filter option if you are looking for a specific signature.
a) The filter option searches for your criteria across each field (ID, Category, Description, Ref‑
erences), and return the results accordingly.
4. Click the View icon to see a simplified overview of the Signature Pool, or click the Add
to Add the Signature Pool to your Configured Signatures section.
5. Click the Save button once you have added your desired signatures
Custom signatures
The Custom Signatures section allows you to craft custom signatures to protect against attacks and
vulnerabilities.
Once you have created your CWAAP profile, the next step is to apply it to an asset so that your config‑
uration can go into effect.
1. From the Configuration section on the left‑hand navigation menu, select Assets.
2. Select the Pencil Icon for the Asset that you want to add the policy to. If you do not have an
Asset already created, please see our Guides on how to Create an Asset.
3. Select the Policies tab.
4. From the drop‑down menu, select your newly created Policy name.
a. If you do not see the policy name listed, please refresh and try again as the provisioning
period can take a few minutes.
5. Click the Save button.
Once your CWAAP policy has been applied to a policy, please allow a few minutes for provisioning to
occur.
Once a Policy has been created, you can easily edit any of the existing configurations. However,
changes to a Policy that has been associated to an Asset causes a provisioning period to occur which
can have a temporary impact on your traffic configuration.
1. From the Configuration section on the left‑hand navigation menu, select Policies.
2. Click the Pencil Icon next to the policy you want to edit.
3. Navigate through each of the Policy Configuration tabs to make changes, and click the
Save button after making changes on any/all tabs.
If you need to remove a CWAAP Policy from an Asset, there are several ways in which you can accom‑
plish this.
Note:
1. From the Configuration section on the left‑hand navigation menu, select Policies.
2. Click the Pencil Icon next to the policy you want to delete.
3. Click Delete.
From the Policy, you can disassociate the Assets that the policy is assigned to, or disable the WAF
Profile.
1. From the Configuration section on the left‑hand navigation menu, select Policies.
2. Click Pencil Icon to edit the policy.
3. On the WAF Profile tab, clear the box under the “Apply WAF Profile to Policy?” section to Ignore.
This disables the WAF profile.
OR
Edit an asset
From the Asset section, you can edit a selected Asset and remove the Policy.
1. From the Configuration section on the left‑hand navigation menu, select Assets.
2. Click the Pencil Icon next to the asset you want to edit.
3. Select Policies tab.
4. Hover over the drop‑down menu and click Minus Icon to remove the associated Policy.
5. Click Save.
Asset configuration
From the CWAAP NG Dashboard, select the Configuration option at the left side of the screen – A new
set of options become available. Select Proxy from the list. The list of configured proxy services dis‑
plays, if any exist.
1. Click the Configure New Proxy button at the top right of the screen. The Configure New Proxy
screen will be displayed.
2. Provide the Proxy Name – The host name that you must proxy.
3. Enter the front end Port and bind it to a corresponding back‑end Origin Server, Port, and Proto‑
col. Back‑end Origin Servers can be an IP Address, CNAME, or host name and Multiple back‑end
Services per VIP.
Note:
Matching back‑end ports load balance between the back‑end services using a ‘Least Connection’
method.
1. Once you have entered all the host information, you must assign the Advanced Options for your
Proxy configuration.
a) LoadBalancer Balance Method: Indicate which option you want to use for load balancing.
You have the following options for load balancing.
i. Least Connection: Selects the service with the least number of active connections to
ensure that the load of the active requests are balanced on the services.
ii. Round Robin: Responds to DNS requests not only with a single potential IP address,
but with one out of a list of potential IP addresses corresponding to several servers
that host identical services. The list is cycled through in a “round‑robin” style, select‑
ing each address and moving onto the next for subsequent requests.
iii. Least Response Time: Selects the service with the least number of active connections
and the least average response time.
iv. Least Bandwidth: Selects the service that is currently serving the least amount of traf‑
fic, measured in megabits per second (Mbps).
v. Least Packets: Selects the service that has received the fewest packets in the last 14
seconds.
vi. Least Request: Selects the service that has received the fewest requests in the last 14
seconds.
From the Proxy Assets screen click the “Edit Icon” next to the host name field of the configuration you
want to update. The update configuration screen will be displayed. Here you can make any changes
you want make and click Save to submit the updated configuration. From this screen, you can also
Delete the configuration by selecting the “Delete” button at the top right of the screen.
SSL certification
1. In the dashboard, select Configuration ‑> Security ‑> SSL Certificates on the left navigation
bar.
2. The SSL Certificates page shows all the active SSL Certificates associated with your account.
4. A prompt window appears allowing you to provide the SSL Certificate information:
• Private Key – Upload or paste the Private Key information. Currently accepts either 2048
bit or 3072 bit RSA key in the PEM format.
• Private Key Password (optional) – Provide the password associated with the Private Key
• Public Certificate Chain – Detect, Upload, or Paste the Public Certificate. If you choose
the Detect option, provide the publicly accessible HTTPS URL. Otherwise, upload or paste
your public server certificate, followed by all intermediate certificates, in the PEM format.
SSL requirements
The minimum requirements for CWAAP SSL certificates are RSA 2048 bit or 3072 keys. This is a require‑
ment of the FIPS devices.
To submit your SSL certification to the portal, you need the following information:
• Private Key
• Private Key Password
• Public Certificate Chain
You can upload your Private Key and your Public Certificate Chain. Also, you can also detect your
Public Certificate Chain by providing the URL. You should also provide the Private Key Password, so
the SSL certificate can be used.
There are four different ways to present SSL Certificates and their components:
1. PEM. Governed by RFCs, it’s used preferentially by open‑source software. It can have various
extensions (.pem, key, .cer,.cert, more)
2. PKCS#7 or P7B. An open standard used by Java and supported by Windows. Does not contain
private key details.
3. PKCS#12 or PFX. A Microsoft private standard that was later defined in an RFC that provides
an enhanced security versus the plain‑text PEM format. The format might contain the private
key material. It’s used preferentially by Windows systems, and are freely converted to the PEM
format by using openssl.
4. DER. The parent format of PEM. It’s useful to think of it as a binary version of the base64‑encoded
PEM file. Not routinely used by much outside of Windows.
Note:
Cirix highly recommends you to convert the .pfx files on your own machine using OpenSSL so
you can store the private key.
Use the following OpenSSL commands to convert the SSL certificate in different formats on your own
machine:
1. Convert DER to PEM: openssl x509 -inform der -in certificate.cer -out
certificate.pem
2. Convert P7B to PEM :: openssl pkcs7 -print_certs -in certificate.p7b -out
certificate.cer
3. Convert PFX to PEM :: openssl pkcs12 -in certificate.pfx -out certificate.
cer –nodes
Alternatively, you can use the free SSL converter available at SSL Shopper.
From the Proxy Assets screen click the “Edit Icon” next to the host name field of the configuration you
want to update. The update configuration screen displays. Here you can make any changes you want
make and click Save to submit the updated configuration. From this screen, you can also Delete the
configuration by selecting the “Delete” button at the top right of the screen.
To test your website using your own domain name BEFORE DNS propagation has completed, you can
use your local computer’s HOSTS file. Your computer uses the entries in your HOSTS file FIRST before
it tries to use your IPS to look up the DNS information for your domain.
The HOSTS file is a special file on your workstation computer that stores the IP address and name
information. You must check the file before DNS, so if you place an entry in this file it supersedes
anything set in DNS. This feature is useful in testing websites as it allows you to control which IP your
local computer visit regardless of the DNS configuration.
The format of the hosts file is simple. Each line has an IP address and a host name separated by one
or more spaces. By default, hosts files typically contain entries for “localhost” and text describing the
file usage. It is best not to change the description.
Example:
1 1.2.3.4 example.com
2 1.2.3.4 www.example.com
3 <!--NeedCopy-->
Windows
1. From the Start drop‑down list, search for “Notepad” (Win 8, 10) or navigate to: “All Programs ‑>
Accessories ‑> Notepad” (Win XP, Vista, 7).
2. Right‑click Notepad and select the Run As Administrator option.
3. In Notepad, click “Open” and select the file option. C:\\Windows\\System32\\Drivers\\
etc\\hosts.
4. Edit the file and click Save.
Linux
When you are finished testing, remember to remove the custom lines that you added to your
Hosts file.
Analytics
The analytics page enables you to view the analytics details. Following are the options:
Attack map
This is a geographical representation of web attacks related to your network in real‑time. The table
shows the detected IP address, attack types, and source location. For information about the attacks
related to your network, you can select a service type ‑ Routed, Proxy, or WAF.
Routed
The Routed page enables you to view your traffic by IP Address, Autonomous Systems Number, or TCP
Flags by IP. For detailed information about the traffic, select one of the options from the left navigation
bar.
Proxy
The Proxy page enables you to view your traffic by Domain, Geolocation, IP Address, URL Path, or User
Agent.
WAF violations
The WAF Violations section enables you to provide detailed information for your WAF mitigation pro‑
file. The following options are available to view your WAF violations details:
• Violation logs
• Violation types
• Domain targets
• Geolocation
• IP targets
• URL path
Select an option to view detailed traffic information and charts for your WAF profile. You can also
export the information to your records.
Violation logs
The Violation Logs screen displays the list of violations handled by your WAF profile. The default
date range is the last day, however you can assign longer date range by selecting a value from the
date range field. You can also export the Violation log by using the export option.
The Violation list shows a high‑level description of the violation details. For more information, click
the (+) icon for the violation you prefer to examine.
Violation types
The WAF Violation Types page enables you to view all the recent violations by their Violation type. This
page has a table and a graphical representation. You can select the date range to filter your search.
You can also export the graph as an image or PDF and you can export the table as a csv or json file by
using the export option.
Alerts
The Alerts page displays a list of alerts that you have triggered. The alerts are displayed in a table
highlighting the following features:
• Alert Type ‑ Indicates the level of the attack (Low, Medium, High)
• Attack Type – Indicates the type of attack
• Destination – The destination IP
• Start Time – The time the alert was triggered
• End Time – The time the alert traffic was no longer a threat
• Duration – The time the alert was active
• Status – The status of the alert
• Report – A PDF containing a report on the Alert
Traffic
The Traffic page displays a graph representation of the traffic for the monitored network.
Routed
On the Routed page, you can view your traffic by IP Address, Autonomous Systems Number, TCP Flags
by IP address. For more information, select an option from the left pane.
IP address
The IP Address page displays all the recent Routed traffic by the attack source IP address. This page is
categorized into four sections – a table representation and three graphical representations (Line, Pie,
Bar charts). You can set the date range from the following options (1 hr, 3 hr, 1 day, 7 day, 30 day, 90
day). You can also view this information broken down into Aggregate In, Clean In, or Mitigated traffic.
You can also export the graph as an image or PDF and you can export the table as a csv or json file by
selecting the export options.
Autonomous systems
The Autonomous Systems page displays all the recent traffic by the attack source ASN. This page has
four sections – a table representation and three graphical representations (Line, Pie, Bar charts). You
can set the date range from the following options (1 hr, 3 hr, 1 day, 7 day, 30 day, 90 day). You can
also view this information broken down into Aggregate In, Clean In, or Mitigated traffic. You can also
export the graph as an image or PDF and you can export the table as a csv or json file by selecting the
export options.
TCP flags by IP
The TCP Flags by IP page display all the recent TCP Flags for the attack source IP address. This page
has four sections – a table representation and three graphical representations (Line, Pie, Bar charts).
You can set the date range as 1 hr, 3 hr, 1 day, 7 day, 30 day, or 90 day. You can also view the details as
Aggregate In, Clean In, or Mitigated traffic. You can also export the graph as an image or PDF and you
can export the table as a csv or json file by selecting the export options.
Assets
The Assets feature display your network traffic by domain, geolocation, IP address, URL path, or user
agent. For detailed information about your traffic, select an option from the left pane.
Domain
The Domain page displays all the recent attack traffic by the attacks target domain. This page displays
the data in a tabular and graphical format. You can set the date range as, 1 hr, 3 hr, 1 day, 7 day, 30 day,
90 day and so forth. You can also export the graphical data as an image or PDF and you can export the
table as a csv or json file.
Geolocation
The Geolocation page displays all the recent violations by the attack source country. The page displays
the data in a tabular and graphical format. You can set the date range as, 1 hr, 3 hr, 1 day, 7 day, 30 day,
90 day and so forth. You can also export the graphical data as an image or PDF and you can export the
table as a csv or json file.
IP Address
The IP Address page displays all the recent violations by the Destination IP. This page is broken into
two sections – a table representation and a graphical representation. You can set the date range from
the following options (1 hr, 3 hr, 1 day, 7 day, 30 day, 90 day). You can also export the graph as an
image or PDF and you can export the table as a csv or json file by selecting the export option buttons
above the data.
URL Path
The URL Path page displays all the recent violations for the URL path. This page is broken into two
sections – a table representation and a graphical representation. You can set the date range from the
following options (1 hr, 3 hr, 1 day, 7 day, 30 day, 90 day). You can also export the graph as an image
or PDF and you can export the table as a csv or json file by selecting the export options.
From the Assets page, click Edit next to the host name field of the configuration you prefer to update.
The update configuration screen will be displayed. Here you can make any changes you want make
To test your website using your own domain name BEFORE DNS propagation has completed, you can
use your local computer’s HOSTS file. Your computer uses the entries in your HOSTS file first before it
tries to use your ISP to look up the DNS information for your domain.
The HOSTS file is a special file on your workstation computer that stores IP address and name informa‑
tion. This file is checked before DNS, so if you place an entry in this file it supersedes anything set in
DNS. This feature is useful in testing websites as it allows you to control which IP your local computer
visits regardless of what is set in the DNS. The format of the HOSTS file is simple. Each line has an IP
address and a host name separated by one or more spaces. By default, hosts files typically contain en‑
tries for the local host and some comment text describing the file and its use. It is best not to change
any of these lines.
Example:
1 1.2.3.4 example.com
2 1.2.3.4 www.example.com
3 <!--NeedCopy-->
Windows:
1. From the Start menu, search for “Notepad” (Win 8, 10) or navigate to: All Programs ->
Accessories ‑> Notepad (Win XP, Vista, 7)‘.
2. Right‑click Notepad and select Run As Administrator.
3. In Notepad, click “Open” and select the file ‑ C:\Windows\System32\Drivers\etc\hosts.
4. Edit the file and save.
Linux:
Note:
When you are finished testing, remember to remove the custom lines that you added to your
Hosts file.
WAF
The WAF section gives violation details for your mitigation profile. The following options enable you
to view your WAF violation details:
• Violation Logs
• Violation Types
• Domain Targets
• Geolocation
• IP Targets
• URL Path
Select an option to view traffic details and graphical representation for your WAF profile. You can also
export the details for your records.
Violation logs
The Violation Logs page displays all the violations handled by a WAF profile. The default date range
is the last day, however, you can select a date to display one of the range options (Today, Yesterday,
Last 7 Days, Last 30 Days, This Month, Last Month, Custom Range). You can also export the Violation
log by using the export option.
The Violation list is compiled in a table showing the high‑level description of a violation (Action, Date/‑
Time, Source IP, and Reason). To view more information, click (+) for the violation you want to exam‑
ine further.
Violation types
The WAF Violation Types page displays all the recent violations by their Violation type. This page has
two sections – a table and a graph. You can set the date range from the following options (1 hr, 3 hr,
1day, 7day, 30day, 90day). You can also export the graph as an image or PDF and you can export the
table as a csv or json file by selecting the export options
The table view lists all the violation types sorted by the number of requests for each respective request.
The CWAAP violation logs display a comprehensive overview of violations in direct contrast to bot pro‑
tection techniques that have been implemented to log or block specific requests that were captured
for your account.
To access the violation Logs, using the left‑hand navigation menu, select Analytics, then WAF, Logs,
and then violation Logs from the drop‑down list.
Following are the violation log menus available in the drop‑down list.
Application
The Applications drop‑down menu allows for the selection of a custom configured asset (or all Assets)
for your account. By default, the All Assets (Combined) application will be selected.
The Date Range filter provides two methods of customizing the data that is displayed on the WAF
Dashboard.
Clicking on the displayed date range selection will open the pop‑out calendar window, which allows
you to select a beginning and end date, as well as selecting a custom time range as well.
Clicking the calendar icon allows you to quickly navigate through months, as well as years to select
the beginning and end dates. Additionally, you can manually type in the desired date instead of using
the calendar option.
The maximum number of days in the past that can be captured is ninety (90) days from the current
date.
Click the green checkmark icon once you have selected your custom time frame to view the results
Instead of creating a custom time frame for your dashboard results, you can use one of the pre‑
configured quick select date range options. By default, the Dashboard will display the results for the
previous seven days (7D).
• 7D ‑ Displays the result details for the previous seven calendar days (week).
• 30D ‑ Displays the result details for the previous thirty days (calendar month).
The Field and Enter Text options enable custom search filters to be created to display your Violation
Log details.
• All
• Source IP
• Timestamp
• Host
• Country
• User‑Agent
• City
• Action
• Reason
• Domain
• URI
• Transaction ID
• Event ID
• Site
• Signature
Note:
The Violation Logs that are currently displayed on the screen (which includes any configured filters)
can be exported in either a:
1. CSV file
2. JSON output
Clicking on either of the download options will display a greyed‑out cloud icon as the file is compiled.
Once the cloud icon becomes clickable, the file will begin to download
The Violation Log Details table displays a comprehensive overview of the violation that was captured,
with hyperlinked content that will navigate you to the Enrichment section, for additional details.
Additional Features
A brief explanation about the violation, as well as what type of violation was triggered.
View Details
The View Details feature displays a more detailed overview of the violation details. Clicking on the
Policy hyperlink will redirect you to the Configuration ‑ Policies section of your account.
The double paper icon is a copy + paste option, as doing a manual copy and paste of the details may
not work as the details may be truncated on the page.
Add IP Filter
Selecting the Add IP Filter button will add the selected IP address to the Blocklist for the account. On
the pop‑out window, the IP / CIDR address will be listed (which can be edited), as well as an indicator
for Blocked (selected by default), or Not Blocked.
Once you click Save, the IP address filter will be added to your policy (which can be found in the View
Details section).
Selecting the Create Relaxation Rule will add the selected violation log entry to the allowed list for the
account. The Violation Reason will determine the possible configuration settings for the Relaxation
Rule.
Once you click the Save button, the Relaxation Rule will be added to your configured policy (which
can be found in the View Details section
Domain targets
The Domain Targets page displays all the recent violations by the attacks target domain. This page
has two sections – a table representation and a graphical representation. You can set the date range
from the following options (1 hr, 3 hr, 1 day, 7 day, 30 day, 90 day). You can also export the graph as
an image or PDF and you can export the table as a csv or json file by selecting the export options.
Geolocation
The Geolocation page displays all the recent violations by the attack source country. This page has
two sections – a table representation and a graphical representation. You can set the date range from
the following options (1 hr, 3 hr, 1 day, 7 day, 30 day, 90 day). You can also export the graph as an
image or PDF and you can export the table as a csv or json file by selecting the export options.
IP targets
The IP Targets page displays the recent violations by the attack Target IP address. The page has two
sections – a table and a graph. You can set the date range from the following options (1 hr, 3 hr, 1 day,
7 day, 30 day, 90 day). You can also export the graph as an image or PDF and you can export the table
as a csv or json file by selecting the export options.
URL path
The URL Path page displays all the recent violations for the URL path having the most blocked or
logged violations. This page has two sections – a table and a graph. You can set a date from the
following options ‑ 1 hr, 3 hr, 1 day, 7 day, 30 day, 90 day. You can also export the graph as an image
or PDF and you can export the table as a csv or json file by selecting the export options.
Enrichment
The CWAAP WAF enrichment section displays an enhanced overview for a selected destination IP ad‑
dress, Source IP address, or country.
• IP Intelligence Results
• Violation Logs ‑ Graphical Data
• Violation Type ‑ Graphical Data
• Violation Log Details
To display results for a specific field type, use the Select Field drop‑down menu and select one of the
following.
• Destination IP
• Source IP
• Country
In the Search field, provide either IP address or the desired Country to return results for
The Date Range filter provides two methods of customizing the data that is displayed on the WAF
Dashboard.
The displayed date range selection field opens the pop‑out calendar window, which allows you to
select a beginning and end date, and selecting a custom time range as well.
Clicking the calendar icon allows you to quickly navigate through months, and years to select the
beginning and end dates. Also, you can manually type in the desired date instead of using the calendar
option.
The maximum number of days in the past that can be captured is 90 (90) days from the current date.
Click the green checkmark icon once you have selected your custom time frame to view the results
Instead of creating a custom time frame for your dashboard results, you can use one of the pre‑
configured quick select date range options. By default, the Dashboard displays the results for the
previous seven days (7D).
IP Intelligence Results
The IP Intelligence Results section displays an overview of the selected IP Address details. The IP
Intelligence details are powered by the CWAAP IPR (IP Reputation) Service.
Violation Logs
The Violation Logs section displays a graphical representation of the last six days and the number of
violations that occurred per day.
Violation Type
The Violation Type section displays a graphical representation of the offending violation types and
the total number of violations that occurred in correlation to the Violation Log timeframe.
The Violation Log Details table displays a comprehensive overview of the violation that was captured
for the selected IP Address or Country for the date range identified in the Violation Logs graph.
Additional Features
Each Violation Log entry in the table has more features that can be utilized to further enhance the
usage of the Violation Log details.
View Details
The View Details feature displays a more detailed overview of the violation details. Clicking the Policy
URL will redirect you to the Policy Configuration page for the policy that generated the violation log.
The blue “i” icon shows the full path details that might be condensed on the Violation Log Details
screen due to length restrictions.
The double paper icon is a copy + paste option, as doing a manual copy and paste of the details might
not work as the details might be truncated on the page.
Click the Show Raw Headers icon to view all of the Raw Headers.
IP Filter
Selecting the Add IP Filter button will add the selected IP address to the Blocked list for the account.
On the pop‑out window, the IP / CIDR address is listed (which can be edited), as well as an indicator
for Blocked (selected by default), or Not Blocked.
Once you click Save, the IP address filter will be added to your policy (which can be found in the View
Details section).
Relaxation Rule
Selecting the Create Relaxation Rule adds the selected violation log entry to the allowed list for the
account. The Violation Reason will determine the possible configuration settings for the Relaxation
Rule.
Once you click the Save button, the Relaxation Rule is added to your configured policy (which can be
found in the View Details section.
The Responder Policy Logs section displays an overview of Response Policies that have been config‑
ured and triggered.
To access the CWAAP responder policy logs, use the left‑hand navigation menu and select Analytics,
then WAF, Logs, and then Responder Policy Logs.
The Responder Policy Logs filter option has a drop‑down menu that allows you to select any config‑
ured Asset or VIP for your account. By default, the All Assets (Combined) is selected.
The Responder Policy Logs displayed on the screen can be exported into either a .PDF file, or in a JSON
file.
The Responder Policy Log has various default time range configurations, and the option to create a
custom time range to retrieve the Responder Policy Logs.
• Today
• Yesterday
• Last 7 Days
• Last 30 Days
• This Month
• Last Month
• Custom Range
The Responder Policy Log Details table provides an overview of the policy by displaying the following
details.
Each field has a sort option that sorts the results either in ascending or descending order (either al‑
phabetical or numerical depending on the column details).
Name Description
Name Description
URI
Site
Date/Time Displays the time in which the incident
occurred (in UTC).
Violation logs
The CWAAP Violation Logs section displays a comprehensive overview of violations in direct contrast
to counter measures that have been implemented to log or block specific requests that were captured
for your account.
To access the Violation Logs, using the left‑hand navigation menu, select Analytics, then WAF, Logs,
and then Violation Logs from the drop‑down list.
Applications
The Applications drop‑down menu allows for the selection of a custom configured asset (or all Assets)
for your account. By default, the All Assets (Combined) application is selected.
Date range
The Date Range filter provides two methods of customizing the data that is displayed on the WAF
Dashboard.
Clicking the displayed date range selection opens the pop‑out calendar window, which allows you to
select a beginning and end date, and selecting a custom time range as well.
Clicking the calendar icon allows you to quickly navigate through months, as well as years to select
the beginning and end dates. Also, you can manually type in the desired date instead of using the
calendar option.
The maximum number of days in the past that can be captured is 90 (90) days from the current date.
Click the green checkmark icon once you have selected your custom time frame to view the results.
Instead of creating a custom time frame for your dashboard results, you can use one of the pre‑
configured quick select date range options. By default, the Dashboard displays the results for the
previous seven days (7D).
The Field and Enter Text options enable custom search filters to be created to display your Violation
Log details.
• All
• Source IP
• Timestamp
• Host
• Country
• User‑Agent
• City
• Action
• Reason
• Domain
• URI
• Transaction ID
• Event ID
• Site
• Signature
Note:
Export options
The Violation Logs that are currently displayed on the screen (which includes any configured filters)
can be exported in either a:
1. CSV file
2. JSON output
Clicking either of the download options display a grayed‑out cloud icon as the file is compiled. Once
the cloud icon becomes clickable, the file begins to download
The Violation Log Details table displays a comprehensive overview of the violation that was captured,
with hyperlinked content that will navigate you to the Enrichment section, for more details.
More features
Each Violation Log entry in the table has more features that can be selected.
View details
The View Details feature displays a more detailed overview of the violation details. Clicking the Policy
hyperlink will redirect you to the Configuration ‑ Policies section of your account.
The blue “ i “ icon shows the full path details that might be condensed on the Violation Log Details
screen due to length restrictions.
The double paper icon is a copy + paste option, as doing a manual copy and paste of the details might
not work as the details might be truncated on the page.
IP filter
Selecting the Add IP Filter button adds the selected IP address to the Blocked list for the account. On
the pop‑out window, the IP / CIDR address is listed (which can be edited), and an indicator for Blocked
(selected by default), or Not Blocked.
Once you click Save, the IP address filter is added to your policy (which can be found in the View
Details section).
Relaxation rule
Selecting the Create Relaxation Rule adds the selected violation log entry to the allowed (or listed)
list for the account. The Violation Reason will determine the possible configuration settings for the
Relaxation Rule.
Once you click the Save button, the Relaxation Rule is added to your configured policy (which can be
found in the View Details section.
Bot
The bot analytics gives insights about bot attacks and its violations occuring in your web applications.
The bot analytics details you about the bot dashboard details and bot logging details.
Bot dashboard
The bot analytics dashboard provides graphical insights to bot analytics and violation details. You can
access the Bot Dashboard on the CWAAP portal to view the bot analytics.
The dashboard displays the details based on the application that you select from the drop‑down list.
When you select an application, the bot analytics such as violation type, IP address, URL path, or Ge‑
olocation are displayed in graphical format. You can selecta analytics type to navigate the log section.
Applications
The Applications menu allows you to select a configured asset (or all assets) for your account that has
CWAAP Bot enabled. By default, the “All Assets (Combined)” application is selected.
If a selected application has no violation details, the section does not display any graphical data.
The Date Range filter provides two methods for customizing the data to display on the CWAAP Bot
dashboard.
The data range picker icon enables you to select a start and end date or select a custom time range.
The calendar icon allows you to quickly navigate through months, as well as years to select the begin‑
ning and end dates. You can also manually enter a date.
Note:
The maximum number of days in the past that can be captured is ninety (90) days from the cur‑
rent date.
Instead of creating a custom time frame for your dashboard results, you can use one of the pre‑
configured quick select date range options. By default, the dashboard displays results for the last
seven days (7D).
Each of the field types displayed in each section is a clickable link that enables you to navigate to the
Violation Logs section of the CWAAP portal.
Additionally, each of the results per insight chart is sorted in descending order based upon the number
of requests.
Violation types
The Violation Types section displays an insight chart of bot Violations that are captured by bot protec‑
tion techniquesmeasure type and the total number of requests received for each bot violation type.
The Violation Type chart allows you to hover over a colored section to display the violation type and
request count.
Domain target
The Domain Target section displays the IP Address for the domain(s) that were impacted by the cap‑
tured violations, as well as the total number of requests that were captured.
IP targets
The IP Targets section highlights the specific IP addressess that are impacted, within the targeted Do‑
main(s) for the captured violations. Also it displays the total number of requests that each IP address
receives.
URL path
The URL Path section displays various URLs that are targeted and the total number of requests for
each URL path. The blue “i” icon next to a URL displays the full URL path name.
Geolocation
The Geolocation section displays the geographical region of the bot violation and also the number of
requests that are captured.
Bot logging
The CWAAP Bot Logs section displays an overview of counter measures and associated violations that
have been configured and triggered. The log type identifies an entry as either a “Violation” or as “Info.”
Note:
The CWAAP bot configurations do not trigger a violation log entry, as they are not technically
violations. However, these events are included in the “Requests” count on the bot dashboard.
Following is a list of bot protection techniques and its associated log entry.
To view the CWAAP analytics, select Analytics from the left‑hand navigation menu, select BOT, and
then select Logs.
The CWAAP bot logs filter option has a drop‑down menu that allows you to select any configured Asset
for your account. By default, the All Assets (Combined) is selected.
Log types
• All
• Info
• Violation
The Field search menu allows you to select a specific Field or Value type to display the CWAAP results
for.
• All
• Source IP
• Destination IP
• Host
• URI
• counter measure
• Action
• Reason
• Domain
• Profile
• Node
• Transaction ID
• Timestamp
• Country
• City
After selecting the field type, you can provide the matching search criteria in the Enter Text field to
further narrow down your search results.
The CWAAP bot logs displayed on the screen can be exported into either to a PDF or a JSON format.
The results displayed in the Bot Violation Logs section capturex details to identify the violation, pro‑
tection technique and bot action applied for the violation.
Each entry captures the action that was taken (due to bot protection techniques configuration), the
impacted policy, the offending Source IP address, the originating country for the offending IP, and the
reason for the bot protection techniques to occur.
Clicking Application, Source IP, or Country links take you to the Enrichment details page, that displays
the detailed description for each these parameters.
For example, clicking the Source IP address link displays the IP Intelligence Results enrichment page,
and provides identifying information that is associated with the offending IP address.
Events
1. Select Services from the top navigation options, and then click Mitigation Events. A list of all
Mitigation Events for the account is displayed with the following details:
• Account
• Start Date and Time
• End Date and Time
• Duration
• Prefixes
• Status
• Chart
3. Under the Associated Mitigations section, click the green arrow under the More Details section
to view Traffic details.
4. The Dropped Traffic details display the type of bot protection techniquesmeasure using dur‑
ing the mitigation, and how what percentage of traffic was dropped due to that bot protection
techniquesmeasure being implemented.
• The total percentage of traffic dropped will equal 100% to denote the end of the Mitigation
Event.
FAQ
NetScaler Web Application and API Protection is a cloud service compatible from anywhere for
applications to be hosted. NetScaler Web App Firewall solution integrated with DDoS mitigation
service, the combination provides a comprehensive, layered protection stack that proactively
prevents bot‑based volumetric attacks, and threats that target the application layer, such as
SQL, cross‑site scripting, CSRF, session hijacking, data exfiltration and zero‑day vulnerabilities.
NetScaler Web App Firewall monitors, filters, or blocks inbound and outbound web application
traffic that has security attacks.
CWAAP DDoS protection is a DDoS mitigation service. CWAAP scrubs malicious Internet traffic,
allowing clean, legitimate traffic to flow to your infrastructure.
A distributed denial‑of‑service (DDoS) attack is when multiple entities are operating together to
attack one target. DDoS attackers often use the use of a botnet—a group of hijacked internet‑
connected devices to carry out large scale attacks. Attackers take advantage of security vulner‑
abilities to control numerous devices using command and control software.
To exhaust network bandwidth, server resources, or applications in such a way that legitimate
users cannot access a site. The purpose for such attacks, however, can vary widely.
6. What are the common Web Application Firewalls (wAF) techniques of Layer 7 attacks?
• Cross‑site request forgeries (CSRF) trick end users into running state‑change actions on a
web app with which they are authenticated. Such attacks can instigate actions such as
transferring funds or changing email addresses.
• SQL injections are well‑known exploits in which an SQL data is inserted into the query
response from a client.
GraphQL is a data query and manipulation language for CWAAP APIs and a runtime for fulfilling queries
with existing data. GraphQL provides a complete description of existing data and exactly what users
are looking in the CWAAP API schema.
For a complete set of CWAAP API documentation, see NetScaler Web Application and API Protection
GraphQL API Schema Reference PDF. The documentation contains reference APIs, examples, and de‑
scriptions.
marks appearing herein are property of Cloud Software Group, Inc. and/or one or more of its subsidiaries, and may be
registered with the U.S. Patent and Trademark Office and in other countries. All other marks are the property of their
respective owner(s).