Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Provide mechanism for filtering plaintext and encrypted protocol traffic #1865

Closed
alma-pixie opened this issue Apr 2, 2024 · 1 comment
Closed

Provide mechanism for filtering plaintext and encrypted protocol traffic #1865

alma-pixie opened this issue Apr 2, 2024 · 1 comment

Comments

@alma-pixie
Copy link
Contributor

We want to identify traffic that is plaintext that is ingressing from or egressing to the Internet. The conn_stats table is able to indicate if a given connection is encrypted or not, but we'd like to ability to tie this back to specific protocol traces.
@alma-pixie alma-pixie mentioned this issue Apr 2, 2024
Merged
vihangm pushed a commit that referenced this issue Apr 4, 2024
@alma-pixie
Add encrypted field to all protocol data tables (#1866)
c8bd214 
Summary: Add encrypted field to all protocol data tables

The goal of this column is to ease the ability of identifying
connections that are plaintext that are ingressing from or egressing to
the Internet.

Relevant Issues: #1865

Type of change: /kind feature

Test Plan: Additional test logic verifies new behavior

Changelog Message: Add `encrypted` boolean field to all protocol/L7 data
tables

Signed-off-by: Alma Pixie <pixienaut@alma.security>
@ddelnano
Copy link
Member

This is available in the v0.14.9 vizier release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ddelnano @alma-pixie