radware/alteon
Vendor | Radware, Inc. |
Author | CrowdStrike |
Version | 1.2.0 |
Minimum LogScale Version | 1.86.0 |
Radware's Alteon virtual appliance (VA) is an application delivery controller that does advanced Layer 4 - 7 local server load balancing by:
Managing application traffic across cloud and data center locations and optimizing availability and performance
Providing global server load balancing and SSL offloading and compression
Employing Radware's AppWall Web Application Firewall (WAF).
While Alteon's WAF can be deployed as a standalone device running its own OS or as an integration within the Alteon OS, this parser focuses on the integrated option.
Breaking Changes
This update includes parser changes, which means that data ingested after upgrade will not be backwards compatible with logs ingested with the previous version.
Updating to version 1.0.0 or newer will therefore result in issues with existing queries in for example dashboards or alerts created prior to this version.
See CrowdStrike Parsing Standard (CPS) 1.0 for more details on the new parser schema.
Follow the CPS Migration to update your queries to use the fields and tags that are available in data parsed with version 1.0.0.
Configurations and Sending The Logs to LogScale
See Alteon Syslog Command Knowledgebase Article for information on how to send Alteon logs to Falcon Log Collector.
Installing the Alteon Package in LogScale
Find the repository where you want to send the logs, or create a new one.
Navigate to your repository in the LogScale interface, click Settings and then on the left.
Click
and install the LogScale package for Alteon (i.e. radware/alteon).When the package has finished installing, click Ingest Tokens).
on the left (still under the , seeIn the right panel, click radware-alteon. Be sure to assign the parser to the LogScale Collector Configuration as described in the documentation Sources & Examples
to create a new token. Give the token an appropriate name (e.g.the name of the server and the name of the server the token is ingesting logs for), then assign the token to the parserBefore leaving this page, view the ingest token and copy it to your clipboard — to save it temporarily elsewhere.
Now that you have a repository set up in LogScale along with an ingest token you're ready to send logs to LogScale.
Next, configure the Falcon LogScale Collector to ship the logs from your syslog server into LogScale. Follow LogScale Collector Install Falcon Log Collector and Configure Falcon Log Collector. LogScale Collector documentation also provides an example of how you can configure your syslog datasource, see the Syslog example here: Sources & Examples.
To configure syslog on the datasource, see Alteon Syslog Command Knowledgebase Article.
Verify Data is Arriving in LogScale
Once you have completed the above steps the data should be arriving in your LogScale repository.
You can verify this by doing a simple search for
#Vendor = "radware" | #event.module =
"alteon"
to see the events.