Why this page exists
Some people want vibes. Some want receipts.
This is the receipts page: qualifications, operating principles, and the constraint set. Not because I’m trying to impress anyone — because clarity is cheaper than confusion.
What I do (in plain English)
I build programs and lead initiatives for a police department that supports and protects a school district. Most of the work is boring by design: policies, evidence workflows, device management, and security posture that has to hold up under audit, stress, and real-world use.
If it doesn’t survive contact with reality, it doesn’t ship.
Current lane: Police technology + evidence
Recent and ongoing work includes:
- Building a digital evidence program (policies + consent-to-search forms, repeatable workflows)
- Deploying and administering CJIS-aligned technology controls, including MDM and MDTs
- Deploying body-worn cameras and authoring usage policies
- Maintaining P25 radio programming (because comms failure is not a “nice to have”)
Proof artifacts (sanitized)
Not case details. Not sensitive internals. Just the kind of work product that proves “this is real.”
- Digital Evidence Program (foundation build): drafted and implemented department policies, workflow expectations, and consent-to-search documentation to make evidence handling repeatable and defensible.
- CJIS-aligned posture (practical controls): deployed and currently administer MDM to enforce device security baselines (access controls, configuration standards, and audit-friendly posture) alongside MDT hardening practices.
- Body-worn camera deployment + policy: rolled out body cameras and authored the usage policy so the tech doesn’t outpace procedure.
- P25 radio programming maintenance: maintained the radio template/programming layer because “comms working” is a safety requirement, not a convenience feature.
- Operational documentation: built SOP-style documentation that survives tired humans and turnover (the quiet difference between “we have a tool” and “we have a program”).
Tooling I’m fluent in
I treat tools as tools — useful, fallible, and never magical.
- Cellebrite (extraction/processing workflows)
- Magnet (analysis support and review workflows)
- IBM MaaS360 (MDM administration)
- DataPilot (device operations / practical workflows)
- Utility (supporting workflows)
Education & certifications
- AAS in Cybersecurity (2022) — graduated with honors
- Bachelor’s in progress — expected graduation 2027
- CompTIA A+
- Network+ (in progress)
- Previously held: Security+ and CySA+
Military background
USMC Sergeant, 2006–2011.
MOS: 5954 — ATC Maintenance Comm Tech.
That experience shows up today as: discipline, systems thinking, and an allergy to fragile processes.
Teaching / public work
I’m actively building training materials for:
- PTAs
- church groups
- parent groups
This work runs under the Safe Screens Weekly banner, and the aim is calm competence: fewer panicked headlines, more usable guardrails.
The ethics line
I don’t do gray-area work. I like sleep.
- No deceptive surveillance-for-fun projects
- No “security theater” sold as security
- No trust-eroding growth hacks
- No work that becomes courtroom material later
If something isn’t a fit, you’ll get a clean redirect instead of a slow ghost.
Route me
- Start: /start/
- Dispatches: /dispatches/
- Advisory: /advisory/
- Contact: /contact/