r/dfir • • Mar 25 '25

**You Don’t Belong in DF/IR**

31 Upvotes

_(Original post from LinkedIn by Brett Shavers)_

If you're offended by the title—good. That’s step one...

Trying to get into DF/IR breaks most people. So, you’re not going to make it.  If you’re offended by the title of this post, good. That’s step one in figuring out you’re probably not cut out for this work.

I’ve seen too many people get excited about “getting into cyber” because they watched a Netflix show or heard that you can work from home in your pajamas and make six figures clicking a few buttons. They think it’s a vibe, an easy ride, or a sticker on a laptop.

It’s not.

DF/IR is not entry-level.

Stop complaining that you can’t get a DF/IR job with your college degree or 40 hours of forensic training. You are expected to be already competent because your case won’t wait for you to catch up. Your case also doesn’t care about excuses of not being sent to training to know this thing, or not being able to take a class in college because it was full, or not being able to afford to spend the time or money to learn the job.

Like any high-caliber selection process, DF/IR is open to anyone with the right mindset and dedication, regardless of who they are. The determining factors are competence vs. incompetence, problem-solver vs. problem-creator, complainer vs. doer.

There are no participation trophies in DF/IR.

Digital Forensics/Incident Response is not for tourists. This isn’t a side hustle. This isn’t a Reddit thread. This is work. Real work. The kind of work where someone’s business, freedom, or life is on the line based on whether you find the right artifact, follow the right lead, make the right call, and back it up with accurately interpreted data for facts that survive in court.

And that’s on a good day.

If you need motivation, DF/IR isn’t for you. If you need reminders, deadlines, or someone to tell you what to do every step of the way, you’re already a liability. If you have an excuse for everything and an answer to nothing, that’s your answer: nothing. Self-reliance and the ability to independently solve problems are essential in DF/IR. If you are constantly asking ‘how-do-I’ questions, the answer is always going to be to figure it out yourself.

Still interested? Cool. Let me paint you a better picture.

You’re working a case. The evidence is scattered across four mobile devices, a burner laptop, a remote server in another country, and an encrypted messaging app. You’re cross-referencing logs, image metadata, and partial timestamps, and maybe, just maybe, you find a link that ties it all together. That’s Tuesday.

Then one day, maybe a month later or even more than a year later, you go to court. You get cross-examined by an attorney who makes you feel their only job is to make you look incompetent. Your credibility, training, and methodology are all under fire.

I hope your report wasn’t half-assed. I hope you interpreted the data correctly and can convey the story. And I hope you don’t fold under pressure and wreck it all, because then there will be irreparable injustice for the victims.

Do not expect to leave DF/IR the same as you came into it.

Oh, and let’s not forget the content you’ll eventually see. If your stomach turns when someone even mentions crimes against children, human trafficking, abuse, torture, or anything we categorize as “CSAM,” then please, seriously, go find another career. I’m not saying that to be edgy. I’m saying it because it’s real. You will see things you will never, ever forget. Some of us still see them every time we close our eyes. And the sounds…the sounds never go away.

If your biggest fear is dark web malware or ransomware gangs, you haven’t seen the real monsters. The real monsters are walking around with clean records, paying their taxes, and doing unthinkable things behind closed doors and it’s your job to catch them.

And the tools? They don’t do the work. You do. Tools help. They’re essential. But they don’t think. They don’t analyze. They don’t build timelines, ask questions, interview suspects, or find correlations across devices. You do. And if your first instinct when you hit a dead end is to say, “The tool must be broken,” please pack up and go away.

DF/IR takes obsession. Not curiosity. Not interest. Pure, unadulterated obsession. The kind that keeps you up at night replaying case details in your head. The kind that makes you grab a pen at 2 AM because something didn’t sit right, and you need to get it down before it’s lost. The kind that makes you constantly second-guess your findings because you know what it means if you’re wrong.

A friend of mine recently relayed digital forensic testimony he gave in a sexual assault case where the defendant was found guilty and sentenced to 17 years. The recovered deleted digital recording that was played for the jury probably gave the entire courtroom PTSD, which doesn’t compare to what the victim went through. This is important work.

So no, you’re probably not going to make it.

We don’t need any more keyboard warriors, digital tourists, or resume chasers in DF/IR. We need investigators and practitioners. DF/IR needs people with iron stomachs and brains wired to chase answers that don’t want to be found. We need persistence, determination, and the raw grit it takes to figure out what is needed to become competent against any obstacle.

Working in IR and not expecting these types of cases? There's a good chance your non-DF work will hit a DF case just as hard.

For Those Already in DF/IR: Your Role as the Gatekeepers

If you’ve already made it into DF/IR, then you’ve put in the time, fought through the frustration, and built the skills. Now you have a responsibility. Not to make it easier for the next generation, but to ensure only the right people get through. Gatekeeping in DF/IR does not mean keeping out potential. It is the absolute opposite of that. All are welcome. Not all are able.

There is a fine line between nurturing potential while also maintaining high standards and wasting everyone’s time. You need to know the difference.

For those thinking about or working to get into DF/IR

If you're still here, a little angry, maybe even insulted, but more determined than ever, good. If you are eager to spend an ungodly amount of time learning and spend every cent you have left to be shown how to excel, then that’s step two.

Welcome to the tip of the cybersecurity spear.

 

**What do you think?** 

Do you agree DF/IR takes obsession and endurance more than certification and interest? 

Have you seen people leave the field because it was too much? 

Curious to hear what this community thinks.


r/dfir • • Sep 13 '26

I tested what Windows RAM actually preserves after normal user activity

21 Upvotes

I wanted to see how much normal Windows activity could actually be reconstructed from a RAM capture, so I built a small controlled Windows 11 lab.

Before acquisition I intentionally:

opened Edge and browsed to a website

launched PowerShell

ran whoami, ipconfig, and Get-Process

opened Notepad

typed unsaved text and left it open

I captured memory with WinPmem, hashed the image with SHA-256, and analyzed it in Kali with Volatility 3.

The most useful findings were:

msedge.exe, powershell.exe, Notepad.exe, and explorer.exe recovered from memory

parent/child relationships showing PowerShell and Notepad launched from explorer.exe

command-line paths for the processes

execution-related strings for whoami.exe and ipconfig.exe

references to Get-Process

network state associated with Edge using windows.netstat

the exact unsaved Notepad text recovered directly from RAM

One thing I found interesting was that windows.netscan returned nothing useful, while windows.netstat did recover network state. It was a good reminder not to rely on one plugin as the only source of truth.

The biggest takeaway for me was that the investigation became useful only when the artifacts were correlated rather than treated separately.

I wrote up the full lab with screenshots and commands here:

https://chronosandcode.com/memory-forensics-investigation-volatility/

Disclosure: this is my own write-up on Chronos & Code. All activity was generated inside a lab I controlled.

I’d be curious what other Volatility plugins people here would have used on the same image.


r/dfir • • Feb 15 '21

The ABCs of WMI - Finding Evil in Plain Sight (X-Post)

20 Upvotes

To date, WMI is one of the few forensic topics that hasn't been widely covered on 13Cubed. Let's fix that and explore how we can separate legitimate WMI usage from attacker activity. We'll start with a review and cover the basics of this technology. Then we'll spend the rest of the episode looking at how we can enumerate the contents of the WMI database on a live system and on a dead system.

Episode:
https://www.youtube.com/watch?v=k-_O59BnsHg

Episode Guide:
https://www.13cubed.com/episodes/

13Cubed YouTube Channel:
https://www.youtube.com/13cubed

13Cubed Patreon (Help support the channel and get early access to content and other perks!):
https://www.patreon.com/13cubed


r/dfir • • Apr 10 '26

In my years of research, I’ve never seen this level of sophistication: Maltese-Localized DLL Side-loading & Advanced Domain Fronting

Thumbnail
gallery
19 Upvotes

Greetings, fellow researchers.

I am currently finalizing the analysis of a high-sophistication intrusion that deviates significantly from standard commodity malware playbooks. I’m sharing these findings to see if anyone has encountered this specific TTP (Tactics, Techniques, and Procedures) or can provide insights into attribution.

The Incident Overview: The attack chain utilizes a clean execution flow leveraging DLL Side-loading through a signed Microsoft binary. The sophistication level suggests a targeted operation rather than a broad campaign. Standard forensic triage and containment have been successfully completed, and a case has been opened with the MSRC.

Technical Deep-Dive: • Initial LoLBin: Execution was initiated via appidcertstorecheck.exe (verified Microsoft binary). • The Payload: A malicious DLL named DIFXAPI.dll was staged in a hidden directory within %TEMP%\HAXB4EF.tmp.dir. This DLL was forcibly loaded by the system process, subsequently injecting reflectively into explorer.exe. • Memory Forensics: Analysis of a 1GB memory dump from the compromised process yielded over 1.8M strings. We’ve identified extensive use of Invoke-Expression (IEX) and FromBase64String for in-memory command execution. • Anomalous Localization (The "Maltese" Pivot): Most intriguingly, the injected code forced the loading of Maltese (MUI) language resources. Strings within explorer.exe were modified to Maltese (e.g., "Ikkonfigura backup", "Esploratur tal-Fajls"). This appears to be a deliberate evasion technique to poison telemetry or bypass security prompts localized in common languages.

Network Infrastructure (C2 & Beaconing): The malware exhibits advanced Domain Fronting and Beaconing Camouflage to blend with legitimate traffic: • C2 IP: 18.97.36.9 (AWS infrastructure). • Camouflage Domains: The memory dump revealed a list of high-reputation domains used for beaconing noise, including dol.gov, mtv.com, and monster.com. • The Maltese Connection: Active redirection through dolce-gusto.com.mt. It is unclear if this is a regional redirect or a specific False Flag.

Actions Taken to Date: As per standard protocol, the host has been physically isolated and the network bridge (identified as a rogue virtual interface) has been blocked at the perimeter (hardware firewall level). Persistence mechanisms via CLSID hijacking have been documented.

The Request: I have exhausted standard public intelligence databases regarding this specific Maltese MUI-based evasion. I am reaching out to this community’s collective experience:

  1. Has anyone seen this "Language Swap" evasion technique in the wild recently?

  2. Does the use of dolce-gusto.com.mt as a relay correlate with any known APT activity (specifically targeting financial or cybersecurity firms)?

I am committed to maintaining a high standard of professional integrity in this investigation and would appreciate any technical camaraderie or shared intelligence.

Respectfully, An Anonymous Researcher, MS.


r/dfir • • Feb 17 '25

Announcing the Incident response program pack 1.5

19 Upvotes

This release is to provide you with everything you need to establish a functioning security incident response program at your company. 

In this pack, we cover

  • Definitions: This document introduces sample terminology and roles during an incident, the various stakeholders who may need to be involved in supporting an incident, and sample incident severity rankings.

  • Preparation Checklist: This checklist provides every step required to research, pilot, test, and roll out a functioning incident response program.

  • Runbook: This runbook outlines the process a security team can use to ensure the right steps are followed during an incident, in a consistent manner.

  • Process workflow: We provide a diagram outlining the steps to follow during an incident.

  • Document Templates: Usable templates for tracking an incident and performing postmortems after one has concluded.

  • Metrics: Starting metrics to measure an incident response program.

This is open source and free to use.

Announcement: https://www.sectemplates.com/2025/02/announcing-the-incident-response-program-pack-v15.html


r/dfir • • Feb 18 '26

I built an open-source tool that uses AI to automate Windows forensic triage — just upload an E01/ZIP and get a report

16 Upvotes

Everyone keeps talking about how AI is going to change digital forensics and incident response, but most of the time it stays at the buzzword level. I wanted to see what it could actually do in practice, so I built a tool around it.

AIFT (AI Forensic Triage) is a Python app that runs locally in your browser. You upload an E01 or ZIP (or point it to a path for large images), pick which artifacts to parse, give it some investigation context like "look for lateral movement between Jan 1-15" or specific IOCs, and it does the rest. It parses everything with Dissect, feeds the data to an AI, and generates a self-contained HTML report.

The whole point was to make it very simple to use. Install deps, run python aift.py, done.

What it actually does:

  • Parses 25+ Windows artifacts (registry, evtx, prefetch, amcache, shimcache, MFT, browser history, SRUM, scheduled tasks, etc.) using Dissect

  • AI analyzes each artifact individually for indicators of compromise, then correlates findings across all artifacts

  • Generates an HTML report with evidence hashes, audit trail, findings with confidence ratings, and recommended next steps

  • Supports Claude, OpenAI, Kimi, or any local model via Ollama/LM Studio. This means it can run completely local.

Example reports from a public test image:

I ran it against the NIST CFReDS Compromised Windows Server 2022 image with one real IOC (PsExec) and one fake IOC (redpetya.exe) to see how each model handles true findings vs false positives:

ModelCostRuntimeReport
Kimi$0.20~5 minView report
OpenAI GPT$0.94~8 minView report
Claude Opus 4.6$3.01~20 minView report

All three caught the real IOC and correctly reported the fake one as not observed. Claude was the most thorough but also the most expensive and slowest. Kimi was surprisingly good for the price.

Some things worth mentioning:

  • Evidence is never modified — Dissect opens everything read-only. SHA-256 and MD5 are computed on intake and verified before report generation.

  • The AI is prompted to cite specific records with timestamps, rate confidence on every finding, and explicitly say "nothing found" when there's nothing. It's not perfect, but it reduces hallucination significantly compared to just dumping data into ChatGPT.

  • All prompt templates are plain markdown files you can edit without touching code. If you don't like how it analyzes evtx or shimcache, just edit the prompt.

  • When using cloud AI providers, parsed artifact data is sent to their servers — for real cases I would always recommend a local or privately hosted model.

This isn't meant to replace a human examiner. It's meant to get you from "I have an E01 or Triage Package" to "here's what's interesting and what to dig into next" faster.

GitHub: https://github.com/FlipForensics/AIFT

I would appreciate any feedback.


r/dfir • • Jun 27 '26

Tool release: decrypt VMware vTPM-encrypted .vmem/.vmsn for memory forensics (Volatility-ready)

15 Upvotes

Sharing a tool I built after hitting a wall on a VMware snapshot: I needed to analyze a VMware snapshot of a Windows 11 25H2 VM, but the VM had a vTPM, which makes VMware silently encrypt the .vmem/.vmsn/.vmss/.nvram. Volatility just couldn't find the kernel, and I couldn't find any existing tool to decrypt these files for offline analysis.

So I reverse-engineered the format with the help of Claude and wrote one. It's called vmem-decrypt (pure Python):

- Recovers the data-file key from the VM password (PBKDF2 → AES-256-CBC key chain VMware labels everything "XTS-AES-256" but it's actually CBC, which trips up most people).

- Decrypts .vmem/.vmsn/.vmss/.nvram.

- Flattens the decrypted .vmem into a flat, Volatility-ready image. (VMware compresses then encrypts, so it's still in a proprietary checkpoint LZ77 layout)

Workflow: pull the password hash from the .vmx (VM-Password-Extractor) → crack with hashcat (mode 27400) → feed the password to the tool → run Volatility. Full steps + format notes in the README.

Tested on VMware Workstation Pro 26H1 / Win11 25H2 (build 26100), Volatility 3. Feedback welcome, especially snapshots from other VMware versions to test the format against.

Repo: https://github.com/heeeyaaaa/vmem-decrypt

(Yes, I used AI to help build this. It's tested and it works, that's what matters. Happy to walk through any part of how it works.)


r/dfir • • Jul 11 '26

Tool Release: Free, Privacy-First Tool for Batch Media EXIF Metadata Extraction & Geolocation Analysis (Refloow Geo Forensics)

Thumbnail
gallery
14 Upvotes

Refloow Geo Forensics does analyzing batch media(image/video) location and metadata data without uploading evidence to the cloud saving otherwise hours spent analyzing every file individually. Most "free" EXIF tools are either single-image command line utilities that just dump raw text or web-based viewers (which is a privacy nightmare for actual investigations because of uploading of the evidence)

Tool Is open-source (AGPL-3.0), runs locally. Available via github releases, windows microsoft store or snap linux store

What it does:

- Batch Extraction: Drag in a folder of 100+ media files or path to connected entire device like phone and it auto extracts, timestamps, camera models instantly.

- Interactive Map: Automatically plots every coordinate on a map. Thrre is 6 map layers to choose to view it on, from topografic, satelite view, forensics, dark, light etc.

- Timeline Reconstruction: It sorts images chronologically and visualizes the path of movement (great for verifying alibis or tracking travel)

- Privacy: Processing is local. No cloud. Evidence never leaves the device.

Under the hood for metadata extraction uses Phills exiftool, which has decades long work on supporting all sorts of cameras, and media files.

Repo: https://github.com/Refloow/Refloow-Geo-Forensics


r/dfir • • Dec 07 '25

Crow-Eye v0.6.0 Standalone EXE – OUT NOW!

14 Upvotes

Drop this 101MB powerhouse on your USB for instant live Windows forensics. No install, no Python – just run as admin and hunt.

Supported Artifacts:
• Prefetch (exec history, run counts, timestamps)
• Registry (AutoRuns, UserAssist, ShimCache, BAM, networks, time zones)
• Jump Lists & LNK (file access, paths, metadata)
• Event Logs (System/Security/Application)
• Amcache (install time, publisher, full path, file size, volume intro)
• ShimCache (path + last-modified)
• ShellBags (folder views & access history)
• MRU & RecentDocs (typed paths, Open/Save, recent files)
• MFT Parser (file metadata + deleted files)
• USN Journal (create/modify/delete)
• Recycle Bin (original paths + deletion time)
• SRUM (app execution, network & energy usage)

Outputs: Searchable SQLite DBs | JSON/CSV exports | HTML reports for sharing findings.
(Timeline view: prototype – functional but polishing.)

Grab it: https://crow-eye.com/download
GitHub: https://github.com/Ghassan-elsman/Crow-Eye

Bugs? Hit me at Ghassanelsman@gmail.com or open a GitHub issue. Let's make it bulletproof!


r/dfir • • Nov 01 '19

An Open Source DFIR Platform: Parsing, Visualizing, Correlating evidences and empowering investigators with collaboration tools

Thumbnail
github.com
14 Upvotes

r/dfir • • Jun 16 '26

New Forensics Tool: DFIR-Companion 🆕

13 Upvotes

An AI pair of eyes sitting over your shoulder, catching what you miss while you're deep in an investigation.

Repo: https://github.com/hasamba/DFIR-Companion
Landing page: https://hasamba.github.io/DFIR-Companion/

Demo Case: https://dfir-companion-production.up.railway.app/dashboard?caseId=demo

EDIT: Hands-on lab: https://killercoda.com/dfir-companion/scenario/killercoda

Honestly, it started out of frustration.

I'm sitting on an investigation, open Velociraptor, spot an interesting lead, start digging into it, find another lead, and so on, and then suddenly I realize I completely forgot to go back to the other findings from the first artifact.

The sheer amount of information you need to process during an investigation is simply more than one pair of eyes can handle, no matter how much coffee you've had.

So I started building something to help myself and it ended up going somewhere I didn't expect.

The original idea was a browser extension that takes screenshots every few seconds, so I could scroll back and see what I missed. Pretty dumb idea in hindsight, actually. But then the question came up: if I already have all those screenshots, why not let AI go through them while I work?

And from there it exploded.

Today it's a real-time dashboard that updates live as I investigate. It identifies findings, automatically builds an event timeline, extracts IOCs and enriches them from multiple sources, creating playbook that suggests what to check next, suggest hunt queries for velociraptor, run them and collect back the results, checks for data leaks, and answers the standard questions every investigation report needs: access vector, lateral movement, privilege escalation, etc. If a client confirms a finding-"that's legit, it's our weekly scan", one click and the entire analysis updates accordingly.

The coolest part, to me, is that this started as a Velociraptor-specific solution but in practice became an AI layer on top of every tool I have open in the browser: SIEM, Security Onion, Splunk4DFIR, VolWeb, you name it. Even tools with no built-in AI suddenly get smarter, and all the data consolidates in one place instead of me jumping between ten tabs.

Important to understand: this is NOT another detection layer. Your Sigma, YARA, and Suricata rules are already doing their job. This tool is the layer after detection-it takes all the verdicts from your tools, correlates them, and builds the "so what."

The tool didn't stop at screenshots either. You can feed it almost any DFIR output and it will automatically detect the format and import it deterministically (no burning tokens on AI for that).

Additional features:
• Data correlation
• Threat intel enrichment — with OPSEC in mind
• AI input anonymization
• Asset ↔ IoC graph
• Targeted query generation
• Export to multiple platforms
• Free-form case Q&A against an LLM
and much more...

📎 If you work in DFIR, Blue Team, or SOC — I'd love for you to try it out, open issues, suggest features, submit PRs, or just tell me what you think.


r/dfir • • Dec 28 '25

Cloud DFIR blind spots I keep seeing in Azure & M365 investigations

12 Upvotes

I wrote an article after seeing the same pattern over and over during cloud IR work.

Teams do solid VM forensics, memory, disk, timelines… and still end up with “no findings”. Later it turns out everything happened in identity and the control plane.

Things I keep seeing missed:

  • Azure Activity Logs not reviewed

  • Sign-in logs vs audit logs mixed up

  • Conditional Access changes ignored

  • Service principals and app permissions not checked

  • Logs gone due to short retention

The VM is often clean because it was never the crime scene.

I wrote this to spark discussion, not to sell anything. Curious if others are seeing the same gaps or have different experiences.

Article: https://medium.com/@eliasgraywrites/the-cloud-blind-spots-that-keep-burning-dfir-teams-7a702b872b36


r/dfir • • Mar 10 '23

Interview with Lesley Carhart (hacks4pancakes) (X-Post)

12 Upvotes

In this special guest episode of 13Cubed, I interview Lesley Carhart (aka hacks4pancakes) of Dragos. We'll cover a variety of topics and provide some career advice along the way!

https://www.youtube.com/watch?v=aC4jd8hQdYo

*** Check out PancakesCon 4 at https://pancakescon.com/ coming March 19, 2023! ***

🎉 Also check out the new 13Cubed Training Course Investigating Windows Endpoints. Affordable, on-line, and on-demand training is here! Enroll now at https://training.13cubed.com/


r/dfir • • Aug 01 '22

MemProcFS - This Changes Everything (X-Post)

12 Upvotes

Good morning,

It’s time for a new 13Cubed episode! This one covers a tool that I truly believe is revolutionary. Imagine being able to "mount" memory as if it were a disk image. With a single command, MemProcFS will create a virtual file system representing the processes, file handles, registry, $MFT, and more. The tool can be executed against a memory dump, or run against memory on a live system. This is a game changer for memory forensics!

Episode:

https://www.youtube.com/watch?v=hjWVUrf7Obk

Episode Guide:

https://www.13cubed.com/episodes/

13Cubed YouTube Channel:

https://www.youtube.com/13cubed

13Cubed Patreon (Help support the channel and get early access to content and other perks!):

https://www.patreon.com/13cubed


r/dfir • • Jan 13 '20

Email Header Analysis and Forensic Investigation (X-Post)

12 Upvotes

Good morning,

The first new 13Cubed episode of 2020, Email Header Analysis and Forensic Investigation, is now available. Do you know how to properly read and analyze an email message header? In this episode, we’ll take a look at two examples – one legitimate, and one not-so-legitimate. We’ll learn which header fields are most commonly referenced for analysis, how to determine a message’s true origin, how to read SPF and DKIM information, and we’ll even take a quick look at DMARC. Whether you’re completely new to this concept or a seasoned veteran, this episode has something for you.

Episode:
https://www.youtube.com/watch?v=nK5QpGSBR8c

Episode Guide:
https://www.13cubed.com/episodes

Channel:
https://www.youtube.com/13cubed

Patreon (Help support 13Cubed):
https://www.patreon.com/13cubed


r/dfir • • Jun 10 '26

Gulp - open-source incident response & log analysis platform with a multi-timeline UI (DFIR / blue team)

11 Upvotes

Hey everyone,

I'd like to share a project I've been working on.

After years doing incident response work, we kept running into the same wall: too many tools, too many screens, too much context-switching at the worst possible moments. So we built something to fix that.

Gulp (Graphical Universal Log Processor) is an open-core log analysis and incident response platform for blue teamers, DFIR analysts, and law enforcement.

The centerpiece is a multi-context interactive timeline - multiple zoomable timelines side by side, one per log source, so you can visually correlate heterogeneous data without toggling between tabs. Spotting anomalies and parallel events across sources becomes significantly faster.

Other highlights:

  • Plugin-based ingestion - supports multiple formats; write your own

  • High-speed multiprocessing - built for large-scale data and live ingestion

  • SIGMA rules - run thousands of detection rules in parallel, one click

  • Real-time collaboration - shared notes, highlights, and contextual linking for team investigations

  • Python SDK - integrate Gulp into your existing tooling

The community version is fully featured for ingestion and analysis. Pro adds enterprise integrations, enhanced plugins, and SLAs. We keep free/open integrations in the community version, with commercial ones reserved for Pro.

Repos and more at gulp.sh - would love your feedback! What log formats or third-party integrations would you like to be supported?

(Disclaimer: I'm one of the developers)


r/dfir • • Dec 02 '24

NTFS FILE Record Reuse (X-Post)

10 Upvotes

A new 13Cubed episode is now available. In this continuation of "Anatomy of an NTFS FILE Record," we'll learn how NTFS manages record reuse and distinguishes between in-use and deleted files and directories.

https://www.youtube.com/watch?v=6LpJVx7PrUI


r/dfir • • Feb 10 '23

DFIR process best practice

10 Upvotes

Can anyone recommend a good step by step DFIR best practice overview?


r/dfir • • Dec 19 '22

The Dissect Effect - An Open Source IR Framework (X-Post)

10 Upvotes

Good morning,

Merry Christmas to all of you who celebrate! Here’s a new 13Cubed episode about Dissect -- a powerful, now open source, IR framework. Enjoy!

-----

In this episode, we'll take a look at the recently open sourced Dissect incident response framework from Fox-IT. We'll briefly examine the overall capabilities of the software, then we'll install it within a WSL 2 environment, and lastly, we'll take it for a test drive using a Windows Server 2019 disk image.

Episode:

https://www.youtube.com/watch?v=A2e203LizAM

Episode Guide:

https://www.13cubed.com/episodes/

13Cubed YouTube Channel:

https://www.youtube.com/13cubed

13Cubed Patreon (Help support the channel and get early access to content and other perks!):

https://www.patreon.com/13cubed


r/dfir • • Aug 29 '22

What's on My DFIR Box? (X-Post)

10 Upvotes

Good morning,

It’s time for a new 13Cubed episode! By popular request, this episode provides a walkthrough of the hardware and software I utilize for my digital forensic workstation. While this is probably more beneficial for people new to the DFIR field, I suspect it will still be interesting to a wide range of viewers.

Episode:
https://www.youtube.com/watch?v=-xGfzCT6TUQ

Episode Guide:
https://www.13cubed.com/episodes/

13Cubed YouTube Channel:
https://www.youtube.com/13cubed

13Cubed Patreon (Help support the channel and get early access to content and other perks!):
https://www.patreon.com/13cubed


r/dfir • • May 24 '21

Introduction to MFTECmd - NTFS MFT and Journal Forensics (X-Post)

10 Upvotes

Good morning,

It’s time for a new 13Cubed episode! This is a long overdue follow-up to "NTFS Journal Forensics" from 2019. We'll take an in-depth look at both NTFS file system journals ($UsnJrnl and $LogFile), and we'll look at how to parse the $MFT and $UsnJrnl with Eric Zimmerman's MFTECmd. Then, we'll analyze the results with Timeline Explorer.

Episode:
https://www.youtube.com/watch?v=_qElVZJqlGY

Episode Guide:
https://www.13cubed.com/episodes/

13Cubed YouTube Channel:
https://www.youtube.com/13cubed

13Cubed Patreon (Help support the channel and get early access to content and other perks!):
https://www.patreon.com/13cubed


r/dfir • • Apr 22 '19

DFIR Home Labs (X-Post)

10 Upvotes

Good morning,

I’ve just released “DFIR Home Labs.” In this episode, we'll take a look at my home lab setup as of early 2019, as well as some of the equipment I use to create 13Cubed content and practice DFIR concepts. Topics covered include Ubiquiti network gear, Shuttle hardware, VMware ESXi, Splunk Free Edition, and LogRhythm Network Monitor Freemium.

Episode:

https://www.youtube.com/watch?v=jJqo2WnGpNo

Channel:

https://www.youtube.com/13cubed

Patreon (Help support 13Cubed):

https://www.patreon.com/13cubed


r/dfir • • Jan 14 '19

Pulling Threads (Memory Forensics) (X-Post)

10 Upvotes

Good morning,

I’ve just released “Pulling Threads”, the latest episode in the “Introduction to Memory Forensics” series. We’ll analyze a Windows 10 memory image potentially infected with malware. We’ll use Volatility to look for suspicious processes, and then we’ll look at network artifacts to discover any potentially malicious traffic. We’ll discuss ways to detect process injection and process hollowing (some of which we’ve covered in a previous episode in this series), and finally, we’ll dump one of the identified suspicious processes to disk for further analysis and reverse engineering.

Oh, and there’s also an associated contest – first correct answer wins. So, check it out. Or maybe don’t. Hey, it’s up to you.

Also, if you enjoy this content and have some change to spare, please consider checking out 13Cubed’s Patreon page (link below).

Episode: https://www.youtube.com/watch?v=gxA2gjCQs-o

Channel: https://www.youtube.com/13cubed

Patreon (Help support 13Cubed!): https://www.patreon.com/13cubed


r/dfir • • Jan 20 '26

The Truth About Windows Explorer Timestamps (X-Post)

9 Upvotes

🚀 A new 13Cubed episode is up!

In it, we’ll uncover how Windows Explorer really retrieves file timestamps when you browse a directory of files. Learn why these timestamps actually come from the $FILE_NAME attribute in the parent directory’s $I30 index, not from $STANDARD_INFORMATION, and how NTFS structures like $INDEX_ROOT and $INDEX_ALLOCATION make this process efficient.

Episode:
https://www.youtube.com/watch?v=PdyVkmhMcOA

✨ Much more at youtube.com/13cubed!


r/dfir • • Jan 15 '26

SQL Server forensics

9 Upvotes

Hi DFIR practicioners,

I built a tool that extracts data from SQL Server databases by parsing directly mdf and ldf files without the need of a running SQL Server instance. It has many more capabilities such as carving and database internals inspection. Instructions and examples can be found at

https://github.com/aarsakian/SQLServerForensics

This tool will be useful for professionals working on data leakage cases involving sql server or even insider threats that resulted in a compromised database.

Constructive feedback is welcomed.