You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/akamai/_dev/build/docs/README.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ The Akamai integration collects events from the Akamai API, specifically reading
6
6
7
7
### SIEM
8
8
9
-
The Security Information and Event Management API allows you to capture security events generated on the Akamai platform in your SIEM application.
9
+
The Security Information and Event Management API allows you to capture security events generated on the Akamai platform in your SIEM application.
10
10
11
-
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.
11
+
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.
12
12
13
13
See [Akamai API get started](https://techdocs.akamai.com/siem-integration/reference/api-get-started) to set up your Akamai account and get your credentials.
14
14
15
-
### To collect data from GCS Bucket[Beta], follow the below steps:
15
+
### To collect data from GCS Bucket, follow the below steps:
16
16
- Configure the [Data Forwarder](https://techdocs.akamai.com/datastream2/docs/stream-google-cloud/) to ingest data into a GCS bucket.
17
17
- Configure the GCS bucket names and credentials along with the required configs under the "Collect Akamai SIEM logs via Google Cloud Storage" section.
18
18
- Make sure the service account and authentication being used, has proper levels of access to the GCS bucket [Manage Service Account Keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys/)
@@ -21,7 +21,6 @@ See [Akamai API get started](https://techdocs.akamai.com/siem-integration/refere
21
21
- 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.
22
22
- The GCS input currently only accepts a service account JSON key or a service account JSON file for authentication.
23
23
- The GCS input currently only supports JSON data.
Copy file name to clipboardExpand all lines: packages/akamai/data_stream/siem/manifest.yml
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,5 @@
1
1
type: logs
2
2
title: Akamai SIEM Logs
3
-
release: experimental
4
3
streams:
5
4
- input: httpjson
6
5
template_path: httpjson.yml.hbs
@@ -124,7 +123,7 @@ streams:
124
123
The request tracer logs requests and responses to the agent's local file-system for debugging configurations. Enabling this request tracing compromises security and should only be used for debugging. See [documentation](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-httpjson.html#_request_tracer_filename) for details.
125
124
126
125
- input: gcs
127
-
title: Collect Akamai SIEM logs via Google Cloud Storage [Beta]
126
+
title: Collect Akamai SIEM logs via Google Cloud Storage
128
127
description: Collecting SIEM logs from Akamai via Google Cloud Storage.
Copy file name to clipboardExpand all lines: packages/akamai/docs/README.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ The Akamai integration collects events from the Akamai API, specifically reading
6
6
7
7
### SIEM
8
8
9
-
The Security Information and Event Management API allows you to capture security events generated on the Akamai platform in your SIEM application.
9
+
The Security Information and Event Management API allows you to capture security events generated on the Akamai platform in your SIEM application.
10
10
11
-
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.
11
+
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.
12
12
13
13
See [Akamai API get started](https://techdocs.akamai.com/siem-integration/reference/api-get-started) to set up your Akamai account and get your credentials.
14
14
15
-
### To collect data from GCS Bucket[Beta], follow the below steps:
15
+
### To collect data from GCS Bucket, follow the below steps:
16
16
- Configure the [Data Forwarder](https://techdocs.akamai.com/datastream2/docs/stream-google-cloud/) to ingest data into a GCS bucket.
17
17
- Configure the GCS bucket names and credentials along with the required configs under the "Collect Akamai SIEM logs via Google Cloud Storage" section.
18
18
- Make sure the service account and authentication being used, has proper levels of access to the GCS bucket [Manage Service Account Keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys/)
@@ -21,7 +21,6 @@ See [Akamai API get started](https://techdocs.akamai.com/siem-integration/refere
21
21
- 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.
22
22
- The GCS input currently only accepts a service account JSON key or a service account JSON file for authentication.
23
23
- The GCS input currently only supports JSON data.
0 commit comments