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

Inconsistent Variable Naming - Track by Source IP #58

Open
wrharding opened this issue Mar 2, 2023 · 1 comment
Open

Inconsistent Variable Naming - Track by Source IP #58

wrharding opened this issue Mar 2, 2023 · 1 comment

Comments

@wrharding
Copy link
Contributor

Tracking by source IP is inconsistent across Sagan:

getting a source ip without normalization: parse_src_ip
https://sagan.readthedocs.io/en/latest/rule-keywords.html#parse-src-ip

normalization rules utilize the tag src-ip
https://github.com/quadrantsec/sagan-rules/blob/main/normalization.rulebase

xbits uses ip_src
https://sagan.readthedocs.io/en/latest/rule-keywords.html#xbits

flexbits uses by_src
https://sagan.readthedocs.io/en/latest/rule-keywords.html#flexbits

mapping from json uses src_ip
https://sagan.readthedocs.io/en/latest/rule-keywords.html#json-map

Sagan will utilize the following syntax to denote a source IP:
"src_ip": "10.200.2.82"

Having consistency around all of these would be ideal, but is certainly not a critical task.

@quadrantsec
Copy link
Collaborator

Agreed. I think i started my own direction and then switch when we became a Suricata shop.

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

No branches or pull requests

1 participant