https://polymathmonkey.github.io/weblog/tags/visibility/index.htmlHugoen-usAll text is licensed under a Creative Commons Attribution 4.0 International License.Wed, 22 Apr 2026 07:09:36 +0200https://polymathmonkey.github.io/weblog/artifacts/threathuntingnet/index.htmlTue, 08 Jul 2025 09:15:00 +0200https://polymathmonkey.github.io/weblog/artifacts/threathuntingnet/index.htmlTable of Contents Introduction Why I Built a Home Lab for Threat Hunting 🕵 Network Setup Topology, Hardware and Tools 🛠 Firewall configuration🧱 Switch configuration What I Learned Whats next Introduction This is a small series I wanted to start, where I write about my small threathunting setup and describe a little what I build and what I am doing with it. In this part, I will describe the Network setup for my Environment, more about how I build the honeypots and the ELK Server I will describe in the follow up articles about threathunting.https://polymathmonkey.github.io/weblog/artifacts/monitmon/index.htmlMon, 08 Dec 2025 11:40:00 +0100https://polymathmonkey.github.io/weblog/artifacts/monitmon/index.htmlIntroduction Requirements Installing Monit on OpenBSD Monit – Essential System and Router Services System monitoring runs every 45 seconds. The first check is delayed by 120 seconds to avoid overloading the system immediately after boot. set daemon 45 with start delay 120 Monit logs to syslog. `idfile` and `statefile` store Monit’s persistent state and identity across restarts. set log syslog set idfile /var/monit/id set statefile /var/monit/state Limits control buffer sizes and timeouts for program outputs, network I/O, and service start/stop/restart operations. This prevents Monit from hanging or processing excessive data.