Daniel O.

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

It's not always a conspiracy.

It's the weekend, so I'll keep this short.

In one week, Microsoft 365 went down, the FAA called a nationwide ground stop, Chase online banking fell over and dragged outage reports for other big banks along with it, and NSANet went wobbly. The comment sections had it figured out. Coordinated attack, obviously.

The explanations so far are a software bug at Microsoft, legacy equipment at the FAA, a software bug at Chase, and scheduled maintenance at the NSA. Four boring causes in four different places.

If you've done this long enough, you've caused one of these yourself.

Not everything is related. Occam's razor doesn't say coincidence always wins. It says the explanation needing the fewest extra assumptions wins. Four large, complicated systems each having a bad day takes far fewer assumptions than one adversary quietly owning all of them and picking the same week to show it.

If real evidence turns up, I'll change my mind. Until then, coincidence is the cheaper bet.

This is something I should repost every 3-6 months, because it's evergreen advice we all forget from time to time. I'll just have to pick new examples.

Have a great weekend.

View post

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?

View post

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.

View post

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

View post

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

View post

View Daniel O.'s profile on Cyberr