-
Notifications
You must be signed in to change notification settings - Fork 474
[Sophos] UTM data stream: replace Javascript processing with ingest pipelines #6816
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
6c0f620
to
33e94b3
Compare
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
🌐 Coverage report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not reviewed packetfilter yet, nor the pipelines, just the test logs and expected.json for them. Will do the rest a bit later.
packages/sophos/data_stream/utm/_dev/test/pipeline/test-sophos-utm-dhcp.log-expected.json
Outdated
Show resolved
Hide resolved
] | ||
}, | ||
"host": { | ||
"hostname": "sophos-test-vm2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
packages/sophos/data_stream/utm/_dev/test/pipeline/test-sophos-utm-dhcp.log-expected.json
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/_dev/test/pipeline/test-sophos-utm-dhcp.log-expected.json
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/_dev/test/pipeline/test-sophos-utm-dhcp.log-expected.json
Outdated
Show resolved
Hide resolved
"country": "United States", | ||
"dnstime": 5, | ||
"filteraction": "REF_HTTP_ACTION", | ||
"fullreqtime": 32181, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this match with event.duration? Unsure as I have not checked their docs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
packages/sophos/data_stream/utm/_dev/test/pipeline/test-sophos-utm-http.log-expected.json
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/_dev/test/pipeline/test-sophos-utm-http.log-expected.json
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/_dev/test/pipeline/test-sophos-utm-http.log-expected.json
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/_dev/test/pipeline/test-sophos-utm-http.log-expected.json
Outdated
Show resolved
Hide resolved
value: start | ||
if: "['17701', '17704', '17707', '17710', '17713'].contains(ctx.event?.code)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/packetfilter.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/http.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/packetfilter.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/packetfilter.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/packetfilter.yml
Outdated
Show resolved
Hide resolved
packages/sophos/data_stream/utm/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
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 |
What does this PR do?
This pull request updates the Sophos integration to:
xg
data stream about an incompatible event type and category.Checklist
changelog.yml
file.Related issues
Screenshots
Integration page and configuration

Dashboards