<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Homelab on kimobu</title><link>https://www.kimobu.space/tags/homelab/</link><description>Recent content in Homelab on kimobu</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright Kimo B</copyright><lastBuildDate>Thu, 05 Sep 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.kimobu.space/tags/homelab/index.xml" rel="self" type="application/rss+xml"/><item><title>Monitoring Kubernetes with Security Onion</title><link>https://www.kimobu.space/posts/Kubernetes-monitoring-securityonion/</link><pubDate>Thu, 05 Sep 2024 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Kubernetes-monitoring-securityonion/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;After adding Kubernetes to my homelab, I wanted to learn how to hack and hunt for malicious activity involving containers. I found &lt;a href="https://madhuakula.com/kubernetes-goat/"&gt;Kubernetes GOAT&lt;/a&gt; which provides a great way to practice hacking. To do the hunting, we need some additional work to enable telemetry on networks, containers, and Kubernetes. In this post I&amp;rsquo;ll walk through how I instrumented my Microk8s cluster to hunt for the hacking actions you can do in the GOAT.&lt;/p&gt;</description></item><item><title>SecurityOnion GPT</title><link>https://www.kimobu.space/posts/SecurityOnion-GPT/</link><pubDate>Mon, 12 Feb 2024 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/SecurityOnion-GPT/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;I was recently catching up on some conference videos and saw a talk by Roberto Rodriguez on &lt;a href="https://www.youtube.com/watch?v=TiBIP7kWaks&amp;amp;list=PL7ZDZo2Xu3332bKrXyCb0VEg52nqmMAcv&amp;amp;index=31"&gt;Empowering Security Teams with Generative AI: GPT models&lt;/a&gt;. This got me thinking about how to integrate GPT to hunting with Security Onion.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Goals&lt;/strong&gt;:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Summarize activity found in Security Onion&lt;/li&gt;
&lt;li&gt;Enrich activity with MITRE ATT&amp;amp;CK attribution&lt;/li&gt;
&lt;li&gt;Convert English questions to Kibana Query Language to hunt&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;In this post, I&amp;rsquo;ll tackle goals 1 and 2. I&amp;rsquo;ll do goal 3 in a separate post. These experiments will be conducted in Jupyter lab.&lt;/p&gt;</description></item><item><title>Learning Kubernetes</title><link>https://www.kimobu.space/posts/Kubernetes/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Kubernetes/</guid><description>&lt;p&gt;I run a few services for the threat intelligence and hunting course that I teach, including &lt;a href="https://github.com/kevoreilly/CAPEv2"&gt;CAPE&lt;/a&gt;, &lt;a href="https://www.misp-project.org"&gt;MISP&lt;/a&gt;, and &lt;a href="https://caldera.mitre.org"&gt;Caldera&lt;/a&gt;. Last semester, I used a few VMs and Docker to provide these, but I wanted to learn Kubernetes. Here are some notes on migrating over.&lt;/p&gt;
&lt;h1 id="getting-started"&gt;Getting Started&lt;/h1&gt;
&lt;p&gt;I started trying Kubernetes the hard way but ultimately ended up using &lt;a href="https://microk8s.io/#install-microk8s"&gt;microk8s&lt;/a&gt;. The install guide was straight forward. I made 1x control plane node and 2x worker nodes. I used &lt;a href="https://www.robert-jensen.dk/posts/2021-microk8s-with-traefik-and-metallb/"&gt;this blog&lt;/a&gt; as a starting point. I used Robert&amp;rsquo;s suggestion for &lt;code&gt;nfs-subdir-external-provisioner&lt;/code&gt; to provide the persistent storage for my pods.&lt;/p&gt;</description></item><item><title>Putting phishing data into Security Onion</title><link>https://www.kimobu.space/posts/Adding-Phishing-to-the-Homelab/</link><pubDate>Thu, 20 Jul 2023 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Adding-Phishing-to-the-Homelab/</guid><description>&lt;p&gt;I wanted to add some phishing scenarios to my hunting homelab. I&amp;rsquo;m more concerned with being able to hunt on malicious emails than on stopping them, so &lt;a href="https://www.cloudflare.com/learning/email-security/dmarc-dkim-spf/"&gt;DMARC, DKIM, and SPF&lt;/a&gt; are out of scope. If you have an offensive lens, you&amp;rsquo;ll want to look at something like &lt;a href="https://www.securesystems.de/blog/building-a-red-team-infrastructure-in-2023/"&gt;this&lt;/a&gt; for an effective phishing set up.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s look at two areas: external mail where phishing comes from and internal mail where phishes will be received.&lt;/p&gt;</description></item><item><title>Adding macOS to my security homelab</title><link>https://www.kimobu.space/posts/macOS-Homelab/</link><pubDate>Wed, 10 May 2023 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/macOS-Homelab/</guid><description>&lt;p&gt;This post has notes on how I added a macOS machine to my security homelab.&lt;/p&gt;
&lt;h1 id="install-macos-to-proxmox"&gt;Install macOS to Proxmox&lt;/h1&gt;
&lt;p&gt;Follow this &lt;a href="https://www.nicksherlock.com/2022/10/installing-macos-13-ventura-on-proxmox/"&gt;guide&lt;/a&gt; to install macOS onto a Proxmox cluster. This will result in an x86 based VM. I plan on looking into an ARM node in the future. Reference &lt;a href="https://i12bretro.github.io/tutorials/0775.html"&gt;this page&lt;/a&gt; if you don&amp;rsquo;t want to extract OSK yourself. Additional note, this installed to local-lvm, not my GlusterFS storage.&lt;/p&gt;
&lt;h1 id="bind-macos-to-active-directory"&gt;Bind macOS to Active Directory&lt;/h1&gt;
&lt;p&gt;Since the rest of the lab is a Windows Active Directory domain, I wanted to join the macOS VM to the domain so domain users could login. Follow &lt;a href="https://www.hexnode.com/blogs/macos-active-directory-binding-explained/"&gt;the guide here&lt;/a&gt; for high level guidance. Ventura changed the look of the Directory Utility but the overall concepts are the same. In Directory Utility, tick the option to &amp;ldquo;create mobile account at login&amp;rdquo; and add the &amp;ldquo;Users&amp;rdquo; OU to allowed administration.&lt;/p&gt;</description></item><item><title>log4j JNDI Exploitation</title><link>https://www.kimobu.space/posts/log4j-JDNI-Exploitation/</link><pubDate>Fri, 10 Dec 2021 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/log4j-JDNI-Exploitation/</guid><description>&lt;h1 id="situation"&gt;Situation&lt;/h1&gt;
&lt;p&gt;A &lt;a href="https://www.lunasec.io/docs/blog/log4j-zero-day/"&gt;remote code execution (RCE) bug was found in log4j&lt;/a&gt;. &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44228"&gt;CVE 2021-44228&lt;/a&gt; has been assigned to it. The vulnerability lies in how log4j interprets Java Naming and Directory Interface (JNDI) URLs. JNDI lets an application look up a service. An attacker can craft a string that looks like &amp;ldquo;${jndi:proto://host/a}&amp;rdquo; where &lt;code&gt;proto&lt;/code&gt; is ldap or rmi, and log4j will connect to the &lt;code&gt;host&lt;/code&gt; to retrieve &lt;code&gt;a&lt;/code&gt;, which would specify how to process the log entry. However, &lt;code&gt;a&lt;/code&gt; can instead provide Java bytecode that log4j will execute.&lt;/p&gt;</description></item><item><title>Security Onion on Proxmox</title><link>https://www.kimobu.space/posts/Security-Onion-Proxmox/</link><pubDate>Wed, 26 May 2021 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Security-Onion-Proxmox/</guid><description>&lt;h1 id="security-onion-on-proxmox"&gt;Security Onion on Proxmox&lt;/h1&gt;
&lt;p&gt;I originally set up my homelab using Ovirt, but have since switched back to Proxmox. The reason for that is that the version of qemu that Ovirt ships with does not support the &amp;ldquo;applesmc&amp;rdquo; device that is needed to run macOS guests, whereas Proxmox does. Another benefit is that Proxmox supports running containers, while Ovirt required full virtual machines, and Proxmox is overall much faster at every day tasks like starting or migrating a VM. I kept the same infrastructure as before, including using Gluster as shared storage amongst the compute nodes.&lt;/p&gt;</description></item><item><title>Installing the Cuckoo Sandbox Using KVM</title><link>https://www.kimobu.space/posts/Installing-the-Cuckoo-sandbox-using-KVM/</link><pubDate>Thu, 23 Jan 2020 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Installing-the-Cuckoo-sandbox-using-KVM/</guid><description>&lt;p&gt;The &lt;a href="https://cuckoosandbox.org"&gt;Cuckoo&lt;/a&gt; project provides a safe environment in which to execute malware (also called &amp;ldquo;detonating&amp;rdquo;). I will be using Cuckoo as part of a malware analysis class. There are &lt;a href="https://www.cybrary.it/blog/0p3n/cuckoo-installation-guide-malware-sandboxing/"&gt;several&lt;/a&gt; &lt;a href="https://medium.com/@sainadhjamalpur/build-your-own-cuckoo-sandbox-installation-guide-3fc44b03a622"&gt;guides&lt;/a&gt; &lt;a href="https://www.sanjaysaha.info/blog/installation-of-cuckoo-sandbox-in-windows-10/"&gt;that&lt;/a&gt; &lt;a href="https://tom-churchill.blogspot.com/2017/08/setting-up-cuckoo-sandbox-step-by-step.html"&gt;you&lt;/a&gt; could follow to setup Cuckoo, but almost all of the ones that I found used VirtualBox as a hypervisor. Since I have a homelab running on KVM, I wanted to install Cuckoo to use that as well. There is no groundbreaking information in this post, but it consolidates information that I had to find from several different sources while troubleshooting.&lt;/p&gt;</description></item></channel></rss>