I’m writing this for my son and others of his age that are exploring interesting and exciting careers as part of their next chapter in college. While my son seems interested in finance – I have advised to try and at least so a minor in cybersecurity. Here, I want to lay out what EXACTLY this is.
I got started on my journey in this in 2003. I had been hired by a local manufacturing company to do IT support. I was out of work forever due to the dotcom crash, and my job that I had loved at Vanguard being an IT metrics manager the last 3 years I loved – and suited me very well for IT management years later. But I had to more or less take 2 steps back into the mail room in 2003 or so, and it was an ego check. But my bills were piling up, jobs were scarce, and I took what I could get. Four days into the job, someone calls me into the server room. Some guy sent up from our parent company in North Carolina. He’s showing me how the exchange server was lit up with vulnerabilities. He’s like, “this will be in my report”. I’m like, “aren’t you going to fix them”? He said “no – my job is to find the problem, your is to fix them”. Me and another guy replaced the two previous IT support people who gave me all of 3 hours of training before they left. My boss was in Ontario.
I went to the “network security” guy as he was introduced to me, and I told him about the issue. He’s like, “well, I guess you have a big job ahead”. Mind you, I had never done anything with IT security up until this point. That was always the scary ninja hacker guys, right? Well, it was my rude awakening to the reality that everyone in IT plays a part in cyber security, and the old term “network security” started to be retired around the year 2010, when I started my MS in cyber security.
///Background
To be fair here – I started learning about patching and group policy from tinkering in 2004-2005. But there was a LOT to learn. In 2006 or so, I figured out how to grab the SMS items from above, customize, and deploy internally. That got me a job as an enterprise admin over 125,000 machines – but that company was not a great fit. I was silently building installs for things like MS office that would be deployed to tens of thousands of machines. I was making some minor mistakes here and there, but learning 10x each day. Then, I was laid off with 25,000 people one day with the global financial crisis. Then a stint with Lockheed. Then all of us laid off one day in 2009. Finally – I found a home at the DoD under US Cybercom and took my SCCM experience over 125,000 machines and dozens of servers supporting 41 countries in 8 languages to a single military installation with 14,000 people and a single server. I eventually moved on from there as an enterprise admin over 42,000 machines and securing them with SCCM and group policy, while running a cyber team out of columbus. The last 7 years I had with US Cybercom was running the installation’s contract cyber (the job I worked in 2009-2013) teams of 75-125 people – sometimes also running the contract for a second installation. These contracts are full blown IT support covering business operations, desktop/server engineering, networking, and cyber security. I didn’t need to be an expert in everything – but I needed to have smart and capable managers under me, so I could provide direction and allow them to execute. My metrics background helped me monitor and track everything!
///End background
So what IS it?
Cyber security is essentially a holistic program your business is built on – which builds security into every aspect of what you do. While in the old days, you may show up at a place, and they would be like “we have McAfee HIPS!!” and that was the end of the discussion. Today, cyber security is thought of in frameworks to secure all aspects of your digital side of the business. I am a big fan of the NIST Cybersecurity Framework 2.0 because it can be the Rosetta stone for a lot of different frameworks.

The objective is to ensure all 107 controls for the framework are satisfied. By doing this, you de-risk your business from cyber attack. While we all think of the ninjas trying to get past our barbed wire network defense, a stat I once read said 47% of all attacks are from within. So – it is important to be able to roll out this framework to the entire organization.
For example, everything is built on governance. What company are you protecting? What are the boundary scopes for the company? Who works for the company? What policies must they follow? What is their password policy? Who has authority to implement items?
Here is the link to the NIST CSF 2.0 so you can see what the controls are like.
I am currently a CIO, so there’s a scope to this similar to my last position – where I would have a business branch, a cyber branch, an infrastructure branch, and a desktop/server branch. Maybe in some companies, a development branch. I do not get into the inner workings of a company I work for when I’m working for them for obvious reasons. But I simply wanted to point out a concept here. Separation of duties.
For example, a desktop engineer can be told to set certain conditions to harden machines for group policy. But the cyber branch is there to verify this was done. They may run a SCAP tool on some machines as a sampling to determine if the group policy is widely pushed, as said. A networking guy may be instructed to deny all and allow by exception for firewalls. However, if change is to be made, he must put in a change with change control and the firewall permit must be registered with cyber. At any time, cyber is permitted to audit – to ensure that the permits align with how configuration is. If drift is detected, this triggers an incident. Maybe a change was done in an emergency, but no one registered the change and updated the firewall permits. Cyber isn’t in the systems making changes – and in many cases, they do not even have elevated credentials and are meant to audit.
Separation of duties means that someone that has authority to make changes – can make changes, but must coordinate with others, and have their work be audited by others.
This is also where the “least privilege doctrine” aspects come in to play. You want to give people the least amount of ability to do their jobs, and no more. Why should Steve in accounting be looking all over the marketing divisions quarterly reports? He could potentially use this information for ill gains at the stock market from insider trading. You don’t want to give a new admin “god rights” as one misstep, and he could take down the company. In both cases, giving ONLY the required levels of access reduces risk to the company’s operations. Separation of duties also prevents an engineer from saying “trust me bro” when he says “we good” with security. “I have us using the lastest DroneStrike1 software!” Dude. Good on you. Where is the documentation for the other 106 controls? Send us evidence you did this. Once cyber collects the evidence, they put it into a tool like Archer, and the CISO or the top cyber person can then look at the risk from the entire organization.
//Side note.
I’m sorry. You get out of college at 22, it will take you years to get your sea legs. All of this starts by understand MIS. How business foundations are great with this because then you understand how inventory and depreciation works. Finance is great to understand CAPEX and ROI. Finance is also good because you learn about risk.
//End side note
So what is the BIG picture? The CIA triad.

When I worked for the DoD, we used RMF. RMF had over 1200 controls (as opposed to most others about 100). Tons of paperwork. Lots of processes defined. For example, you needed to show that your ticketing system would track every piece of software installed – called an artifact. This demonstrated a process – a person requests it, someone approves it (with fiscal responsibility for paying for it), IT then installs it, and then bills back the department. You needed to demonstrate that business process, then show the ticket where Susie asked for Project, how it was approved, then were able to follow the bill back. This also prevents fraud within the company. And, ensures that any software is installed by an IT person and not the user themselves. This shows control over your environment. All pieces of SW needed to be reviewed with a 300 step process to ensure China wasn’t using a SW company to install backdoors on us. This is why we never allowed any kind of freeware in the DoD. Almost all of it has some sort of thing I am suspicious about.
Confidentiality – typically, this might involve encryption. Least privilege. Auditing of rights.
Integrity. Is what was sent what arrived, or was there a man in the middle attack? Is the software hash of where it originated the same as destination, or was the executable replaced mid transit?
Availability – can we ensure we don’t get hit by a DDoS attack? Can we ensure server uptime and redundancy? Do ALL aspects of the company have redundancy?
Guns, Gates, and Guards
I also worked in physical security in college, and have a security minor. Think of cyber security in these old school terms. You approach a military installation, and you see gates. This is your single points of ingress or egress. Guards are there with guns. CCTV is watching you come in and leave. But once you get through the perimeter, the place may have 50 large buildings that are nondescript. Your job is to go around and check that all of the doors are locked. All of the windows are closed. Then, even if someone were to get inside of the building – you need to make sure all of the cabinets are locked, doors are locked, no PII is sitting on desks, and safes are locked.
The CCTV in that is like the logs. Everything has logs, and if you understand how logs work, you are ahead of 98% of your competition. I used to write scripts to go through all of my hundreds of logs, so when I sat down at 7AM, I had an automated report for me telling me where I need to look to do maintenance.
Three types of cyber jobs
Today, there are three types of jobs in cyber we dealt with in the DoD.
Technical – doing Nessus scans, operating the antivirus, doing PKI entry level work putting certs on smart cards (Identity).
Investigative – this is your white hat – pen testing, cyber investigations, cyber response, recovery. Digital forensics
Policy – this is your framework people who also dictate cyber policy to the organization. This is your risk management people. These are your IT auditors. These are your former accountants that want to follow the money trail for an order of 400 PCs that are supposed to be in a warehouse. They collect all of the cyber artifacts from the divisions that SET the cyber tools so they can work with the regulating bodies.
Popular certs?
Certs are important in the DoD, as it’s like cub scouts there and the more cub scout badges you get, the more they think you are qualified. It doesn’t work that way in IT. I have seen many people pass certs that are complete dopes, and others that were extremely smart to work with, but could not pass a cert test.
I have a CISSP – which covers the 10 domains of cyber security and is the gold standard cert to run an IT security organization. The Security+ is a more entry level one, and I once saw a desktop tech with 15 years experience take 5 tries to pass it. I bought a book in November 2009, read it in three weeks, and passed the test. But, I also had 14 years of experience with that working in securing items.
The CAP was the gold standard for the policy people. They call a lot of that stuff GRC these days. It’s very dry and good for the accounting folks.
The CEH was what was used for the white hats. This means that the “good guys” use the same tools the bad guys (black hats) would use and find problems first, so the other groups can fix it, then they run the tools again to ensure things are resolved. Notice the separation of duties here?
Risk Management
I almost forgot this – I will keep this brief, as I write about risk a lot here.
An organization needs to identify risks. Frameworks here do that for you. You then determine the likeness of an event, and the impact of it. These then dictate the priorities you set.
Most orgs are never 100% perfect. Anyone who has ever done vulnerability patching knows this. It is a constant ebb and flow where every day you try and get better just as new threats come out and evolve.
College?
Most people I have worked with in IT for 32 years did not have a college degree and made really good money. A degree is useful to be a manager or even help with higher level engineering assignments. Someone can make an incredible career doing nothing but entry level cyber work for 30 years. My MS helped me get more advanced level jobs. My MBA helped me get management jobs.
Overall, in 29 years of work outside of college, not one manager ever asked me about my GPA. It was all about the experience. It was all about networking. I pledged a fraternity in college, and my first interview out I was interviewed by a guy named Mitch – who pledged my fraternity years earlier at my college. We knew a few of the same people. That interview was about “how does he work with people. How can he take instruction. What experience does he already have. What’s his upside”? When I interviewed people, I interviewed them with their next job in mind. All of them. Every single one of them.
I’m not saying college isn’t important. I’m saying that in my case, I had 3 years of experience at my first “real” full time job interview, and I damn near worked full time at Harley Davidson my senior year WHILE taking 42 credits. I was not hired because I had a 4.0 or 2.4 – it was “how can he work in a team, and can he do the job”?
So all of you that are in college, or going to college, find a job. ANYTHING for 5-20 hours a week. Preferably, in your field of interest. You have NO IDEA what the entry level job market is like. Everyone sounds the exact same, and I don’t care you got an A in a database class 2 years ago. If you love databases, I can keep you in mind for a junior DBA I have that may want to leave inside of a year. But don’t think your 3.8 GPA is going to do anything for me. Why? Have you ever punched a clock? Understood work under stress? Understood work dynamics? Had a boss? Worked late? Went above and beyond? Suffered to get the job done even being deathly sick? Work during college establishes – RESPONSIBILITY and gets you the primer for work stuff out of the way.
Leave a Reply