<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Macos on clo.ng</title>
    <link>https://clo.ng/categories/macos/</link>
    <description>Recent content in Macos on clo.ng</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 27 Jul 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://clo.ng/categories/macos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Leveraging osquery to examine the XProtect Behavioral Service DB</title>
      <link>https://clo.ng/blog/osquery-xpdb/</link>
      <pubDate>Thu, 27 Jul 2023 00:00:00 +0000</pubDate>
      <guid>https://clo.ng/blog/osquery-xpdb/</guid>
      <description>&lt;p&gt;Upon reading Mandiant&amp;rsquo;s &lt;a href=&#34;https://www.mandiant.com/resources/blog/north-korea-supply-chain&#34;&gt;&amp;ldquo;North Korea Leverages SaaS Provider in a Targeted Supply Chain Attack&amp;rdquo;&lt;/a&gt;, one of the artifacts that stood out to me was the usage of XProtect&amp;rsquo;s Behavior Service DB. Until now, I had assumed all XProtect detections were signature based, but it sounds like Apple may be testing some behavioral-based rules to flag suspicious process executions in newer versions of MacOS.&lt;/p&gt;&#xA;&lt;h1 id=&#34;examining-the-db-locally-using-sqlite3&#34;&gt;Examining the DB locally using sqlite3&lt;/h1&gt;&#xA;&lt;p&gt;If you&amp;rsquo;d like to take a look at the DB on your own system, you can simply run &lt;code&gt;sudo sqlite3 /var/protected/xprotect/XPdb&lt;/code&gt;:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
