Akamai Cloud Web Application Firewall

This package provides a parser for Akamai Security Events Collector logs in JSON format. Ingesting this data to LogScale will allow you to correlate cloud firewall security events with the rest of the log data from your internet-facing infrastructure.

The parser normalizes data to a common schema based on CrowdStrike Parsing Standard (CPS) 1.0. This schema allows you to search the data without knowing the data specifically, and just knowing the common schema instead. It also allows you to combine the data more easily with other data sources which conform to the same schema.

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.

Installing the Package in LogScale

Find the repository where you want to send the Akamai Cloud Web Application Firewall events, or Creating a Repository or View.

  1. Navigate to your repository in the LogScale interface, click Settings and then Packages on the left.

  2. Click Marketplace and install the LogScale package for Akamai Cloud Web Application Firewall (i.e. akamai/asec).

Configurations and Sending the Logs to LogScale

  1. To get logs from Akamai into LogScale, configure the to send logs into an S3 bucket.

  2. Then you need to configure LogScale to collect data from AWS S3 buckets using the asec-json. See the documentation for cloud: Ingesting Data from AWS S3 and self-hosted Ingesting Data from AWS S3 deployments to send logs directly from S3 bucket into LogScale repository.

Refer to Akamai log file structure to get additional details about recorded events.

Verify Data is Arriving in LogScale

Once you have completed the above steps the Akamai Cloud Web Application Firewall data should be arriving in your LogScale repository.

You can verify this by doing a simple search for the events:

#Vendor = "akamai" 
| #event.module="asec"

Package Contents Explained

This package parses incoming data, and normalizing the data as part of that parsing. The parser normalizes the data to CrowdStrike Parsing Standard (CPS) 1.0 schema based on OpenTelemetry standards, while still preserving the original data.

If you want to search using the original field names and values, you can access those in the fields whose names are prefixed with the word Vendor. Fields which are not prefixed with Vendor are standard fields which are either based on the schema (e.g. source.ip) or on LogScale conventions (e.g. @rawstring).

The fields which the parser currently maps the data to, are chosen based on what seems the most relevant, and will potentially be expanded in the future. But the parser won't necessarily normalize every field that has potential to be normalized.

Event Categorisation

As part of the schema, events are categorized by fields:

  • event.kind

  • event.category

  • event.type

event.kind and #event.outcome can be searched using Field Filters fields, but event.kind and event.type are arrays, so need to be searched using the following syntax:

array:contains("event.category[]", value="network")

For example, the following will find events where some event.type[n] field contains the value network, regardless of what n is.

Note that not all events will be categorized to this level of detail.

Normalized Fields

Here are some of the normalized fields which are being set by this parser:

  • source.* (e.g. source.ip,source.geo.city,source.address,source.geo.country )

  • geo* (e.g. geo.region,geo.city,geo.country )

  • url.* (e.g. url.port, url.domain, url.path, url.query)

  • ecs* (e.g. ecs.version )

  • network.* (e.g. network.protocol )

  • event.* (e.g. event.type, event.kind, event.id)

  • http.* (e.g. http.response.status, http.response.bytes, http.request.method,http.request.id,http.version)