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

Placing this rule in my Elastic Search Stack ISSUE #5

Open
prashantmitm opened this issue Apr 19, 2020 · 0 comments
Open

Placing this rule in my Elastic Search Stack ISSUE #5

prashantmitm opened this issue Apr 19, 2020 · 0 comments

Comments

@prashantmitm
Copy link

Hi,

I love the tool for its effectiveness and simplicity to be implemented. I would really like to take its advantage in our Production Environment. Let me describe you a little on the production setup:
I am trying to place the tool in my Elastic Stack Server, and my DNS logs are being forwarded to the ELK stack using beats. While doing live capture, the traffic should not be sniffed at port 53, but on 5044 port. I have changed that in the python code.

But still no DGA are being detected, when i try looking up for the domains from testing_txt.
Do you know how this tool could work in a similar setup. A response is much appreciated. Thanks

Prashant

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