<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Forensics on cpus.me</title>
    <link>https://cpus.me/tags/forensics/</link>
    <description>Recent content in Forensics on cpus.me</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 08 Aug 2026 00:30:00 +0200</lastBuildDate>
    <atom:link href="https://cpus.me/tags/forensics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>macOS Forensic Artifact Browser</title>
      <link>https://cpus.me/2026/macos-forensic-artifacts/</link>
      <pubDate>Sat, 08 Aug 2026 00:30:00 +0200</pubDate>
      <guid>https://cpus.me/2026/macos-forensic-artifacts/</guid>
      <description>&lt;p&gt;A searchable index of 313 macOS forensic artifacts collectable from a live system, covering&#xA;macOS 13 Ventura through macOS 26. Each entry records where the artifact lives, how to collect&#xA;it, what privilege the collection requires, and what investigative question it answers.&lt;/p&gt;&#xA;&lt;p&gt;Root alone is not sufficient on macOS 13 and later. TCC applies regardless of uid, so a root&#xA;process without Full Disk Access gets &lt;code&gt;EPERM&lt;/code&gt; on Mail, Messages, Safari data, the user&amp;rsquo;s Desktop,&#xA;Documents and Downloads, and on &lt;code&gt;TCC.db&lt;/code&gt; itself. Every entry declares its access tier, so you can&#xA;filter for exactly what a given privilege level can reach.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
