Window's Logs on Steroids! SYSMON - Let's Deploy a Host Intrusion Detection System #10

Поделиться
HTML-код
  • Опубликовано: 24 янв 2025

Комментарии • 14

  • @SoCyber-n5k
    @SoCyber-n5k 13 дней назад

    You are good. The explanation is simple and straightforward

  • @Zeybek-n7z
    @Zeybek-n7z 2 года назад +1

    Taylor, thank you so much! I love Wazuh, and I know many people complain and say Wazuh is a pain to manage, but that's what I love about Wazuh and its granularity that many of the big products don't offer. You are truly a master at your craft. Thanks again for these great videos.

  • @denisret5457
    @denisret5457 4 месяца назад +1

    Hello guys, why there is only the first Event which work for me ?

    • @yasser-cifer8175
      @yasser-cifer8175 2 месяца назад

      same issue , could you please tell me if you solve it and how

  • @ronaldratzlaff6672
    @ronaldratzlaff6672 8 месяцев назад +1

    Hey Taylor,
    I followd this guide and I get some sysmon alerts in Wazuh (process creation and a few others), but for some reason the DNS query alert rule (101100) seems to not be working for me. I see the DNS queries in sysmon on the windows client, but they are not showing in the Wazuh dashboard. As mentioned, other sysmon alerts do show. Any ideas why that particular rule might fail?

    • @tommykohler1168
      @tommykohler1168 6 месяцев назад

      Same problem here...have you solved the problem? If yes, could you please tell me how?

    • @2809kev
      @2809kev 6 месяцев назад

      @@tommykohler1168 did either of you figure this out?

    • @krishyadav6993
      @krishyadav6993 3 месяца назад

      It is not working because the rule ID is not defined correctly. Use the following rule:
      61650
      Sysmon - Event 22: DNS Query.
      no_full_log
      Hopefully, this will resolve the issue for the DNS query.

    • @krishyadav6993
      @krishyadav6993 3 месяца назад

      @@tommykohler1168 It is not working because the rule ID is not defined correctly. Use the following rule:
      61650
      Sysmon - Event 22: DNS Query.
      no_full_log
      Hopefully, this will resolve the issue for the DNS query.

    • @krishyadav6993
      @krishyadav6993 3 месяца назад

      @@2809kev It is not working because the rule ID is not defined correctly. Use the following rule:
      61650
      Sysmon - Event 22: DNS Query.
      no_full_log
      Hopefully, this will resolve the issue for the DNS query.

  • @khai-vq5hn
    @khai-vq5hn 9 месяцев назад

    is it possible that i ll be receiving logs in wazuh manger deploed locally on vmware workstation and windows 10 vm on azure

    • @khai-vq5hn
      @khai-vq5hn 9 месяцев назад

      i tried hell alot and nothing is working out

  • @pawelsmierciak2559
    @pawelsmierciak2559 3 года назад +5

    just one thing is missing here :) while running sysmon for the first time you need to add option -accepteula because it wont install and you wont get any error message :(

    • @taylorwalton_socfortress
      @taylorwalton_socfortress  3 года назад +7

      Hey Pawel, thanks for pointing that out :). Command to be ran "sysmon -accepteula -i c:\windows\config.xml"