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

after and threshold tracking keys from json_map/normalization #47

Open
bryant-smith opened this issue Sep 7, 2022 · 0 comments
Open

Comments

@bryant-smith
Copy link
Contributor

It could be useful to grab the key used in the json_map field and be able to track by whatever the user defined in json_map. Here's an example:

alert any $HOME_NET any -> $HOME_NET any (msg:"[WINDOWS-AUTH] Domain Controller Blocked Audit: Audit NTLM authentication to this domain controller [100/1]"; \
program:Microsoft-Windows-NTLM/Operational; \
json_map:"event_id",".EventID"; 
event_id:8004; \
json_map:"host.workstationName",".WorkstationName"; \
json_map:"host.username",".Hostname"; \
after: track by_host.workstationName&by_host.username, count 10, seconds 60; \
threshold: type suppress, track by_host.workstationName&by_host.username, count 1, seconds 60; \
classtype:attempted-user; sid:1111111; rev:1;)

In the example we can use the predetermined fields, like event_id, or a user defined variable. This give the ability to track by two or more strings with after and/or threshold. If this can be done, maybe the same can be done with liblognorm. Any fields that are defined using liblognorm can be tracked with after and/or threshold.

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