akamai - fingerprint event.original instead of requestId - #12393
Merged
andrewkroh merged 0 commit intoJan 21, 2025
Conversation
Contributor
🚀 Benchmarks reportTo see the full report comment with |
andrewkroh
marked this pull request as ready for review
January 17, 2025 19:25
andrewkroh
added
the
Team:Security-Service Integrations
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
|
💚 Build Succeeded
|
kcreddy
approved these changes
Jan 20, 2025
kcreddy
left a comment
kcreddy
left a comment
Contributor
There was a problem hiding this comment.
LGTM.
We could possibly use only the httpMessage part of the message, unless variations could be possible in other parts of the message too.
Contributor
|
Package akamai - 2.27.2 containing this change is available at https://epr.elastic.co/package/akamai/2.27.2/ |
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
Fix the document _id calculation to allow events with the same requestId to be indexed. The httpMessage.requestId field in Akamai SIEM events is not unique to all events based on observations of the data. It was observed that a given request ID could have multiple records. Among three records with the same requestId, one variant had httpMessage.bytes=0 and another had a different httpMessage.responseHeaders with "Server: Akamai Image Server...". I prefixed the document _id value with the timestamp based on recommendations from the "Efficient Duplicate Prevention for Event-Based Data in Elasticsearch" blog post. References - https://www.elastic.co/blog/efficient-duplicate-prevention-for-event-based-data-in-elasticsearch. - https://github.com/akamai/akamai-apis/blob/b106ff167cb582efdaf4aa185c962ab33d3d6dee/apis/siem/v1/schemas/siem-event-200.yaml#L260-L263
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
Fix the document _id calculation to allow events with the same requestId to be indexed. The httpMessage.requestId field in Akamai SIEM events is not unique to all events based on observations of the data. It was observed that a given request ID could have multiple records. Among three records with the same requestId, one variant had httpMessage.bytes=0 and another had a different httpMessage.responseHeaders with "Server: Akamai Image Server...". I prefixed the document _id value with the timestamp based on recommendations from the "Efficient Duplicate Prevention for Event-Based Data in Elasticsearch" blog post. References - https://www.elastic.co/blog/efficient-duplicate-prevention-for-event-based-data-in-elasticsearch. - https://github.com/akamai/akamai-apis/blob/b106ff167cb582efdaf4aa185c962ab33d3d6dee/apis/siem/v1/schemas/siem-event-200.yaml#L260-L263
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message