sysmon-config VS hub

https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/networking-overview plenty of windows troubleshooting tips here too, and this is pretty good symon script saves to event viewer even after a reboot! , also care with wireshark as it may give you a false sense of there's a fault, try tcpIPview from sysinternals and yeah procmon for sure. https://github.com/SwiftOnSecurity/sysmon-config use psping to ping the server directly and see the latency goes up and down, you can ping it more often every 1 second so you get a better more detailed resul.

Rebooted and downloaded sysmon 14.16 and sysmonconfig-export.xml

There's all sorts of things you can do for various types of monitoring including Zabbix, Graylog, roll-your-own with Sysmon (see https://github.com/SwiftOnSecurity/sysmon-config), etc. The question becomes one of time - don't get so focused on DIY or free that you spend hours (or pay someone to spend hours) a month babysitting.

If you don't catch it what changes can you do to your logging to enable it? Can you push it out to the environment? While sysmon is awesome, you can do your hunts with built in logging most of the time... Just might not have all the data around it you want to have. I would throw sysmon on a test box (make sure you have a config file that filters out the noise: https://github.com/SwiftOnSecurity/sysmon-config)

I played around with https://github.com/SwiftOnSecurity/sysmon-config Maybe there xml can point you in the right direction

and here's an off the shelf config file: https://github.com/SwiftOnSecurity/sysmon-config

- Make sure you have sysmon installed on the agent host and it is logging event to the Sysmon folder as ID 22. Can use this xml file

Out of our 286 Windows Servers, this single server did not like our sysmon config file from SwitfOnSecurity - https://github.com/SwiftOnSecurity/sysmon-config/blob/master/sysmonconfig-export.xml

I use their free plan so I can't tell about any other plan. In order to protect all your services, you just have to deploy Crowdsec once, give it access to the logs of all your existing services and set up the relevant bouncers (reverse proxy and probably Cloudflare). You must also give it the relevant collections from https://hub.crowdsec.net/ such as https://hub.crowdsec.net/author/crowdsecurity/collections/nextcloud

Doesn't work adding it to acquis.yaml. Crowdsec fails to start. If I go to hub.crowdsec.net there are multiple predefined collections, many of which define an acquisition script but don't say where to put it.

The ssh-bf scenario:

We don't have support for them yet, however, if you provide log samples and open an issue with the samples on https://github.com/crowdsecurity/hub. We can work on supporting them.

You find the required contents of the acquis.yaml on the dedicated page of each collection on the hub.

This isn't usable in latest Caddy versions unfortunately. See https://github.com/crowdsecurity/hub/pull/433

I have news. There's a PR for Exchange support. I don't have an ETA for it to be merged, though.

I just submitted a PR for Wireguard support. Feel free to try it out. I haven't been able to test it much. And yes, it's my first PR :-)

Your use case sounds cool. Unfortunately CrowdSec is not very mature on Windows (yet). That being said we have just written a parser for sysmon. It's very much WIP and needs testing. Also there's not any scenarios yet so CrowdSec can't detect anything there yet. That being said we would love to collaborate with you on creating them if you're willing to invest time in it too. A good place to do that would be via our Discord (invite link under the subreddit description) where I will be happy to set up a dedicated channel where you can have direct access to our devs.

Thanks for joining and asking questions :-) sudo cscli metrics gives you an overview of which log sources is being parsed and which attacks has been detected. You add a custom application by creating a parser and scenario or downloading a collection from the hub and adding a suitable data source.