Suggestions for crowdsec + caddy + docker setup

Submitted ⁨⁨4⁩ ⁨days⁩ ago⁩ by ⁨whysofurious@lemmy.dbzer0.com⁩ to ⁨selfhosted@lemmy.world⁩

Hi all!

I’ll try to be quick but I apologise first as I am pretty new to security stuff and my questions might be obvious to the more experts.

I have a VPS (hetzner) set up with docker, caddy for the reverse proxy, and authentik as the only login method for a couple of services (hedgedoc and forgejo). Since most of these has to be available and accessible on the internet, I also setup crowdsec and built caddy with the relevant bouncer. This allows crowdsec to inspect the caddy logs for all the services I am serving through it and act accordingly.

So far, so good. However, I also saw that crowdsec can directly monitor container logs with the docker integration or through container labels. Also, I saw a couple of collections on crowdsec hub specifically for Authentik and Gitea.

I feel I am missing something so my question are:

Would it be useful to monitor container logs given my setup or would it be redundant?
Should I add the app-specific collections, or would docker logs monitoring be enough?

My current crowdsec collections

___ - crowdsecurity/linux - crowdsecurity/appsec-generic-rules - crowdsecurity/caddy - crowdsecurity/whitelist-good-actors - crowdsecurity/http-cve - crowdsecurity/iptables

source

Comments

Sort:hotnew top

just_another_person@lemmy.world ⁨4⁩ ⁨days⁩ ago
You only need Crowdsec to monitor the exposed service ports. If Authentik is exposed, and has a Crowdsec plugin, then add it. Otherwise, you’re just wasting resources having it watch things it can’t take action.

If you just need something to consolidate logs where you can watch them, use a centralized logging tool for that job.

source
- whysofurious@lemmy.dbzer0.com ⁨4⁩ ⁨days⁩ ago
  Thanks for the answer :) make sense, I will go through with the plugins for the services I have exposed, although not all of them have crowdsec collections.
  
  source
  - just_another_person@lemmy.world ⁨4⁩ ⁨days⁩ ago
    You can easily create custom rules and bouncers if needed for something specific as well. They’re templatized for the most part. Possibly even something a stupid AI could kick out, but make sure you know what it’s doing, and don’t trust it outright.
    
    source
    -> View More Comments
irmadlad@lemmy.world ⁨4⁩ ⁨days⁩ ago
On the free plan, you should be able to set up 2 remediation components, 4 blocklists, and a variety of scenarios. For the scenarios, I’d only install what you have need for.

As far as logs, I personally think something more along the lines of Grafana+Loki_Alloy for logs and metrics. You could even use something like lnav. Lnav is simple to install. It’s not a dialed out dashboard of metrics, rather it keeps things simple. After install, to access it simply type lnav and the log location you wish to view: lnav /var/log/auth.log or lnav /var/log/syslog in the cli.

I really tried with logging aps like ELK, Graylog, etc. I found them to be quite heavy for my environment. They certainly do have all the bells and whistles and pretty graphics, but again, it comes down to what can your server run comfortably. I didn’t want to eat up 2/3 of my resources just to look at logs. The Grafana+Loki+Alloy combo really sips the resources. I think for all I have Grafana monitoring, it clocks in at around 2+/- gb in used resources.

source
- whysofurious@lemmy.dbzer0.com ⁨3⁩ ⁨days⁩ ago
  Thanks for the thorough reply! I didn’t know about Inav, but it looks very interesting. I agree on the Grafana stack, it’s not something I really need now, and if I have to inspect single containers I can go for something like Dozzle.
  
  About crowdsec free plan, looking at the pricing page, I see that the community plan has unlimited remediation components and 3 blocklist + unlimited scenarios, or am I looking in the wrong place? (honestly that page is pretty confusing)
  
  source
  - irmadlad@lemmy.world ⁨3⁩ ⁨days⁩ ago
    I’m probably telling you wrong, but I’ve only been able to do the cs-blocklist-mirror and firewall-bouncer. There are a bunch of the scenarios that are remediation components. If you look at something like cs-cloudflare-worker-bouncer, well I don’t have a use for the cs-cloudflare-worker-bouncer remediation component, so that doesn’t get installed. Same for remediation components like cs-aws-waf-bouncer. So yes, there are unlimited remediation components, just not all will fit your use case. As I understand it, you can even write your own, tho I’ve not dabbled in that aspect.
    
    If all you want to do is look at Docker logs and the occasional syslog, then I would think Dozzle to be quite capable in conjunction with something along the lines of lnav.
    
    source