I'm a third-year BS Computer Science (Robotics) student focused on becoming a purple-team security engineer — someone fluent in both offense and defense. My approach to every project is the same loop: run a realistic attack, watch it from the defender's side, then write the detection that closes the gap.
Outside the lab I lead development on a government-facing community reporting platform, train as a competitive recurve archer, and work steadily through a cybersecurity certification roadmap toward OSCP.
Every project here is built in an isolated home lab on hardware I own, documented as if it were a real engagement, and published so it can be reviewed end to end.
A platform serving the people of Nueva Vizcaya, bringing local services and information into a single app. My focus is the backend architecture and security — building reliable APIs, hardening authentication, and keeping user data protected.
A purple-team build plan — red and blue projects across offense, defense, and general security. Each becomes its own documented repo as I complete it.
My certification roadmap, ordered by priority and cost — free wins first, then the credentials that prove I'm Purple, building toward OSCP.
My self-directed path from CS student to Purple Team — a four-stage plan built on hands-on labs, not just checklists. The through-line is the Purple loop: run the attack, detect it, write the rule that catches it.