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

Add feature to allow Base64 decoding in the UI on specific fields #4358

Closed
smayzak opened this issue Jun 30, 2015 · 3 comments
Closed

Add feature to allow Base64 decoding in the UI on specific fields #4358

smayzak opened this issue Jun 30, 2015 · 3 comments
Assignees
@jbudz
Labels
good first issue low hanging fruit release_note:enhancement

Comments

@smayzak
Copy link

smayzak commented Jun 30, 2015

Sometimes people want to send data into Elasticsearch encoded and would like to be able to decode in Kibana and not as part of a logstash filter for example. Any chance we can add a Field formatter or something to allow decoding in the UI?
@sgerlach
Copy link

This feature would be awesome for processing and displaying IDS payload data. Suricata is currently able to send JSON encoded alert data and within it, base64 encoded payload data. While it also has the option of sending clear text, this can become unmanageable and large data to store. A base64 decoder in Kibana would keep payload data size relatively small and enable security analysts to remain in one console for reviewing logs and alerts. Kibana for the win!
https://redmine.openinfosecfoundation.org/projects/suricata/wiki/EveJSONOutput

@naisanza
Copy link

+1

@jbudz jbudz self-assigned this Jun 30, 2015
@dkiser
Copy link

dkiser commented Jul 1, 2015

+1 - be awesome to have a "packet view" plugin that you can map data types to in kibana and have other plugin types for other visualization tools in the future (hex editors, etc etc)

jbudz added a commit to jbudz/kibana that referenced this issue Jul 1, 2015
@jbudz
Add transform for decoding base64 strings. Closes elastic#4358
90e4fb8
@jbudz jbudz mentioned this issue Jul 2, 2015
Merged
spalger pushed a commit that referenced this issue Nov 20, 2019
[7.x] [a11y] add initial accessibility functional tests (#4358… (#50086)
9a6724c 
* [a11y] add initial accessibility functional tests

* add accessibility jobs

* fix config path

* remove percy setup from scripts

* disable color-contrast rule

* apply changes from @myasonik

* define aria-controls/owns props even when suggestions aren't visible

* [ftr/a11y] only throw error when there are errors

* adding tests for management page

* add a11y test for management page

* adding ignore rules' to a11y

* accessibility test for kibana home

* 7 passing tests, 0 failures

* jest snapshot update

* support a11y test in pipeline job

* update a11y test script for pipelines

* use oss compatible ci setup

* fix exclude syntax

* add default exclusion syntax
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jbudz jbudz

Labels
good first issue low hanging fruit release_note:enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@w33ble @smayzak @naisanza @jbudz @sgerlach @dkiser