[Sophos] UTM data stream: replace Javascript processing with ingest pipelines - #6816
Conversation
6c0f620 to
33e94b3
Compare
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
🌐 Coverage report
|
P1llus
left a comment
There was a problem hiding this comment.
Not reviewed packetfilter yet, nor the pipelines, just the test logs and expected.json for them. Will do the rest a bit later.
| ] | ||
| }, | ||
| "host": { | ||
| "hostname": "sophos-test-vm2" |
There was a problem hiding this comment.
Are these the host or the observer? I would say its the observer maybe? Unsure if it was SIEM that required host.name or host.hostname for it to appear, but we could check that out if necessary.
There was a problem hiding this comment.
I would say it is the hostname where the original log was created since Sophos reads directly from the original log files, based on the list here. In addition, the timestamp read from logs is considered the original timestamp of the event.
But, I am not 100% sure here.
| "country": "United States", | ||
| "dnstime": 5, | ||
| "filteraction": "REF_HTTP_ACTION", | ||
| "fullreqtime": 32181, |
There was a problem hiding this comment.
Would this match with event.duration? Unsure as I have not checked their docs
There was a problem hiding this comment.
It seems so, but I am not 100% sure either, most of HTTP events have several time-related fields, such as:
authtime="0" dnstime="249" aptptime="0" cattime="206" avscantime="0" fullreqtime="1499"
It is complicated to say for sure as I couldn't find any docs related to these fields.
| value: start | ||
| if: "['17701', '17704', '17707', '17710', '17713'].contains(ctx.event?.code)" |
There was a problem hiding this comment.
|
Package sophos - 3.0.0 containing this change is available at https://epr.elastic.co/search?package=sophos |
4 similar comments
|
Package sophos - 3.0.0 containing this change is available at https://epr.elastic.co/search?package=sophos |
|
Package sophos - 3.0.0 containing this change is available at https://epr.elastic.co/search?package=sophos |
|
Package sophos - 3.0.0 containing this change is available at https://epr.elastic.co/search?package=sophos |
|
Package sophos - 3.0.0 containing this change is available at https://epr.elastic.co/search?package=sophos |
…ipelines (elastic#6816) * Fix invalid event type for XG data stream * Update Sophos UTM data stream * Add event outcome and log source to UTM events * Generate sample event and add it to package docs * Convert some fields from keyword to long * Create dashboards for Sophos UTM * Add screenshots of Sophos UTM dashboards * Update changelog * Add requested changes * Adapt dashboards to requested changes * Add service to event.action for some cases * Add requested changes in ingest pipelines * Remove extra conditions * Lowercase observer type
What does this PR do?
This pull request updates the Sophos integration to:
xgdata stream about an incompatible event type and category.Checklist
changelog.ymlfile.Related issues
Screenshots
Integration page and configuration

Dashboards