• 0 Posts
  • 905 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle

  • You are trying to de-jargon topics, and that’s fine, but the two following categories do not help, they are localized habits and don’t have any value to non-english or nontechnical people, or both:

    • shortenings: a11y for accessibility is not a common contraction, it’s not helpful for anyone to understand the term itself
    • names of services: CF for cloudflare is not something worth defining. Names change, and you wouldn’t see this in a professional document. It’s like defining “lol”, the acronym is shorthand in typed communication, not technical jargon.

    Side note, DNS stands for domain name system, it has never meant domain name service.

    I personally find bots annoying, half the content on the internet is already bots.







  • The author says that Linux should be as usable for grandparents as it is for children

    My problem with this statement constantly bombarded on us is that it assumes that someone somewhere out there who cares.

    To me, it seems that is the actual deciding factor in sticking with Linux… Realizing that if you want something that doesn’t exist, you’ll have to make it.


  • Oh, yeah, absolutely. Suricata was created not long after snort, in the days when an ids did the gathering and the correlation.

    You’re totally right, the way most people and orgs do it today is to ship ids logs to a siem for the correlation, overall easier to manage. ELK is the go-to for most, not sure about wazuh, I’ve only seen it in the homelab space, but it might work.

    There is a distro (not totally open source) called SELKS, which sets up suricata, elastic and some other tooling (kibana) in a commonly-used setup. I deploy it a lot because it saves time with the non-security setup with dB’s and such. Pretty easy to point syslog to it and you can see alerts right away and start tuning.

    I’m envious of your position, I learned a lot setting this stuff up.


  • The mirrored traffic will retain their VLAN tags and Suricata can parse these tags.

    I’m not sure how far down this path you’ve gone, but suricata will not automatically correlate primitives into actual alerts from different vlans without transforms, which are cpu-intensive for what they do.

    You may want to pull your tap/span/mirror from a point where they converge, like internal side of network egress.





  • From my perspective

    Are you aware that I don’t have your perspective?

    I wanted to know more about your project, from your own words. Instead I got a lecture about how “dumb” I am, so I’m no longer interested, because you seem like a jerk. Whether that was intensional or is coming from an ill-adapted social outlook, I’m still not sure of.

    You seem to care more about being correct than talking about your project, which is your choice, I suppose.

    I’d close this with a glib sign-off like “have a nice day”, but I’m not sure having a nice day is within your array of skills.





  • You can get creative with Linux.

    1. Install on 512mb, remove and trim system services, and lower the memory. Running KVM is by itself likely not going to let you do that, I suspect.
    2. Use Alpine as you say.I run many alpine containers on between 25MB and 60MB, I give them 256MB, but it’s way overkill.

    Regarding alpine, be prepared to find differences from glibc and systemd distros in places you don’t expect. PHP (god forbid you should need it) is a right mess on alpine. Mongodb will not work on alpine. Stuff like that.

    I may take some challenge on this, but the tcpip stack seems faster on alpine than in debian, at least in my use cases.