Daniel O.
Nashville, United States · Senior Cybersecurity Consulting Engineer | EDR/XDR · Zero Trust · Architecture & Engineering | CISSP · CCSP · GIAC · HighPoint
Middle Tennessee State University (MTSU)
10 followers
About
Security that sounds right in a planning session and fails in production usually has the same root cause. The controls were designed without a real understanding of the systems they were meant to protect. I came up through systems and network administration. Twenty-five years in IT and cybersecurity, including a move into security architecture and engineering, put me on both sides of those failures. I have designed controls and I have been called in when they fell short. I have spent plenty of nights helping pick up the pieces. That work is satisfying. The better engagement is the one where nothing breaks and clients eat dinner with their families.My focus is endpoint detection and response (EDR), extended detection and response (XDR), Zero Trust architecture, and security consulting across enterprise environments. I have worked across more product categories than I care to count. What I have learned is that the tools are not the hard part. Making them work together, turning a collection of point solutions into an integrated security posture, is where most programs struggle. In practice that means CrowdStrike Falcon, Microsoft Defender XDR, Entra ID, Intune, Zscaler, Okta, and the integrations that connect them. When those integrations do not exist, I build them in PowerShell, most often against on-premises Active Directory or Entra ID through the Microsoft Graph API.I hold the CISSP and CCSP, and multiple GIAC certifications across detection, incident response, and forensics.The range matters: media, healthcare, federal contracting under a clearance, and organizations from under 50 people to Fortune 500. Every engagement has constraints nobody briefed me on going in. Finding the practical path through those is most of the job.If you need someone to assess what you have and tell you plainly what to fix first and why, that is the work I do. The systems and networking background means your IT team and I speak the same language, which is usually what makes security land. If the plan already exists and needs to be executed correctly, I will work with your team to make sure it holds up in production.
Specialties
- EDR
- Risk Management
- Security Engineering
- Security Strategy
- Zero Trust Architecture
Skills
- AI Security
- Active Directory
- Architecture
- CIS Critical Security Controls
- Cloud Security
- Cofense PhishMe
- Communication
- Crowdstrike Falcon
- Cyber Defense
- Cyber-security
77 skills in total
Licenses & Certifications
-
GIAC Defending Advanced Threats
GIAC / SANS
Issued Sep 2021 · Expires Sep 2029
-
Certified Cloud Security Professional
ISC²
Issued Jun 2021 · Expires Jun 2030
-
GIAC Certified Detection Analyst (GCDA)
Global Information Assurance Certification (GIAC)
Issued Jun 2020 · Expires Jun 2028
10 certifications in total
Experience
-
Senior Cyber Security Consultant
HighPoint
May 2025 — Present
-
Senior Cyber Security Engineer
Fluor Federal Petroleum Operations, Strategic Petroleum Reserve
Sep 2019 — May 2025
-
Enterprise Information Security Architect | Senior Cyber Security Engineer
Lifepoint Health®
Aug 2017 — Sep 2019
Brentwood, TN
7 experiences in total
Education
-
Middle Tennessee State University (MTSU)
Master of Science, Computer Information Systems
Jan 2004 — Jan 2006
-
Murray State University
BS, Computer Information Systems
Jan 1993 — Jan 1999
Repositories
-
0x44616e69656c/build-lab
Stands up a lab Active Directory domain controller from an ISO in one command: builds the Windows Server 2025 VM, promotes the forest, and stages a lived-in AD domain that populates itself at your first Administrator logon. I designed this because I like a fresh lab environment, but I do not like building a lab for the umpteenth time.
PowerShell · 1 star
-
0x44616e69656c/new-AdDomain
Stands up a fresh Windows Server 2025 Active Directory forest and fills it with realistic-looking users, groups, computers, service accounts, GPOs, and a certificate authority. Built for labs, demos, red-team ranges, and SIEM testing, not for production.
PowerShell · 2 stars
-
0x44616e69656c/New-VMwareWorkstationVM
Unattended Windows Server 2025 deployment to VMware Workstation. One command. No ADK. No clicking through Setup. If you have ever sat there pressing Next through Windows Server Setup on a VM you know you are going to rebuild three days from now, this is for you.
PowerShell · 2 stars
Recent posts
I fail three out of four attempts at drawing a stick person, and the art on this post is 100% AI generated.
I use fairly extensive prompting, and some images take several re-prompts to turn out the way I want. In general the process works for my needs.
The art is one example of how I use AI. It makes me better at things I already do, and it lets me take on tasks I am completely unqualified for. I think the result is better overall. Each kind of use carries its own risks, and I explore some of them here.
This post was AI edited, though when I wrote this sentence it hadn't been yet. I frequently use AI, with a strong personalized writing prompt, to edit and occasionally rewrite what I have already drafted.
My goal is to keep my voice and thoughts my own. I look at AI editing kind of like having an editor following me around, which is a luxury I could not otherwise afford for a LinkedIn post or an email.
What I do not do is allow AI to draft communications. Well, mostly. I find even with a strong prompt, AI tends to be a bit verbose. Thorough is good up to the point the recipient refuses to read what I have written. Funny enough, I sometimes have the same issue with my own writing.
I say mostly because I do allow auto-drafting of some documentation files. I still do manual edits, but honestly, for technical writing, AI's verbosity can be a win. It includes steps I would leave out, because once I have worked with something long enough, they become second nature. Microsoft could learn from this left-out-step lesson in their technical walkthroughs.
I use AI heavily in my coding projects. I use different processes depending on whether this is work or a personal project, but both involve AI. Work still gets more hands-on review and hand-written code that I end up having beautified by an agent. I still believe anything done for a paying customer should get a human review.
Personal coding projects are mostly AI written, and heavily AI reviewed. AI even directs the work lanes, so I end up becoming a manager reviewing planning and work product rather than a collaborative coder. Most of my friends who are coders do this, but I can't bring myself to do that for client work. I have real worries about giving up this much control, but for the moment, I can't argue with the results. I'm now creating projects I would never have tackled due to scope or complexity.
That carries its own risk. As the projects get more complex, they can outgrow my ability to judge the work.
In several projects I have started using AI to prompt AI, with mixed results. On the positive side, this helps me make sure I get exactly what I am looking for by creating good guardrails. On the negative side, these generated prompts can be "too good" and end up limiting the worker AI in undesirable ways. When creating review prompts I have noticed that the AI is very good at creating prompts that cover exactly what it thinks needs to be looked at, saving wasted tokens but at the expense of coverage. I tend to mitigate this by doing rounds of very loosely scoped reviews between AI-generated reviews to allow the reviewer agent to run wild. This is an area I am still improving my skills in, and I use it to different extents depending on the task.
As I have written before, I have legitimate concerns about deskilling, but I also see areas where AI has improved my efforts. I believe my writing has improved, or at least I'm happier with my hand-written first drafts than I was a year ago. On the flip side, I struggle less with new coding tasks, so I do have my doubts as to whether the lessons learned will stick.
This post is very meta about my methods. Is it useful, or at least interesting? Is there any interest in more coverage of them?
I've worked with the same colleague at three different companies. We met at the first one. I referred him to the second. He referred me to the third.
I've had other jobs start the same way, with a former manager or peer reaching out to suggest I apply. Some turned into jobs. Others weren't a good fit. Either way, the referral meant I came in with a better idea of what was on offer, and they came in with a better idea of me.
The first career advice I ever got pointed the other way. The summer before my freshman year, I met a software developer doing some side work at the school where my mother worked. He told me to have no loyalty, because the companies I'd work for would have none for me. He was an early believer in jumping early and often.
He wasn't totally wrong. I've worked for companies that felt mercenary, and others that meant it when they said the team was like a family. But he left out two things. The first is that your loyalty doesn't have to go to the company. It can go to the people. Companies move on when you leave. Good colleagues remember you, and they're the ones who mention your name when a job opens.
The second is pride. Doing good work matters whether or not the company appreciates it. They're paying you to be a professional, so be one.
As for jumping early and often, it has its own costs, which the longer article this came from gets into.
If you're just starting, you may think you don't have connections yet. You probably have more than you think. Classmates, professors, anyone you've worked with in any job, people you met at a conference, friends of friends or relatives, even a chance conversation with a stranger. My own first IT job during college came through a friend.
So use them. This may be a bit controversial, but life isn't fair. If someone can get you the inside track, take it. At best it gets you an interview. After that it's on you, but getting the chance to make your case is often the hardest part.
Internships count here too. They were rare when I was in school, and I never did one, but they're far more common and important now. Do them while you're eligible. Something in cyber is great, but any IT internship is good, and anything that puts you in a corporate environment still beats nothing. Employers want to see that you already understand how companies work, so they don't have to teach you that before the job they hired you for.
Do good work for the people next to you. Some of them will be the ones who mention your name later.
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
I asked a client for their last pen test report and was shocked at how thin it was. I knew the firm that did the work. They had smart, experienced people. It wasn't a puppy mill pushing juniors through engagements. So what happened?
A few days later I got the rest of the story, including the scope and rules of engagement. The tester had been put in a straitjacket and locked in a room. They couldn't pivot between machines. They couldn't use any credentials they captured. Every exploit needed explicit approval, one at a time. Significant parts of the estate were off limits. On paper it was a pen test. In practice it was closer to a vulnerability scan with a glorified cover page.
The client dictated those restrictions. They told me so. That was their right, and the security firm still sold the result as a pen test. I never met the tester, but my read is they got handed a signed contract and told to deliver on it, and they did what they could inside the box.
Nobody came out of it well. The firm put its name on a report that looks weak to anyone who knows what a pen test report is supposed to look like. Read cold, without the scope in hand, it makes the tester look like they'd done less than the minimum. The client got a mostly clean report and could tell their own customers they had no High or Critical findings. The report did list constraints, in a boilerplate paragraph. Nothing in it told a reader how much of the environment had never been looked at. And everyone signed off.
A coverage statement on page one would have made the gaps visible. The client might not have wanted it, and the firm might have lost the work.
Every decision you make carries your name, or your company's. That's true in consulting, and it's just as true in a corporate seat.
Here's the in-house version. The CIO reads the draft report and says, "That Critical seems too high. An attacker would have a hard time even reaching it. Let's move it down so it doesn't freak out the board." You already accounted for that difficulty when you rated the finding Critical. If someone can show you missed something, revisit it. "It will upset the board" isn't evidence.
If you accept that feedback without pushing back, you aren't doing anyone a favor. The board is now making risk decisions on a picture you know is wrong, and you drew it. I promise, no one will remember the conversation during the breach.
I'm not telling you to refuse to be reasonable. I've had to bend more than once in my career. Usually it takes conversation and negotiation to find a version everyone can accept and be at least a little unhappy with. Having said that, I can negotiate scope, wording, and how we explain a finding. I can't sign off on a conclusion I know the evidence doesn't support. That's where compromise becomes unethical.
Your name is on the document. Make sure it holds up in a room full of people who know better. You won't be in that room to explain it.
#Cybersecurity #Integrity #ProfessionalEthics #Accountability #SecurityConsulting
𝗧𝗵𝗲𝗿𝗲'𝘀 𝗻𝗼 𝗼𝗻𝗲 𝘁𝗿𝘂𝗲 𝗽𝗮𝘁𝗵 𝗶𝗻𝘁𝗼 𝗰𝘆𝗯𝗲𝗿𝘀𝗲𝗰𝘂𝗿𝗶𝘁𝘆 (𝗵𝗲𝗿𝗲 𝗮𝗿𝗲 𝗮 𝗳𝗲𝘄 𝗮𝗻𝘆𝘄𝗮𝘆)
When someone asks me how to get into cybersecurity, I usually ask what they want their workday to look like. Investigating an alert? Building and securing systems? Testing them? Helping an organization decide which risks it can live with? You don't need a permanent answer. You need a direction you can try, and permission to change it when you learn more.
Take what's useful here and ignore the rest. There's more than one way into this field, and I'd be suspicious of anyone selling you the one true path.
𝗪𝗵𝗮𝘁 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗱𝗼 𝘁𝗼𝗱𝗮𝘆
Before I start waxing poetic, here's some actual advice. I wanted you to see the immediately useful stuff before you fall asleep when the old man starts rambling.
● If you're in school, finishing is job one. Don't lose sight of that. Everything else will try to take time away from this goal, and it's the one that will serve you unaided through your career (degrees don't call for CPEs, yet).
● Personal projects. Pick something that interests you and build a project around it. Document what you did. Post it (GitHub or a personal blog works) so others can see it. Then do it again. What that looks like depends on where you're headed.
● If you're interested in identity, build out an Entra lab, secure it, build automation around creating users securely, etc.
● If you're interested in GRC, pick a framework like the CIS Controls or NIST CSF 2.0 and assess something against it. A made-up company is ideal, because you can give it the messy problems and successes real companies have. Write it up the way you'd hand it to a client, with findings, risk ratings, and recommendations someone could act on. Get it to the point you'd want others to see it, then publish it.
● On the offensive side, hacking labs are everywhere. TryHackMe and Hack The Box are the best known, and both have free tiers and student pricing (for Hack The Box, that's through HTB Academy). Do the lab, but document your process. Everyone does walkthroughs, and those have their place. Be different. Write it up as a pen test report, as if a customer paid for a narrow engagement and this is what you handed them at the end. Check the platform's rules before you publish. Hack The Box, for example, has documented writeup limits.
● On the defensive side, TryHackMe has blue team content too, and LetsDefend (owned by Hack The Box) is built around SOC analyst work. Same deal as above. Document what you did and publish it.
● I'm not endorsing those platforms. They just happen to be popular. Use whatever platform you like and have access to.
● If you're not already, start following industry news. It's a habit that pays off once you're working, and it helps now too. You'll know what's hot, and you'll be able to talk intelligently about current topics. See what you can find in the format you like best (video, podcast, RSS feed, email). One of these days, I'll do a series cataloging all the options. There are many.
● Internships. Do them while you're eligible. If you can find something cyber related, great, but anything IT is far better than no internship. A distant third is anything that gets you into a corporate environment, which still beats nothing. A lot of what employers want to see is that you already understand how companies work, so they don't need to train you on that before they even start on the job skills they hired you for.
● Get a job working on computers. Students should check whether their university hires for help desk, PC support, or lab support. If you're not in school, the same kinds of jobs exist everywhere. Anything that shows you've held a job working with PCs looks amazing. I'm convinced working for my university is what got me my first job.
● Every time you get an opening, talk to people in the field. The summer before my freshman year, I chatted with a software developer who was doing some side work at the school where my mother worked. I still remember his advice. I don't totally agree with it, but it's been useful in its own way. These chance encounters can matter more than you'd think.
● Use your connections. This one may be a bit controversial, but life isn't fair. If you know someone who can get you the inside track, use it. That inside track will, at best, get you an interview. After that it's on you, but getting the chance to make your case can be the hardest part. Connections aren't a requirement to break into the field, whatever some people claim, but use any advantage you have.
𝗙𝗶𝗻𝗱 𝗮 𝗽𝗮𝘁𝗵 (𝗲𝘃𝗲𝗻 𝗶𝗳 𝗶𝘁'𝘀 𝘄𝗿𝗼𝗻𝗴)
Figure out early which things you don't enjoy doing and whether they're critical to your path. If they are, take a hard look at the path. Is this a big part of what you'll be doing, or a small piece you should just accept as the un-fun part of the fun job?
You can't learn everything early on. If a topic seems unlikely to matter for the path you want, and you don't enjoy it, put it aside for now. Spend that time on something you can use. You can come back if paid work gives you a reason to.
Don't apply that rule blindly, though. Unless you head toward cryptography, you can probably leave the math behind modern encryption alone. Networking is harder to dodge. Even if it bores you, learn enough to understand where traffic is going and why. Those are just two easy examples, and plenty of topics fall somewhere between them. If you can't tell what can wait, ask someone doing the job before you skip it.
If you find as you go that you're not enjoying the specialty you've picked, consider an early pivot. It's a lot easier to decide you don't like something now than years into a career, when pivoting forces a step backward.
𝗣𝗶𝗰𝗸 𝗮 𝘀𝗶𝗱𝗲 (𝗺𝗼𝘀𝘁𝗹𝘆)
Cyber is a broad field. The simplest way to slice it is red (offense) and blue (defense), with specialties inside each and plenty of overlap between them. That's an oversimplification, but it's a useful one everyone makes.
It helps to know a bit of both. If you understand why a particular class of attack works, you can defend better. If you know how networks are typically defended, you can attack better. Having said that, especially early on, it makes sense to put at least 80% of your effort (a made-up percentage, but probably close enough to reality) toward the direction you think you want to go. It's easy to get lost in the options. Cut out an entire branch of the field and it goes from totally overwhelming to merely overwhelming.
In my experience, there are more jobs on the defensive side than the offensive side, and more companies have defensive teams than dedicated offensive teams.
Red has a lot of subspecialties, although the people I know on that side tend to work across several of them, apart from those in very niche roles. Red roles include pen testing, red team operations (usually a later-career pivot), and various specialties that roll up into those broader groups.
Blue has generalists and specialists, plus a group in between that Gartner calls versatilists. A generalist knows a little about a lot. A specialist goes deep on one thing. A versatilist has the high-level knowledge of a generalist but also goes deep in a few areas and moves between them as the work demands. You'll find many generalists eventually become versatilists by accident. How specialized a given role is varies a lot from shop to shop. Blue roles include SOC analysts, security engineers, security architects, identity specialists, GRC specialists, vulnerability specialists, and security operations roles (which can mean almost anything).
Many areas of defensive security were once handled by systems administrators, and in smaller organizations they still are. I tend to see cyber as a specialty of IT, with everything under it as a subspecialty. That's especially true on the defensive side.
Then there are the overlap positions that don't fit neatly on either side and can pull from both. That includes incident response, digital forensics, malware analysis, and so on.
Management is worth mentioning here, even though almost nobody starts there. In my experience, more senior-level security managers have come from the blue side, much as there are more blue jobs in general. I could probably come up with a theory as to why, but I'll leave it as a personal observation. My current manager came from the red side and is great, so exceptions exist. How to get into management is out of scope, but if that's your goal, keep it in mind as you go so each step moves you along that path. I fell into management and got out when I could, so I'm not an authority here.
𝗧𝗵𝗲 𝗳𝗿𝗼𝗻𝘁 𝗱𝗼𝗼𝗿 𝗶𝘀 𝘂𝘀𝘂𝗮𝗹𝗹𝘆 𝗜𝗧
You've probably seen headlines about a massive shortage of cybersecurity workers. The big number usually traces back to ISC2's Cybersecurity Workforce Study. The 2024 edition (https://www.isc2.org/Insights/2024/09/Employers-Must-Act-Cybersecurity-Workforce-Growth-Stalls-as-Skills-Gaps-Widen) put the gap at 4.8 million people. The 2025 edition (https://www.isc2.org/Insights/2025/12/2025-ISC2-Cybersecurity-Workforce-Study) didn't publish a gap number at all and shifted its focus to skills, with 59% of respondents reporting critical or significant skills needs. My read is that the shortage is real in one specific sense. Companies want more mid-level and senior security people than they can find. That's a different thing from wanting people with no experience, and the space between those two is where a lot of newcomers get stuck.
Truly entry-level security jobs can be hard to find. You'll see postings labeled entry level that ask for three years of experience and a cert or two, and that's not a typo. Security work usually means making judgment calls about systems someone else built, and it's hard to make those calls well if you've never run the systems yourself. This is the "specialty of IT" thing from earlier in action. Most of the security people I know came in through help desk, systems administration, or networking, and that path still works. It can feel slow when your goal is security and your days are spent on something related but different. It's also how you build a solid foundation.
ISC2's 2025 study backs up the IT route. It's still the most common way in, and only 3% of the professionals surveyed entered through an internship or apprenticeship. That's no knock on internships. The people who did come in that way recommend it at a higher rate than any other route, 69%, and I still think they're one of the best things you can do while still in school. Just don't count on an internship as the express lane that bypasses IT. It's also shifting. Among respondents aged 21 to 29, as many came in through routes other than IT or a cybersecurity degree as through IT, 38% each.
AI is squeezing the bottom rung too. A lot of the repetitive tier-one work, like triaging alerts and writing up routine tickets, is exactly what security vendors are trying to automate. My read is that this makes the first job harder to get rather than making it disappear, and I'd rather you hear that from me now than have it surprise you halfway through a job search. Your first job is going to be harder to land than mine was. What sets you apart is the stuff in the list at the top. Real IT experience, projects you can point to, and people who know your name.
𝗬𝗼𝘂𝗿 𝗼𝗹𝗱 𝗰𝗮𝗿𝗲𝗲𝗿 𝗰𝗼𝘂𝗻𝘁𝘀
If you're changing careers, the math is a little different. You're not starting from zero, even if it feels that way. Ten years in finance, healthcare, or logistics means you already know how a business in that industry actually runs, what it gets regulated on, and where the money goes. A lot of security people never pick that up. GRC roles in particular tend to value sector-specific experience. You may still need some IT time to fill in the technical side, but look first for roles where your old career counts as experience instead of starting over at the bottom.
𝗟𝗲𝗮𝗿𝗻 𝘁𝗼 𝘄𝗿𝗶𝘁𝗲 (𝗮𝗻𝗱 𝘁𝗮𝗹𝗸)
This might be the most important section here, and it's the one people skip. It's also what separates "meets expectations" from "exceeds" on a performance review.
Almost everything in security ends with getting someone else to do something. Something they likely know needs doing but have delayed repeatedly. Patch the server. Fund the project. Stop clicking every single link. Accept the risk in writing. You can be technically right about all of it and still get nowhere if you can't explain it to the person who has to act. Being right is the easy part.
Most of your output will be written. Tickets, emails, findings, incident timelines, the pen test report. Somebody will read every one of those without you there to explain what you meant. Write for that person. Put the conclusion first, say what you need them to do, and cut anything they don't need in order to decide. A finding that makes a sysadmin dig through three paragraphs to learn which server and which patch is a finding that sits in a queue.
Then there's translating risk for people who don't care about the technology, which is most of the people who sign off on things. A CFO doesn't need to know, or care, how the exploit works. They need to know what it could cost, how likely it is, and what fixing it costs. That's the same math they already do for insurance. Frame it that way and you'll get a lot further than you will with a CVSS score.
AI can help with editing. Don't let it be your ghostwriter, and don't accept all of its suggestions blindly either. I lean on AI as an editor, and the value for me has come from reading the feedback and the reasons behind it rather than just accepting the changes. I think my writing has improved more in the last few months than in the few years before that. I've also trained my editor on the quirks that are part of how I write, so it stops trying to fix them. Obviously, only use AI where allowed.
There's no book or trick I can point you to. My style has changed a lot over the years, and I'm still not as good a writer as I'd like. It comes down to practice, and the good news is that you can practice this now. Every project write-up you publish is practice. So is explaining something technical to a friend who isn't in IT and watching for the moment their eyes glaze over. If you get a chance to present, even a short talk at a club meeting or a local conference, take it. It may be uncomfortable the first few times. It gets better. It can even be fun if you let it.
𝗗𝗼𝗻'𝘁 𝗱𝗼 𝗶𝘁 𝗷𝘂𝘀𝘁 𝗳𝗼𝗿 𝘁𝗵𝗲 𝗺𝗼𝗻𝗲𝘆
Cyber (and IT in general) is a field that pays well compared to many other professions with similar or greater education requirements. That's obvious looking at BLS (or pick your favorite) salary surveys and comparing to other roles.
The downside is that people know this and get into cyber with little real interest beyond the salary. That's a path to misery. Stop. Think. Do you really want to do something that demands this level of dedication for decades if you don't have some passion for it? I've been told my take on this is wrong, and that curiosity, tolerance for frustration, and general interest matter more than real passion. That's probably fair pushback. I still lead with the pessimistic version because I've worked with people who would have been happier doing something else, and I don't want to paint an overly rosy picture. Take my harshness as care for your future happiness. If you think you have what it takes, don't let me discourage you.
I always want to cut the "tough love" speech, but I think it's important, so it's here. Get past that, and it's a rewarding career path.
𝗠𝗼𝘃𝗶𝗻𝗴 𝘂𝗽
Everyone wants to advance quickly, especially early on. Advancement can mean title, money, power, whatever it means to you. Don't stall out before you get where you want to be, but don't rush it or reach for shortcuts either. The shortcuts I mean are things like cramming certs you can't back up, using braindumps to pass exams, or hopping jobs for a title you can't do yet. They catch up with you, usually in an interview or during your first bad week in the new role.
Early on, what moves you up is mostly boring. Do the job you have well. Own problems all the way to the fix instead of passing them along, and write down what you learned so the next person doesn't have to rediscover it. Be the person people trust to actually close the ticket. None of that is glamorous, but it's what gets your name mentioned when a better role opens up.
Make sure people know what you want. Your manager can't help you get somewhere they don't know you're trying to go. Even worse, when they see promise, they may try to help you get where they think you should want to go. Tell them, and ask what it would take. Then learn a bit of the job one step up, or one step over, so the move is a short hop instead of a leap.
Be realistic about how raises work, too. In my experience the biggest jumps in pay and title come from changing jobs, although I've had both without changing companies. The expediency of changing jobs for advancement doesn't mean you should hop constantly. A resume full of six-to-eighteen-month stints raises its own questions. But if you've outgrown a role and there's nowhere to go internally, moving on is normal and nobody sensible will hold the occasional fast pivot against you. Unless you chose a position badly, you will not outgrow it in months.
I'd like to think the days of hopping from job to job in rapid succession for better pay and title are on their way out, but so far the numbers mostly follow the job market. Atlanta Fed wage data, as SHRM reported it (https://www.shrm.org/executive-network/insights/job-hopping-premium-shrinks), had wage growth for job switchers at 4.8% in early 2025 against 4.6% for people who stayed put, down from 7.7% against 5.5% in 2023. The Atlanta Fed's tracker (https://www.atlantafed.org/research-and-data/data/wage-growth-tracker) shows that gap opening back up in 2026. Even when the bump is real, it's a win now that can cost you later. Every move resets you to learning a new environment, and the holes that leaves show up down the road, usually when someone expects the depth your title implies. You'll occasionally hear recruiters and hiring managers put it as a question. Does this person have ten years of experience, or one year of experience ten times? That's not a question you want asked about you when you're going after the top technical roles or management.
The days of working forty years and getting a gold watch were gone before I entered the job market, but I think changing jobs too often leads to short-term thinking and missing the long-term results of your actions. In security that cost is concrete. If you never stay much past a year, you never live with the architecture you designed, the exceptions you approved, or the audit that finally finds the problem you left behind. We went too far in the employee free-agent direction. Time will tell whether it swings back. I can hope it does.
𝗬𝗼𝘂 𝗰𝗮𝗻 𝗳𝗮𝗸𝗲 𝗶𝘁 (𝗳𝗼𝗿 𝗮 𝘄𝗵𝗶𝗹𝗲)
Learning has never been easier, and landing that first job has never felt harder, so the pull to speed-run certs, braindump your way through exams, and hop jobs to keep up makes sense. I understand the desire. Can you fake it? Yes. I've known a couple of people who took jobs they knew they weren't qualified for, using methods I'd call flatly unethical, then spent every evening and weekend trying to keep up. They worked 80 to 100 hours a week, reported 40, and probably produced what someone competent could have done in 30. It worked for them, for certain definitions of worked.
I've also watched people get promoted to the point of incompetence (there's a name for that, the Peter principle) and then not be able to keep up. That usually ends badly, because even stepping back to the last level you could handle raises questions. Picture explaining why your last title, the one you lost in a "restructuring," was Director, and why you're now applying for senior engineer jobs after twelve months of no callbacks for management roles. Most hiring managers won't ask. They'll just pass on the resume. That's not a made-up scenario. A former colleague of mine went through exactly that. He eventually got another job through a referral, but he was out of IT for a bit less than two years. That's close to the worst case. Technically it isn't the worst, since he didn't kill anyone or cause anything big enough to get sued, but it's close.
I haven't seen many people I'd call top 10% performers take the fake-it route. I've always treated this as a long game. I've made missteps, but never one I couldn't recover from, and faking it leaves a lot less room for error. You're going to struggle either way. For me, the stress of faking it on top of everything else was never worth it.
𝗬𝗼𝘂'𝗹𝗹 𝗻𝗲𝘃𝗲𝗿 𝘀𝘁𝗼𝗽 𝘀𝘁𝘂𝗱𝘆𝗶𝗻𝗴
I hope you enjoy learning, because in this field you'll need to learn something every day until you retire.
I mean, technically that's not true. Plenty of people stagnate and quit learning, slowly becoming less and less valuable and harder to employ, but that's not going to happen to you.
Seriously, I log well over a hundred hours of formal training a year. That's a mix of work hours and my own time. Outside of formal training, multiple times a week I'm working on technologies or products I know well and still learning new aspects or changes. It never stops.
I see this as one of the big selling points of the field, but go in expecting it. Remember that comment about passion? There's a reason I think it's required, even if that isn't a universal belief.
𝗦𝗰𝗿𝗶𝗽𝘁, 𝗯𝘂𝘁 𝘆𝗼𝘂 𝗱𝗼𝗻'𝘁 𝗵𝗮𝘃𝗲 𝘁𝗼 𝗯𝗲 𝗮 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿
I never enjoyed programming classes in college, but scripting is one of my favorite parts of the job today.
You don't need to code to excel in cyber, but strong scripting helps. You don't necessarily need it on day one, but at some point you'll likely need to pick it up. This is one place where AI can really speed up getting productive, but that comes with some risk (more on that below).
If you're starting from scratch, learn Python. I'm a PowerShell guy myself, because most of my work lives in Microsoft environments, and if you end up in a Windows shop you'll want PowerShell too. But Python is what I recommend first. It runs everywhere, a lot of security tooling is written in it, and when you need to hit an API or chew through a pile of log data, there's usually a Python library that already does the hard part. On the Linux side, learn enough Bash to get around, or more if it becomes a significant part of your day-to-day.
Don't stress too much about which language comes first. The concepts carry over. Variables, loops, working with files, calling an API, parsing JSON. Once you've learned them in one language, the second goes much faster. The best first project is something you already do by hand that annoys you. Automate that.
What you don't need to do is become a "real" developer. There are some specialties where a strong development background helps. DevSecOps and code audit are examples. Outside of those, true development work isn't the norm.
There's a weird place where scripting turns into pseudo-development. I've written scripts that ran thousands of lines and did the same work as commercial packages. I've had to learn "enough" programming theory to get by, but I still don't consider myself a programmer, nor do I want to play one on TV. Some people would argue that's wandering into development. I don't know.
𝗨𝘀𝗲 𝗔𝗜, 𝗯𝘂𝘁 𝗱𝗼𝗻'𝘁 𝘀𝗸𝗶𝗽 𝘁𝗵𝗲 𝘀𝘁𝗿𝘂𝗴𝗴𝗹𝗲
AI, or more precisely LLMs, will be part of your work life. It makes research easier. DO NOT rely on it blindly at work, and I'd suggest limiting how much you use it while you're learning. Most people I know learn by struggling, and AI papers over the struggle.
My own AI use is something I wrestle with. I worry that to some extent it deskills me, even while it helps me turn out better work, and that's with a decades-long base to build on. I have real concerns for someone still learning who leans on AI too much. Having said that, once you're in the workplace, you'll likely need to use it to be competitive.
One thing that cuts in your favor is that experience counts for less here than almost anywhere else. My years in the field give me some advantage, maybe, but they also come with some calcified ideas. Truly new technology puts everyone on a more level playing field. Compare that to identity management, which has changed so much since I started that younger me wouldn't recognize today's minimum standards, but it changed slowly enough that experience kept its value. I don't see a generational divide in who uses AI well, either. I work with people younger and older than me who are more and less skilled with it.
On the practical side, learn to prompt well. Play with your tool of choice, see where it goes wrong, and figure out what makes those mistakes less likely next time. If you want to build out automated AI workflows, that's great, but you'll be going well beyond where most people in corporate America are today. Even the LLM adopters.
Whatever you use AI for, use it ethically. In short, check its output, follow your employer's rules (some push AI use while others still discourage it), and keep company-sensitive information out of tools that haven't been approved for that use. Don't pass AI output off as your own work. That doesn't mean disclosing every time AI helps you edit a document. I don't. But I'm working on a personal coding project right now where almost all of the code will be machine-generated, and it will say so, because that won't be obvious to most people reading it. My feelings on what counts as ethical AI use keep shifting, so expect yours to as well, but define a minimum standard and think hard any time that shifts.
What about AI certs? I'd say not yet. Nothing has shaken out as the one employers ask for, and the technology changes too fast for a cert to keep up. Projects might be worth it. AI security means different things to different people, from restricting what employees paste into chatbots to protecting custom deployments, with a lot of gray in between. Some of that is settling into standard practice and some keeps changing. If you want to go deep into AI security, there will be jobs. I just can't predict yet what they'll look like.
𝗖𝗲𝗿𝘁𝘀 𝗺𝗮𝘁𝘁𝗲𝗿 𝗺𝗼𝘀𝘁 𝗲𝗮𝗿𝗹𝘆
Certs are the subject everyone has an opinion on. I have a ton of them and mixed feelings about them, but if they're useful anywhere, it's probably early in your career. In general, certs do a few things.
● From a learning standpoint, they give you a path to follow, so you cover all the bases instead of picking and choosing.
● They check HR boxes in some cases. In the era of Applicant Tracking Systems (ATS), that can decide whether a human ever sees your resume.
● They demonstrate some minimum level of knowledge.
● They show you can study and learn a topic or product.
The biggest thing certs have going for them is that they're standardized. Picture a recruiter reading 50 cyber resumes in the morning and 50 accounting resumes in the afternoon. They need shortcuts, and certs are that shortcut. They don't spend much time per resume either. TheLadders' 2018 eye-tracking study (https://www.theladders.com/static/images/basicSite/pdfs/TheLadders-EyeTracking-StudyC2.pdf) put the average first pass at 7.4 seconds. You'll hear recruiters and hiring managers quote 30 to 90 seconds for a resume that survives that first cut. And that's after the ATS has already had its turn.
So if you have a free afternoon, should you study for a cert or work on a project? It's not either-or, and plenty of people will disagree with me here. Certs give you more even coverage. Projects mirror the real world, so they go deeper, but they leave gaps where things just didn't come up. The struggle of working through the unknowns in a project tends to stick better. The bigger difference is how fast each one plateaus. One to three certs early in your career puts you ahead of most of the competition. A dozen doesn't put you much further ahead. Projects keep paying off a lot longer.
As for which certs, that's harder to answer without specifics you may not even know yet, but here are a few guidelines I find useful.
● For a general defensive security cert, I still think it's hard to beat the Security+. It's well recognized in the industry and the coverage is reasonably good. Your local library likely has training materials, and there are plenty of inexpensive or free online classes. If it weren't for the time and exam costs, I'd suggest the classic A+ -> Net+ -> Sec+ route, but I have mixed feelings about whether it's worth the investment. The three do build on each other, so it may make sense to at least review the Net+ material first. CompTIA's exams have gotten expensive, but if you're a student, you can get a significant discount.
● ISC2 is the other big name in vendor-neutral certs. Its entry-level cert is Certified in Cybersecurity (CC), and I'm a bit skeptical of it myself. It just doesn't show up in job postings the way Security+ does. The one you'll hear about constantly is the CISSP, which I hold. It's a great cert, but it isn't a starter cert. It requires four to five years of work experience across at least two of its eight domains, depending on your education and other certs. You can pass the exam before you have the experience and become an Associate of ISC2, which gives you six years to gain the experience to upgrade. That's a legitimate path, but treat it as a long-term goal.
● If you want something vendor-specific, think about the tools and technologies you expect to work with and see what's offered. Microsoft, AWS, and Google all offer free or very low-cost training for some of their products. You'll have to pay for the exams, but check for student discounts.
● On the offensive side, there are fewer options. PenTest+ is probably the most recognized "entry level" offensive cert, but far less so than Security+ is on the defensive side. You'll see CEH listed as required or preferred on a lot of job postings, so it can get you past HR. Few practitioners I know take it seriously, myself included. The OSCP is the offensive cert that people respect almost universally as meaning you have some level of real skill. It's challenging for a beginner, but in my opinion, cyber, and especially offensive cyber, isn't really a beginner field.
𝗣𝗼𝘀𝘁𝘀 𝗶𝗻 𝘁𝗵𝗶𝘀 𝘀𝗲𝗿𝗶𝗲𝘀
I'm pulling pieces of this out as standalone LinkedIn posts, usually with a story that didn't fit here. New ones get added to this list as they go up.
1. Find a path (https://www.linkedin.com/feed/update/urn:li:activity:7515339251337715712/) - Why my resume has a step backward in it, and why you don't need a permanent answer to get started
2. Pick a side (https://www.linkedin.com/feed/update/urn:li:activity:7517875960755437568/) - A virus author who dialed into my BBS, and why it pays to pick red or blue early and still look over the fence
3. The front door is usually IT (https://www.linkedin.com/feed/update/urn:li:activity:7520412681133101056/) - The cleanup that wiped a professor's work, and why most security people start in IT
𝗣𝗹𝗮𝗰𝗲𝘀 𝘄𝗼𝗿𝘁𝗵 𝘆𝗼𝘂𝗿 𝘁𝗶𝗺𝗲
LinkedIn - I post one or two items a week. Topics vary, but a lot of them cover the same ground as this, so follow or connect if it's useful.
Simply Cyber - If you haven't dug through everything they offer, do it. Dr. Gerald Auger and friends have created a mountain of material, much of it free for the taking. https://simplycyber.io/ and https://www.youtube.com/@SimplyCyber
Antisyphon Training - The training arm of Black Hills Information Security. They offer plenty of low-cost and free training, and some of their courses use a pay-what-you-can model, which is hard to beat on a tight budget. https://www.antisyphontraining.com/
BSides or other local conferences - Go. Meet people. Learn things. Volunteer.
Local chapters - ISSA, OWASP, and ISC2 all have local chapters in a lot of cities, and most of them welcome newcomers and students. It's the same idea as local conferences, and they meet more often than once a year. This is also a good place to meet hiring managers. Don't go in waving a resume, but get to know people so you have the connections when the time is right.
Student competitions - If your school has a team for the Collegiate Cyber Defense Competition (CCDC) or the National Cyber League (NCL), join it. If it doesn't, NCL also runs an individual game you can enter on your own. CCDC in particular is about as close to defending a real network under pressure as you'll get in school.
𝗙𝗼𝗿 𝘁𝗵𝗼𝘀𝗲 𝘄𝗵𝗼 𝘀𝗰𝗿𝗼𝗹𝗹𝗲𝗱 𝘀𝘁𝗿𝗮𝗶𝗴𝗵𝘁 𝘁𝗼 𝘁𝗵𝗲 𝗯𝗼𝘁𝘁𝗼𝗺
That's a lot, and none of it has to happen this week. Pick one thing from the list at the top and start there. If you're still not sure which direction you're headed, that's fine too. Most of us figured it out by trying the wrong thing first.
[INFO] Old man has finished rambling. Resuming normal operations.