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.

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

Add schema fields #72

Open
theherodied opened this issue Mar 10, 2023 · 2 comments
Open

Add schema fields #72

theherodied opened this issue Mar 10, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation triaged

Comments

@theherodied
Copy link

Please describe what you are requesting
See field requests below. Two notes, I see the dev branch has policy_uid but no policy_uuid. With uuid being universally unique across devices this field would be a beneficial addition. For the session_duration I see that network_connection_duration was recently added. So this might not be needed anymore.

Describe what change you are proposing
policy.csv:
"policy_type", "default, policy, local-in-policy, local-in-policy-6", "keyword", " "
"policy_uuid", " ", "keyword", " "

network.csv
"network_interface_in_role","lan, wan","keyword/loweronly",
"network_interface_out_role","lan, wan","keyword/loweronly",
"network_service","ftp, ssh, smtp","keyword/loweronly","From service name field https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml"
"network_translation_type","dnat, snat, noop","keyword","NAT translation performed"

session.csv
"session_duration", " ", "Keyword", "Duration of a session in seconds such as a Firewall connection, TCP connection, user session,etc."

Describe the log source
Fortinet Fortigates, but this could apply to any firewall or router.

@theherodied theherodied changed the title Update schema fields Add schema fields Mar 10, 2023
@miwent miwent added documentation Improvements or additions to documentation triaged labels Mar 15, 2023
@theherodied
Copy link
Author

theherodied commented Mar 30, 2023

Edit: It appears that the Graylog GeoIP City database adapter shows the traits fields even though the City database itself does not contain it. Still interested in how the data would preferably be mapped.

@miwent , I'm looking at adding the MaxMind GeoIP City database is_ fields. Would that make sense to add under source_as_, source_geo_, or add a source_is field? And of course the corresponding destination fields.

Example information from the city database:
"traits": {
"autonomous_system_number": null,
"autonomous_system_organization": null,
"connection_type": null,
"domain": null,
"ip_address": "x.x.x.x",
"is_anonymous": false,
"is_anonymous_proxy": false,
"is_anonymous_vpn": false,
"is_hosting_provider": false,
"is_legitimate_proxy": false,
"is_public_proxy": false,
"is_satellite_provider": false,
"is_tor_exit_node": false,
"isp": null,
"organization": null,
"user_type": null

@miwent
Copy link
Collaborator

miwent commented Mar 30, 2023

@theherodied source_is_ prefix would work for the is_ properties

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation triaged
Projects
None yet
Development

No branches or pull requests

2 participants