<?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>Ai on kimobu</title><link>https://www.kimobu.space/tags/ai/</link><description>Recent content in Ai on kimobu</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright Kimo B</copyright><lastBuildDate>Sun, 13 Apr 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.kimobu.space/tags/ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Vibe coding a Mach-o parser</title><link>https://www.kimobu.space/posts/Vibe-coding-a-Macho-Parser/</link><pubDate>Sun, 13 Apr 2025 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/Vibe-coding-a-Macho-Parser/</guid><description>&lt;p&gt;Way back in 2021 when I was working on my &lt;a href="https://github.com/kimobu/lhtml"&gt;dissertation&lt;/a&gt; I used a Python library called &lt;a href="https://github.com/aaronst/macholibre"&gt;macholibre&lt;/a&gt; to parse Mach-O files. There are &lt;a href="https://github.com/search?q=macho%20parser&amp;amp;type=repositories"&gt;several other options&lt;/a&gt; for parsing these file types. I&amp;rsquo;m sure they&amp;rsquo;re all great, but it&amp;rsquo;s a lot to go through to find some features I want. Mainly, outputting as JSON to easily load into other applications. This seemed like a good opportunity to try &lt;a href="https://en.wikipedia.org/wiki/Vibe_coding"&gt;vibe-coding&lt;/a&gt; a Swift-based Mach-O parser using ChatGPT. After some trial and error, I&amp;rsquo;ve made &lt;a href="https://github.com/kimobu/machp"&gt;MachP&lt;/a&gt; available. Let&amp;rsquo;s look at how this went.&lt;/p&gt;</description></item><item><title>GPT Detections on Windows and Linux</title><link>https://www.kimobu.space/posts/GPT-Detections-on-Windows-and-Linux/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/GPT-Detections-on-Windows-and-Linux/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;This is a follow up to &lt;a href="https://www.kimobu.space/posts/A-Little-Less-Malware-a-Little-More-Context/"&gt;A Little Less Malware&lt;/a&gt;, applying the same techniques to Linux and Windows data. There are some differences with this experiment. In the last one, we used Apple&amp;rsquo;s ESF to collect telemetry, which gave us process group identifiers to work with. In this experiment, I&amp;rsquo;m using only the Elastic Agent and the process telemetry it provides. Unfortunately, Elastic Agent does not send PGID for Linux, and while Windows notionally &lt;a href="https://learn.microsoft.com/en-us/windows/console/console-process-groups"&gt;supports the concept&lt;/a&gt;, in practice it does not exist. First let&amp;rsquo;s look at a couple of ways to group activity without PGIDs.&lt;/p&gt;</description></item><item><title>A Little Less Malware a Little More Context: Using AI to detect malicious activity</title><link>https://www.kimobu.space/posts/A-Little-Less-Malware-a-Little-More-Context/</link><pubDate>Fri, 27 Dec 2024 00:00:00 +0000</pubDate><guid>https://www.kimobu.space/posts/A-Little-Less-Malware-a-Little-More-Context/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;A coworker and I gave a &lt;a href="https://objectivebythesea.org/v7/talks/OBTS_v7_mBumanglag_jMillman.pdf"&gt;talk at Objective by the Sea v7&lt;/a&gt; on using Large Language Models (LLMs) as a behavioral detection. Another speaker, &lt;a href="https://x.com/DefSecSentinel"&gt;Colson&lt;/a&gt;, gave a great &lt;a href="https://objectivebythesea.org/v7/talks/OBTS_v7_cWilhoit.pdf"&gt;talk&lt;/a&gt; on why behavioral detections are so useful. LLMs are particularly adept at understanding and processing language-like structures, which include not only traditional text but also command-line arguments. In cybersecurity events, where command-line interactions often reveal attacker behaviors, LLMs can be leveraged to do behavioral detection without needing to be an expert in analyzing malicious actions or writing detections.&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></channel></rss>