IT • Cybersecurity • Web • Digital Forensics

IT, Cybersecurity, Web Dev, and Digital Forensics — without the fluff.

Hands-on consulting, incident-ready hardening, and practical guides for teams who want fewer fires and better evidence.

Built for reality: audits, incidents, migrations, and Monday morning chaos.

Projects in the lab

Build logs and write-ups: storage, OSINT, automation, forensics tooling.

View all →

Forensics Byte Homelab Build Log

Phase 2: First Power-On and Platform Validation

Status

The NAS host is alive. Phase 2 wraps up with a clean POST, both NVMe boot drives visible, the HBA detected and reporting correctly, and the BIOS configured for a TrueNAS SCALE install. The platform is ready. The next log entry is where the real storage work begins.

Where Phase 2 Started

Phase 1 left off with the hardware fully assembled: the MSI PRO B760M-P DDR4 seated in the case, the Intel i5-12500 in the socket, 64GB of DDR4 at 3200 MHz across the slots, two WD Blue SN5000 500GB NVMe drives in M2_1 and M2_2, and the LSI HBA tucked into a PCIe slot. Everything was physically in place. Phase 2 was supposed to be the easy part: flip the switch, confirm a POST, start poking around BIOS. That is mostly how it went, except for a detour that took longer than it should have and taught a lesson I already knew but apparently needed a refresher on.

Homelab Build Log, Phase 1: The NAS Takes Shape

This is the first entry in what I expect will be a multi-part build log. The full homelab is a dual-host setup, and I am splitting it deliberately into two machines with two very different jobs. This post covers the NAS, which is the first host to reach a meaningful assembly milestone. The second host, a Proxmox compute node, will get its own thread once the NAS is stable and running.

Overview

There is something satisfying about building infrastructure from scratch, not because the process is always smooth, but because every decision leaves a visible trace in the final result. This post documents the current state of my home lab, a two-host architecture that separates dedicated NAS duties from a virtualization platform. It covers the hardware inventory, how services are distributed across the two hosts, the decision forks I worked through during the build, and the real-world market pressures that shaped what I actually purchased versus what I originally planned.

Latest from the blog

Guides, field notes, and teardown posts.

View all →

Geofence Warrants: A Governance-First Framework for Getting Them Right

Geofence warrants can give investigations life when leads run dry, but they also sweep in bystanders and can accelerate tunnel vision. I’m pro tool, pro rule. The only way this capability stays viable is by building guardrails that are credible to judges, juries, and the public, while still letting investigators do their job.

Mar 1, 2026 Read →

Why I’m Conflicted About Automatic License Plate Readers

Why I’m Conflicted About Automatic License Plate Readers

In policing, some technologies are like a hammer. Simple tool, obvious purpose. ALPR is not that.

Automatic license plate readers can help recover stolen vehicles, locate missing people, and generate time-sensitive investigative leads. They can also be misused in ways that feel uniquely invasive, because they turn everyday movement into a searchable historical record.

Both outcomes are documented in the real world. That’s why I’m conflicted.

Feb 8, 2026 Read →

Policing’s Hard Truth: Use Every Advantage, Govern Every Power

Policing is a cat-and-mouse game, and the mouse usually plans first. That reality creates pressure to use every lawful advantage to stop harm and solve cases. But it’s also why law enforcement has to hold itself to a higher standard, because ethical drift is real: shortcuts become habits, habits become culture, and culture decides what happens when nobody is watching. This precursor sets the rule for the series: powerful tools require stronger guardrails, or legitimacy erodes and everyone loses.

Feb 7, 2026 Read →

How engagements work

Clear scope. Clear deliverables. No mystery meat consulting.

1) Diagnose

We define constraints, map risk, and agree on a finish line before touching tools.

2) Implement

Hardening, fixes, builds, or migrations with documentation you can reuse later.

3) Hand-off

Runbooks + training + optional retainer support so the solution survives Monday.

Get the Field Notes

Occasional emails: tactics, checklists, teardown posts. No spam. No motivational posters.

Subscribe / Contact