Gh0stlyKn1ght
Robotics • Security • Autonomy
Phase 1 · Project 02

Embedded Security Workflow (Arduino / ESP32)

I want better reflexes with firmware and low-level access: read the bits, poke serial, fuzz lightly, and see what breaks. This is me setting habits before things get complex.

← Phase 1 Research Log

Plan
Scope
What I'm focusing on
  • Reading firmware
  • Serial communication inspection
  • Basic fuzzing
  • Attack surfaces: overflow, logic abuse
  • Defining a “secure microcontroller workflow”
Cost

$25–50

Why it matters

Embedded devices power everything I touch later. If I practice security here, I won’t be guessing when it counts.

Logs
In progress
Log 1: Firmware extraction + tooling

Note how I pulled the firmware, set up tools, and what failed along the way. Keep commands handy for reuse.

Log 2: Serial behavior + fuzz tests

Watch serial I/O, map message shapes, and do light fuzzing. Log crashes/hangs and how I mitigate them.