Posted in Cybersecurity Careers

Early in my career, a cleanup I deployed wiped a professor's work. The account that triggered it was never…

Daniel O. — Senior Cybersecurity Consulting Engineer | EDR/XDR · Zero Trust · Architecture & Engineering | CISSP · CCSP · GIAC

Early in my career, a cleanup I deployed wiped a professor's work. The account that triggered it was never supposed to be on his computer.

A friend helped me get a job babysitting computers and their users in one of my university's computer labs, and I worked up from there. Over about three years I went from fixing lab machines, to desktop support for faculty and staff, to servers and networking for the full-time sysadmins. Before I left, I trained my replacement.

The cleanup was a policy I deployed to delete local files from the lab machines. What nobody in central IT knew was that a teaching assistant had purloined a lab login and was using it to log into their professor's computer. The cleanup ran under that login on his machine and wiped the edits he'd saved locally. The original data lived elsewhere, so it cost him rework, not his research. No one was happy, and my management took some heat for it. Working an IT gig, I learned that people use systems in ways nobody plans for.

That’s the kind of judgment security work runs on. Every control eventually meets someone using an account in a way nobody documented, and you learn to expect that by supporting real, unpredictable users.

After graduation, a headhunter I met at a job fair helped me find my first full-time job. No referral. I'm still convinced the university work was the biggest reason I got interviews and offers. That job was at a company with about 35 employees, two servers, daisy-chained 10 Mb switches and a 768k internet connection. If it had a plug, it was my responsibility.

Most of the security people I know came in through IT, me included. That path still works.

You've probably seen headlines about a cybersecurity worker shortage. ISC2's 2024 workforce study estimated the gap at 4.8 million workers, and its 2025 study stopped publishing that number. My read is that the shortage is real, but it's for mid-level and senior people. Companies want more of them than they can find, which is a different thing from wanting to hire someone to train from zero. It's why postings labeled entry level ask for three years and a cert or two, and that's not a typo.

Your first full-time job is going to be harder to land than mine was. What helps is real IT experience, projects you can point to, and people who know your name. My path started with the same friend who showed me tech could be a good career.

Shortly before graduation, I asked a couple of professors how I could get someone to let me work on their networks. Their answer was something like "That's hard." Today people ask me the same question about cyber, and the honest answer hasn't changed much. Don't get hung up on starting in cyber. Get in the door however you can, and pivot once you've proven you won't wipe too many systems inadvertently.

#Cybersecurity #CareerAdvice #EntryLevel #ITCareers #LessonsLearned

Early in my career, a cleanup I deployed wiped a professor's work. The account that triggered it was never…

4 reactions · 2 comments

Topics: #careeradvice, #lessonslearned, #itcareers, #entrylevel, #cybersecurity

Comments

Daniel O.: This one started as a section of a longer article on getting into cybersecurity. The full article covers more ground, and it links to every post pulled from it. https://cyberr.ai/post/b5f53c3b-e255-4834-9237-2d5c904e7fff

Victor Font: Daniel, your experience illustrates something that often gets overlooked in cybersecurity career discussions: technical knowledge and operational judgment are not the same thing. The latter develops through experience, particularly when systems behave exactly as configured but produce consequences nobody anticipated. Your cleanup incident is a perfect example. The control worked, but the assumptio

Read and join the discussion on Cyberr