Loading

Akamai Integration

Version 4.0.0 (View all)
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) Google Cloud Storage
Minimum Kibana version(s) 9.5.0

The Akamai integration collects events from the Akamai API, specifically reading from the Akamai SIEM API.

Breaking change in 4.0.0: The backend used to collect Akamai SIEM logs from the API has changed. This version requires Elastic Stack 9.5.0 or later. After upgrading, existing agent policies that collect Akamai SIEM logs via the API must be reconfigured for data collection to resume. If you previously set the advanced SSL Configuration option, it must be rewritten using the OpenTelemetry tls schema (ca_file/ca_pem, cert_file/cert_pem, key_file/key_pem, insecure_skip_verify, min_version, max_version) rather than the Beats keys (certificate_authorities, verification_mode, supported_protocols). The Akamai SIEM API only provides access to the previous 12 hours of events, so reconfigure the policy within 12 hours of upgrading to avoid a permanent gap in the data; the Initial Interval option (default and maximum 12h) controls how far back the first fetch reaches. Collection from Google Cloud Storage is unaffected.

The Security Information and Event Management API allows you to capture security events generated on the Akamai platform in your SIEM application.

Use this API to get security event data generated on the Akamai platform and correlate it with data from other sources in your SIEM solution. Capture security event data incrementally, or replay missed security events from the past 12 hours. You can store, query, and analyze the data delivered through this API on your end, then go back and adjust your Akamai security settings. If you’re coding your own SIEM connector, it needs to adhere to these specifications in order to pull in security events from Akamai Security Events Collector (ASEC) and process them properly.

See Akamai API get started to set up your Akamai account and get your credentials.

  • Enable the "Collect Akamai SIEM logs via API" toggle; it is disabled by default.
  • Configure the API Host, Zone IDs and the EdgeGrid credentials (Client Token, Client Secret, Access Token) under the "Collect Akamai SIEM logs via API" section.
  • If the integration policy uses a namespace other than default, set the "Data Stream Namespace" option to the same value.

API collection uses the native OpenTelemetry akamai_siem receiver behind the scenes. This is an internal backend detail and does not change the data you collect.

Note:

  • Cursor persistence is enabled by default, so collection resumes from where it left off after an Elastic Agent restart. It can be turned off via the "Persist Cursor" advanced option. Cursor persistence is also not guaranteed across stack upgrades and breaking changes. Whenever the cursor is unavailable, the integration re-fetches the configured Initial Interval window; replayed events are deduplicated by the ingest pipeline's event.original fingerprint as long as the data stream is still writing to the same backing index.
  • Configure the Data Forwarder to ingest data into a GCS bucket.
  • Configure the GCS bucket names and credentials along with the required configs under the "Collect Akamai SIEM logs via Google Cloud Storage" section.
  • Make sure the service account and authentication being used, has proper levels of access to the GCS bucket Manage Service Account Keys

Note:

  • The GCS input currently does not support fetching of buckets using bucket prefixes, so the bucket names have to be configured manually for each data stream.
  • The GCS input currently only accepts a service account JSON key or a service account JSON file for authentication.
  • The GCS input currently only supports JSON data.