cam garrison

Cybersecurity & network systems administration student. I learn the quiet machinery underneath enterprise IT — then I use it to build things people actually feel: sites, apps, and experiences where the technology disappears and only the effect remains. This page is the public-facing record.

Discipline Cybersec & NetSys Admin

School Univ. of Cincinnati

Class Of May 2028

Sector Cincinnati, OH

WALLACE CORP REGISTRY NEXUS-9 PERSONNEL CHANNEL VOIGHT-KAMPFF: CLEARED BASELINE STABLE ACCESS GRANTED — NX-1324 "CELLS INTERLINKED WITHIN CELLS INTERLINKED" UPLINK NOMINAL REPLICANT QUOTIENT 0.000 WALLACE CORP REGISTRY NEXUS-9 PERSONNEL CHANNEL VOIGHT-KAMPFF: CLEARED BASELINE STABLE

▣ ARCHIVE TRANSMISSION ▣

"We were brought up to believe everything could be diagnosed, patched, hardened. The truth is messier. Networks dream too — they just dream in packets, in retransmits, in the static between heartbeats."

— OPERATOR LOG / NX-1324 / FRAGMENT 07

01 /// FILE

identity

// who is registered to this archive

I'm a Cybersecurity & Network Systems Administration student at the University of Cincinnati. Doing the degree by day, running labs and reading writeups by night, and slowly figuring out which corner of this field fits me best. So far the answer is "wherever the infrastructure is most obviously held together by tape, documentation, and somebody's heroic 2014 PowerShell script" — and I mean that as a compliment.

Outside of class I've spent the last two summers doing internships across cyber operations and enterprise systems engineering. Between them I've gotten to put hands on the parts of IT that nobody puts on a brochure — endpoint imaging at scale, AD policy archaeology, on-prem-to-cloud co-existence, the cabling that holds an office together, and the strange, specific intimacy of debugging a backup job at 11pm on a Thursday.

"More human than human" is not a slogan. It is a specification. And specifications, in this profession, are the difference between a system and a wish.

I care most about the unglamorous parts done well — clean baselines, documented configurations, the small set of habits that make a system survive an audit and a Tuesday at 3am with equal grace. The flashy stuff is downstream of that. I would rather be the engineer who never has to explain why something failed than the one with the best war story.

Where I want to take this: the place where infrastructure meets wonder. I'm drawn to experience design and themed entertainment — the discipline of hiding the technology so completely that what's left is a feeling. The same instincts that keep a system surviving an audit at 3am are the ones that make an experience feel effortless. Rigor underneath, magic on top.

This site is a working notebook. Builds is the portfolio — live, shipped work I designed end to end. Background is the formal record. Field Notes is where I write up things I've learned the hard way. The Archive is for the parts that don't belong on a résumé.

▸ See the Builds

02 /// LOG

recent deployments

// short summary — full record on the background page

INTERNSHIP MAY 2026 — AUGUST 2026 ▸ ON-SITE

systems engineer intern

MEDPACE // enterprise infrastructure

INTERNSHIP JUNE 2025 — AUGUST 2025 ▸ ON-SITE

cybersecurity intern

NCUS // cyber operations

Endpoint lifecycle, system imaging, and OS deployment across multiple facilities.
System hardening, baseline security configurations, and cyber insurance readiness.
NIST-aligned documentation, custom Ethernet runs, and a lot of "why is this not in the GPO yet."

▸ Full Background File