I'm a fourth-year BS Computer Science (Robotics) student (irregular, SY 2026–27) working toward 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.

I do most of my work from a computer shop here in Bambang, Nueva Vizcaya. I don't have a rig of my own yet, so I'm building a cybersecurity skill set on limited resources — free labs, open-source tools, and a lot of persistence. I'm saving up to fund paid certifications and build my own PC, partly through being outsourced by the Provincial Government of Nueva Vizcaya, working under the guidance of the PDRRMO on the One Vizcaya project.

Resource limits aside, I document every project as if it were a real engagement and publish it so it can be reviewed end to end. The goal is simple: let the work speak for itself, and keep climbing the certification roadmap toward OSCP.

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.

No projects match that combination.

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.