Skip to content

Add RDP schema record type and missing TLS fields #1186

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

Merged
merged 4 commits into from
Nov 19, 2020

Conversation

satta
Copy link
Contributor

@satta satta commented Nov 19, 2020

📔 Description

Add a new record type in the Suricata schema for RDP and add, among others, the missing tls.sni field that would be required for some applications involving domain indicators.

📝 Checklist

  • All user-facing changes have changelog entries.
  • The changes are reflected on docs.tenzir.com/vast, if necessary. (n/a)
  • The PR description contains instructions for the reviewer, if necessary. (n/a)

🎯 Review Instructions

Just double-check the syntax please.

This commit adds the previously missing 'sni' and
'session_resumed' fields.
Copy link
Member

@mavam mavam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update!

@mavam mavam requested a review from dominiklohmann November 19, 2020 17:05
Co-authored-by: Matthias Vallentin <vallentin@icir.org>
Copy link
Member

@dominiklohmann dominiklohmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks alright to me. The fields match what Suricata exports.

This change by itself is not breaking, because it's a strict superset of the old schema.

@dominiklohmann dominiklohmann merged commit 4f32bb0 into tenzir:master Nov 19, 2020
@satta satta deleted the schemastuff2 branch November 19, 2020 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants