Radware CWAF collector

[ 1 Overview ] [ 2 Devo collector features ] [ 3 Data sources ] [ 4 Flattening preprocessing ] [ 5 Minimum configuration required for basic pulling ] [ 6 Accepted authentication methods ] [ 7 Run the collector ] [ 8 Collector services detail ] [ 9 Collector operations ] [ 10 Change log ]

Overview

Radware's Cloud WAF Service is a web application firewall that provides continuous adaptive web application security protection and full coverage.

Devo collector features

Feature	Details

Feature	Details
Allow parallel downloading (`multipod`)	`not allowed`
Running environments	`collector server` `on-premise`
Populated Devo events	`table`
Flattening preprocessing	`no`
Allowed source events obfuscation	`yes`
Requires IP whitelisting	`yes`

Data sources

Data source	Description	API endpoint	Collector service name	Devo table	Available from release
Get User Activity Log List	Customers can monitor changes in their Cloud WAF applications using the Activity log. Any change in the configuration is logged in the Activity Log, including the time and the user that performed the change.	`v1/userActivityLogs/reports/`	`user_activity`	`waf.radware.api.user_activity`	v1.0.0
Get Security Events List	Security events are the events reported by WAF when an attack is detected. This allows user visibility to the protected traffic, refinement of false positives, and detailed explanations of security attacks.	`mgmt/monitor/reporter/reports-ext/APPWALL_REPORTS`	`security_events`	`waf.radware.api.security_event`	v1.0.0

For more information on how the events are parsed, visit our page.

Flattening preprocessing

Data source	Collector service	Optional	Flattening details

Data source	Collector service	Optional	Flattening details
Get User Activity Log List	`user_activity`	yes	not required
Get Security Events List	`security_events`	yes	not required

Minimum configuration required for basic pulling

Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.

This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details.

Setting	Details

Setting	Details
username	The username for the Radware API. To find out how to get it, see the Vendor Setup guide.
password	The password for the Radware API. To find out how to get it, see the Vendor Setup guide.

See the Accepted authentication methods section to verify what settings are required based on the desired authentication method.

Accepted authentication methods

Authentication method	username	password

Authentication method	username	password
token	REQUIRED	REQUIRED

Run the collector

Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).

Collector services detail

This section is intended to explain how to proceed with specific actions for services.

Internal process and deduplication method

Data is collected by setting a start date and by pagination. To eliminate duplicates, the date of the last event sent to Devo and the ids of events with the same date are stored.

Devo categorization and destination

All events of this service are ingested into the table waf.radware.api.user_activity. This service has the following components:

Component	Description

Component	Description
Setup	The setup module is in charge of authenticating the service and managing the token expiration when needed.
Puller	The setup module is in charge of pulling the data in a organized way and delivering the events via SDK.

Setup output

A successful run has the following output messages for the setup module:

INFO InputProcess::MainThread -> RadwarePullerSetup(radware_cwaf_collector,radware_input#12345,user_activity#predefined) -> Starting thread
INFO InputProcess::MainThread -> RadwarePuller(radware_input,12345,user_activity,predefined) - Starting thread
WARNING InputProcess::RadwarePullerSetup(radware_cwaf_collector,radware_input#12345,user_activity#predefined) -> The token/header/authentication has not been created yet
INFO InputProcess::RadwarePullerSetup(radware_cwaf_collector,radware_input#12345,user_activity#predefined) -> Setup for module <RadwarePuller> has been successfully executed

Puller output

A successful initial run has the following output messages for the puller module:

Note that the PrePull action is executed only one time before the first run of the Pull action.

INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> RadwarePuller(radware_input,12345,user_activity,predefined) Starting the execution of pre_pull()
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Reading persisted data
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Data retrieved from the persistence: None
WARNING InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> start_time_in_utc has not been found in the configuration, the start date will be: 2023-09-26 08:01:50.653070+00:00
WARNING InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Persistence will be overridden due to the retrieved state is empty
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Running the persistence upgrade steps
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Running the persistence corrections steps
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Running the persistence corrections steps
WARNING InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Some changes have been detected and the persistence needs to be updated. Previous content: None. New content: {'@persistence_version': 1, 'start_time_epoch': 1695715310653, 'last_event_time_epoch': 1695715310653, 'last_ids': []}
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Updating the persistence
WARNING InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Persistence has been updated successfully
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> RadwarePuller(radware_input,12345,user_activity,predefined) Finalizing the execution of pre_pull()
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Starting data collection every 60 seconds
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Pull Started
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Ingesting events from 2023-09-26 08:01:50.653000+00:00 to 2023-09-26 08:02:50.653070+00:00
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Page 0 of 1: Delivered 2 events
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1695715370653):Number of requests made: 1; Number of events received: 2; Number of duplicated events filtered out: 0; Number of events generated and sent: 2; Average of events per second: 0.580.
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Statistics for this pull cycle (@devo_pulling_id=1695715370653):Number of requests made: 1; Number of events received: 2; Number of duplicated events filtered out: 0; Number of events generated and sent: 2; Average of events per second: 0.580.
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> The data is up to date!
INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Data collection completed. Elapsed time: 3.465 seconds. Waiting for 56.535 second(s) until the next one

After a successful collector’s execution (that is, no error logs found), you will see the following log message:

INFO InputProcess::RadwarePuller(radware_input,12345,user_activity,predefined) -> Statistics for this pull cycle (@devo_pulling_id=1695715370653):Number of requests made: 1; Number of events received: 2; Number of duplicated events filtered out: 0; Number of events generated and sent: 2; Average of events per second: 0.580.

Restart the persistence

This collector uses persistent storage to download events in an orderly fashion and avoid duplicates. In case you want to re-ingest historical data or recreate the persistence, you can restart the persistence of this collector by following these steps:

Edit the configuration file.
Change the value of the initial_start_time_in_utc_value parameter to a different one.
Save the changes.
Restart the collector.

The collector will detect this change and will restart the persistence using the parameters of the configuration file or the default configuration in case it has not been provided.

Troubleshooting

This collector has different security layers that detect both an invalid configuration and abnormal operation. This table will help you detect and resolve the most common errors.

Error type	Error ID	Error message	Cause	Solution
`InitVariablesError`	1	`initial_start_time_in_utc` is not set as per the datetime_format : `{datetime_format}`	The date in config is not as per required format	Ensure the date format is correct.
`ApiError`	400	HTTP ERROR 400: Bad request: The server could not understand the request.	The API request is malformed.	Contact the Devo team
`ApiError`	401	HTTP ERROR 401: Unauthorized: Authentication is required and has failed or has not been provided.	The user is not authorized to access the requested service.	Check the permissions and that the credentials are not expired.
`ApiError`	402	HTTP ERROR 500: Server Error: An error occurred on the server.	Unknown server error.	Check that the internet connection works correctly and contact the company that manages the server on which the events are hosted.
`ApiError`	403	Request Error: Received status code `{status_code}`	Unknown API error	Contact the Devo team.
`ApiError`	404	HTTP ERROR 429: Too Many Requests: The user has sent too many requests in a given amount of time.	Too many requests have been sent to the resource.	Check:- That there is only one POD running.- That there are no more computers using the same credentials, Wait several minutes before restarting the collector. If nothing works, contact the Devo team.

Internal process and deduplication method

Data is collected by setting a start date and by pagination. To eliminate duplicates, the date of the last event sent to Devo and the ids of events with the same date are stored.

Devo categorization and destination

All events of this service are ingested into the table waf.radware.api.security_event. This service has the following components:

Component	Description

Component	Description
Setup	The setup module is in charge of authenticating the service and managing the token expiration when needed.
Puller	The setup module is in charge of pulling the data in a organized way and delivering the events via SDK.

Setup output

A successful run has the following output messages for the setup module:

Puller output

A successful initial run has the following output messages for the puller module:

After a successful collector’s execution (that is, no error logs found), you will see the following log message:

Restart the persistence

This collector uses persistent storage to download events in an orderly fashion and avoid duplicates. In case you want to re-ingest historical data or recreate the persistence, you can restart the persistence of this collector by following these steps:

Edit the configuration file.
Change the value of the initial_start_time_in_utc_value parameter to a different one.
Save the changes.
Restart the collector.

The collector will detect this change and will restart the persistence using the parameters of the configuration file or the default configuration in case it has not been provided.

Troubleshooting

This collector has different security layers that detect both an invalid configuration and abnormal operation. This table will help you detect and resolve the most common errors.

Error type	Error ID	Error message	Cause	Solution
`InitVariablesError`	1	`initial_start_time_in_utc` is not set as per the datetime_format : `{datetime_format}`	The date in config is not as per required format	Ensure the date format is correct.
`ApiError`	400	HTTP ERROR 400: Bad request: The server could not understand the request.	The API request is malformed.	Contact the Devo team
`ApiError`	401	HTTP ERROR 401: Unauthorized: Authentication is required and has failed or has not been provided.	The user is not authorized to access the requested service.	Check the permissions and that the credentials are not expired.
`ApiError`	402	HTTP ERROR 500: Server Error: An error occurred on the server.	Unknown server error.	Check that the internet connection works correctly and contact the company that manages the server on which the events are hosted.
`ApiError`	403	Request Error: Received status code `{status_code}`	Unknown API error	Contact the Devo team.
`ApiError`	404	HTTP ERROR 429: Too Many Requests: The user has sent too many requests in a given amount of time.	Too many requests have been sent to the resource.	Check:- That there is only one POD running.- That there are no more computers using the same credentials, Wait several minutes before restarting the collector. If nothing works, contact the Devo team.

Collector operations

This section is intended to explain how to proceed with specific operations of this collector.

Initialization

The initialization module is in charge of setup and running the input (pulling logic) and output (delivering logic) services and validating the given configuration.

A successful run has the following output messages for the initializer module:

Events delivery and Devo ingestion

The event delivery module is in charge of receiving the events from the internal queues where all events are injected by the pullers and delivering them using the selected compatible delivery method.

A successful run has the following output messages for the initializer module:

Sender services

The Integrations Factory Collector SDK has 3 different senders services depending on the event type to delivery (internal, standard, and lookup). This collector uses the following Sender Services:

Sender services	Description

Sender services	Description
`internal_senders`	In charge of delivering internal metrics to Devo such as logging traces or metrics.
`standard_senders`	In charge of delivering pulled events to Devo.

Sender statistics

Each service displays its own performance statistics that allow checking how many events have been delivered to Devo by type:

Logging trace	Description

Logging trace

Description

Number of available senders: 1

Displays the number of concurrent senders available for the given Sender Service.

sender manager internal queue size: 0

Displays the items available in the internal sender queue.

Total number of messages sent: 44, messages sent since "2023-01-10 16:09:16.116750+00:00": 21 (elapsed 0.000 seconds)

Displayes the number of events from the last time and following the given example, the following conclusions can be obtained:

44 events were sent to Devo since the collector started.
The last checkpoint timestamp was 2023-01-10 16:09:16.116750+00:00.
21 events where sent to Devo between the last UTC checkpoint and now.
Those 21 events required 0.000 seconds to be delivered.

To check the memory usage of this collector, look for the following log records in the collector which are displayed every 5 minutes by default, always after running the memory-free process.

The used memory is displayed by running processes and the sum of both values will give the total used memory for the collector.
The global pressure of the available memory is displayed in the global value.
All metrics (Global, RSS, VMS) include the value before freeing and after previous -> after freeing memory

Change log

Release	Released on	Release type	Details	Recommendations

Release	Released on	Release type	Details	Recommendations
`v1.0.0`	Aug 19, 2024	NEW FEATURE	`-`	`Initial version`