-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat] Add ECS tls fields to zeek and aws modules #15936
Conversation
Pinging @elastic/siem (Team:SIEM) |
- zeek/smtp + tls.established - zeek/rdp + tls.established - zeek/ssl + tls.cipher + tls.curve + tls.client.issuer + tls.established + tls.resumed + tls.server.issuer + tls.version + tls.version_protocol - aws/elb + tls.cipher + tls.version + tls.version_protocol - aws/s3access + tls.cipher + tls.version + tls.version_protocol Closes elastic#15757
39dd032
to
895dc36
Compare
jenkins, test this |
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.
Looking great :-)
Nitpick: I would suggest converting booleans from string to boolean datatype.
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.
LGTM. Just the one question on Painless stuff.
- set: | ||
field: tls.cipher | ||
value: '{{aws.elb.ssl_cipher}}' | ||
if: ctx.aws?.elb.ssl_cipher != null |
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.
Does this work safely if the ssl_cipher
field does not exist?
Is this the same as if: ctx.aws?.elb?.ssl_cipher != null
?
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 does work if ssl_cipher
doesn't exist, the http logs are good examples.
That being said it might be safer to use null safe operator on both
This doc would fails with current if: ctx.aws?.elb.ssl_cipher != null
{
"aws.elb.ip": "10.0.0.1"
}
and this doc succeeds
{
"aws": {
"elb": {
"ip": "10.0.0.1"
}
}
}
both work with if: ctx.aws?.elb?.ssl_cipher != null
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.
This doc would fails...
This is to be expected, Elasticsearch ingest pipelines don't support dotted keys (other than the dot expander processor). So I'd be surprised if Painless (the if clause) supported it.
* Add ECS tls fields to zeek and aws modules - zeek/smtp + tls.established - zeek/rdp + tls.established - zeek/ssl + tls.cipher + tls.curve + tls.client.issuer + tls.established + tls.resumed + tls.server.issuer + tls.version + tls.version_protocol - aws/elb + tls.cipher + tls.version + tls.version_protocol - aws/s3access + tls.cipher + tls.version + tls.version_protocol Closes elastic#15757 (cherry picked from commit b6baae0)
* Add ECS tls fields to zeek and aws modules - zeek/smtp + tls.established - zeek/rdp + tls.established - zeek/ssl + tls.cipher + tls.curve + tls.client.issuer + tls.established + tls.resumed + tls.server.issuer + tls.version + tls.version_protocol - aws/elb + tls.cipher + tls.version + tls.version_protocol - aws/s3access + tls.cipher + tls.version + tls.version_protocol Closes #15757 (cherry picked from commit b6baae0)
Backported in #16043. |
Closes #15757