Cherry-pick #21696 to 7.x: Add ja3 fields to Zeek SSL log #22358
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.
Cherry-pick of PR #21696 to 7.x branch. Original message:
What does this PR do?
Rename
ja3s
totls.server.ja3s
if present (requires zeek/salesforce/ja3 package package).Rename
ja3
totls.client.ja3
if present (requires zeek/salesforce/ja3 package package).Rename
subject
totls.server.subject
(instead of deleting it after parsing).Rename
not_valid_before
totls.server.not_before
if present.Rename
not_valid_after
totls.server.not_after
if present.Fix dashboard reference for
zeek.ssl.server.name
that was usingzeek.ssl.server_name
.Why is it important?
Improves the Zeek SSL dataset's ability to populate the TLS tab in the Security app.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
tls.server.not_after
andtls.server.hash.sha1
to the zeek.ssl log and update the pipeline for those fields.