Every Cybersecurity Job Explained!

Career Exploration
27 followers
6 Video Views·Aug 27, 2026
Explore an array of cybersecurity courses in the TCM Security Academy! We offer beginner-friendly, intermediate-level, blue team, red team, fundamentals, and more.
Alex has been on a roll lately; first the PWPE, and now today’s video! He’s breaking down (almost) every cybersecurity career path out there.
Whether you’re eyeing Red Team roles like Penetration Tester, Red Team Operator, or Vulnerability Assessor, or leaning toward Blue Team positions like Incident Responder, Forensics Analyst, or SOC Analyst, this video has you covered.
If you’ve been wondering which direction to take in your cyber journey, don’t miss this deep dive.
AI Generated·May contain errors
Today, I thought I'd go through every role in cybersecurity and talk about what a day in the
life might look like and give you some of my thoughts on why you would and wouldn't want to
do that job. A quick caveat here is that job titles can vary wildly from organization to
organization. So, for example, I know pen testers that are labeled as analysts and some CISOs
simply are the CFO of a company whilst others are helping out building new machines on the help
desk. And I'm not exaggerating here. I've seen that in a reasonably sized organization that had
more than 5000 employees. So I will try and strike a logical balance. But remember that generally no
two roles of the same title are exactly the same and use the timestamps to skip to ones that might
be of interest to you. If you enjoy the video, then don't forget to like and subscribe. And if
you have some story or insights or advice for a role that you're currently in, then feel free to
share down in the comments below. And with that, let's dive in. So we're going to start out on the
red team side. And the most prevalent role here is, of course, a penetration tester or pen tester. So
for me, I started network pen testing internally. So for the organization that I was working for at
the time, and I was doing post change testing. So after some new infrastructure had been deployed
or updated, and also I was verifying and retesting findings from pen tests that were performed by
third parties. So this was, of course, part of the organization's compliance activities.
After that, I did some pen testing on and off and a little bit of red teaming too. But if you've
watched any of my videos, then you'll know that I settled more into AppSec and web app pen testing
during my career. So typically, we're testing against a network and Active Directory, of course,
plays a big role here. But understanding networks and file shares and pivoting and scanning at scale
are all really important skills. And I think something that catches out a lot of junior
testers is that critical findings in a weird context. And if you've ever scanned a network
with Nessus, you'll know what I mean here, especially if you're doing authenticated scans,
it'll be like edge on the domain controller is out of date. And if you browse to a specific site,
hosting a specific exploits, then the attacker could get remote code execution. But who is
browsing the internet from the domain controller for one, and if it's an attacker, then they're
already on the domain controller. So is this an issue at all? In this context, clearly not a
critical issue. But I have seen things like this on reports and tagged with a critical rating from
newer testers from time to time. I'd also say that scripting is a really important skill for network
pen testing. You'll often have to automate things or write a script that triggers things in a chain
or sequence. So that's something to keep in mind. Now, typically over a week, you'll be attending
scoping meetings and calls with your clients and helping them set up a Dropbox or give you some
kind of initial access, maybe doing OSINT and looking at their external infrastructure, scanning
the internal network, attacking Active Directory, looking for credentials flying over the network,
maybe from some software deployment tool, and ultimately trying to get the domain controller
or customer data or into the card data environment. And you'll be able to write reports on your
findings and do debriefs and support remediation and maybe follow up testing too. So generally
speaking, it's quite a well-rounded job in terms of technical work and client interactions. But of
course, the setup or weighting of these can change depending from organization to organization. Now,
if you enjoy doing pen testing and you're happy with shorter project life cycles, then it's a
good job. But maybe if you get bored easily or you don't like working within the constraints,
which I've seen pen tests where you're not allowed to run exploits without written permission,
and getting that permission was a long process following a risk assessment that you had to
conduct, if you're not good with tight deadlines, then maybe pen testing isn't an optimal choice
for you. Next, we'll move on to web app pen testing. So I think increasingly these days,
networks and web apps are becoming a separate specialty, which I think is the right way to do
things. But I've talked about this before, so we won't dive into that. The general structure of a
web app pen test is a little bit similar though to network pen testing, even if the technical skills
are different. You'll often be interacting with clients, usually before and after the testing,
and of course, spending most of your time understanding how the target works, what the
technology stack is, and of course, going through and systematically testing functionality and
endpoints that you've either been given or have uncovered. For me, once again, I was previously
working with the internal development teams and doing appsec on the products that the organization
built, so this included a lot of code review, threat modeling, supporting the architecture and
design process, and of course, pre-release testing. Now, this is more of a general appsec engineering
approach rather than a pure pen testing one, and usually I had a lot of knowledge of the target
applications that I was testing, so just keep that in mind when I'm giving advice about web app pen
testing, that I've worked a little bit more internally rather than from an external perspective.
But a typical day, you might be in some scoping calls or in a meeting where the development team
or product manager runs you through the targets, and then you'll probably have some documentation
and spend most of your time testing, and unfortunately, you'll only usually have about
four days of testing and one day for reporting, regardless of the size of the application,
and this is one of the downsides of being in a penetration testing role, you're often short
on time. Now, if you like how HTTP and other protocols are pretty flexible rather than a
solid set of rules and enjoy digging deep into quirky functionality, but also fuzzing and checking
for many different issues in different scenarios, then you'll probably enjoy web app pen testing.
For me, I like the balance between following my checklist and then going deeper into parts
of the application that are either unique or behaving weirdly, which is where you can be
more creative. And it's also interesting to explore how different teams implement and solve
different problems and assessing those solutions and helping the team fix things and make good
decisions going forward. On the other hand, if you don't really find web apps interesting or grasp
the different approaches like REST and why they might be used, and maybe making minor changes to
payloads and examining behavior seems boring to you, then web app pen testing might not be for you.
Next, we have the red team operator. So in my career, I've done a small amount of red teaming,
and this is to say that we were doing adversary emulation for a specific APT. And just to clarify,
I've seen a lot of people online say that red teaming is pen testing, but without scope,
and that is complete rubbish. If anything, red teaming is way more specific than penetration
testing, especially when we're talking about using specific attacks for a specific adversary.
And also what we're looking for is what is detected and how the organization responds,
etc. The main difference for me is that we had to go a little slower with our scans to avoid
initial detection and the use of different tools and C2 infrastructure and focusing more on
persistence and making sure that we didn't trip things like EDR solutions. So on a pen test,
we generally don't care about being loud, and we can just try a bunch of different things until
an exploit works. On the red team, we might do some testing locally to see if we can create a
payload that doesn't get blocked and raise an alert, or we might try to disable these products
on endpoints altogether. Generally, I think the skills for red teaming and pen testing are quite
similar. It's just the mindset and the approach is different. And for me, I actually think that
general pen testing is a little bit more fun and satisfying, but red teaming has its place too.
For some red teams, there can be more follow-up interactions with the clients and maybe their blue
team. So rather than just the delivery of a report, so that could be a pro or a con depending
on what you really enjoy doing. I quite like helping clients and in particular, collaborating
with engineers to improve their systems. So for me, this is one of the highlights of the role.
So next I've got the vulnerability assessor, and this is a catch-all title for those roles
that are running vulnerability management programs, but doing the scanning and assessing
the results themselves. So I've put together two vulnerability management programs in place for
two separate organizations before, and I can say that this job is great if you have good people
around you who are invested in security, and terrible if nobody at your organization cares
about security. So you'll often be working with the infrastructure team or the networking team
to make sure that your scanners can actually reach everything that they need to, and also
maybe provisioning accounts so that you can do things like authenticated scanning. The first
downside to this role is the processing of the large amount of output that network scanners put
out. Unfortunately, I'm yet to see a scanning report that has meaningful ratings on findings,
and I get why they don't, because scanners don't understand which parts of your infrastructure are
critical, what's internet facing, what's in the DMZ, where is your CDE, etc etc. All of your assets
are different, and of course carry different levels of risk, and scanners don't understand
that. But the worst part of this role is showing some meaningful results that you've spent a long
time putting together to the infra team, or whoever's job it is to patch and maintain the
network, and they just don't care, and they don't do anything. And then your job becomes defending
the results, and trying to convince them to fix things, whilst your spreadsheet or tool has an
ever-growing number of critical issues, and you've got senior management saying that this isn't
acceptable, and there should be zero criticals by the end of the month, and the larger the organization
the more teams you need to interact with, and the harder this job becomes. It's not all bad though,
if you can get teams on board and working with you, and some dedicated resources to resolving
issues over time, and you have a process for scanning before deployment of new infrastructure,
or maybe you're fixing things in the base image that they're using, then the job can have a real
impact on the overall security posture of an organization. So I think that this role is way
harder than people give it credit for, but I think it can be rewarding, and honestly over time I think
that you'll have a far bigger impact on the actual security posture of an organization than any pen
test ever will, if you can make it work, and if you can get buy-in from the right teams.
Elevate your cybersecurity expertise with TCM security certifications. Our certifications offer
in-depth practical training in penetration testing and ethical hacking. With real-world exam scenarios
and expert guidance, you're not just gaining a certificate, you're gaining a skill set that's in
high demand. Visit certifications.tcm-sec.com and take your first step towards a distinguished
cybersecurity career. Moving into the blue team, we have the SOC analysts. So I've never actually
worked in a dedicated SOC, but I have worked as part of a small security team, and we were
responsible for detecting and responding to threats, and we actually had some good tools
available to us. But in a typical day, what we'll be doing is triaging alerts, escalating threats
that we think are legit, and writing shift or handover reports. Now, some SOC analysts will be
more involved in the engineering side as well, so maybe you're deploying sensors or writing rules to
pass logs into the central seam, or creating testing and some orchestration scripts. I'd say
if you're a detail-oriented person and enjoy understanding the behavior of many different
protocols and technologies and investigating things, then this is a great job. But if you
don't like shift work, and you find it hard to stay focused for long periods of time, and you
don't work well under pressure, then maybe there are other roles that might be more suitable. But
there is a lot of scope to branch out into different areas from here, so I think that if
you're generally interested in blue team roles, starting as a SOC analyst is a good way to get
some experience. Next, we have the incident responder, who is basically there ready to deal
with things when everything goes wrong. So, an incident responder might be isolating hosts,
ensuring that there are some intact forensics, and interacting with different stakeholders. And I
think that working as an incident responder can be pretty high stress, especially when you're working
with a lot of unknowns and information that maybe isn't good information, and you have to make good
decisions based on that. But making good decisions, it's also a skill that comes with knowledge and
experience too. Now, moving on to digital forensics, this is quite an interesting field, and having
heard some of the stories from analysts at places like First Conference, and also people that I've
worked with, there are some crazy things that you can encounter. But it does require real discipline
and attention to detail. I'm not that familiar with the tools that a digital forensics analyst
would use, but I do know that there are a range of skills and processes required, like chain of
custody, and of course a deep understanding of operating systems and skills like memory forensics.
So, if you like detail obsessed lab work, then this is definitely worth checking out. But if you're not
so into meticulous analysis or courtroom level documentation, then it might not be for you.
Next, we have the, I want to be a red team equivalent, but for the blue team world, and that is being a
malware analyst or reverse engineer. And it sounds cool, and it is a cool job, but I do suspect a lot of
people are drawn to it simply from the title. Typically, you'll be running samples in a sandbox
and doing static analysis with tools like Kedra, and writing detection signatures, and of course
reports. I think that a strong grasp of assembly and operating systems internals and debuggers are
really important here, and similar to the forensics analyst role, I think that it's a very detail
oriented role that requires long hours of analytical work, followed by writing technical documentation,
and of course plenty of research and reading as well. Alright, so let's move on to threat hunting,
and instead of waiting for an alert to pop, we assume that someone is already inside, and we
basically go looking for them. And I think the biggest thing for threat hunting is understanding
what normal looks like, as well as understanding the different techniques that attackers can use.
Once again, if you enjoy detail-oriented work, and you're driven by curiosity, then threat hunting
could be a good fit for you. But if you like quick wins, and you're not okay dealing with uncertainty
or obscurity, then maybe you should be looking elsewhere. And finally, to round out the blue team
section, security engineering is the hands-on nuts-and-bolts side of the team. One day you might
be deploying or upgrading a new firewall cluster, the next you're scripting an Ansible playbook to
harden hundreds of servers, and then maybe on Friday you're tuning IDS rules so they're not
quite so noisy. Security engineers also have to deal with patch cycles, config reviews,
vulnerability scanning, and generally speaking it's a mixed bag of jobs in one. I think that
security engineers need to have a pretty broad skill set, and also be able to get to grips with
technologies very quickly, and in particular have good troubleshooting skills. So if you enjoy
rolling up your sleeves, tinkering with new things, and basically being the person who makes secure by
default actually happen, then you're probably going to enjoy this role. On the flip side,
if endless patching, emergency changes at weird times, or maintaining other people's misconfigured
boxes sounds like pure misery, then maybe steer clear of this role. Now moving into the realm of
GRC, where admittedly I don't have a lot of experience, but I have worked closely with GRC
analysts before at organizations where the members of the security team, both technical and non-technical,
are grouped together. So with GRC analysts we're generally looking at mapping controls to standards,
spearheading projects to improve compliance, and then also gathering evidence to keep auditors
happy. I actually miss working with my old GRC colleagues. It's a good role if you're a people
person, whatever that means, but also if you're thorough and organized. It can get a little tricky
sometimes, like I've seen a GRC analyst asking simple questions like, is our data encrypted? And
then this has led to a long conversation with many engineers about encryption and how it works, and if
it satisfies this vague high-risk data needs to be stored in a encrypted format sentence, and if
hashing counts, and if the database that auto-encrypts and decrypts, and if that counts as high-risk data
and where the key is stored, and honestly it's bonkers, and even worse when you get engineers
that are either on their high horse or salty that you're asking questions about their precious
database, or simply ones that don't know and try to make it up as they go along. So a pro tip here,
it's okay to say you don't know when you don't know. If you find these security frameworks and
policies interesting, and like to work with people across different departments, and also running
projects that can have a big impact on many areas of business, then GRC is a good place to be.
Let's move on to being a risk manager. Now I think that actually I do have some risk management
certification from like 10 years ago, but I've never really done any real risk management work
other than helping fill in some spreadsheets here and there, so this one is just going off my
general opinion and not really backed by any real experience. But I think that some of the skills
overlap with the GRC analyst, but thinking more strategically about risk and considering what-if
scenarios, and maybe hosting tabletop sessions to explore different risks and their real potential
is what separates it. And it's likely that once again, being able to work well with people is
going to be really helpful, but I suspect in some organizations the role might become a little bit
repetitive. But of course, like I say, I don't really have a lot of experience here, so if you're
a risk manager and want to add some insights, then obviously drop some comments and advice below.
So now we have security auditors whose role can vary quite a bit. They might just be there to
verify evidence and compensating controls that have been listed in a spreadsheet to make sure
that everything is in order, or they might actually be going further to test whether or not
controls are implemented correctly and actually do what they're meant to do. So attention to detail
here and being able to ask good questions and get meaningful answers out of colleagues who are
sometimes unwilling to give you information I think is a key skill, but also striking a balance
between confronting teams about gaps and understanding when something is good enough
is also important. Next, the compliance manager role whose responsibility basically boils down
to making sure that the organization actually meets the laws and regulations. So they might
spend their day tracking new regulations, preparing for upcoming changes, tracking GRC related projects,
or maybe they're more of a program manager which overarches many projects. But I think if you find
regulations interesting and are able to navigate the legal jargon and you enjoy project management,
then I think this role is an interesting one to explore. But as with a lot of GRC roles,
the ever-changing regulation alphabet soup can be a challenge. And finally, to round out the GRC
section, here in Europe we have the DPO, the data protection officer, which is quite a common role.
And I think in other places in the world, like the States, it might be similar to a privacy officer
role. So I'm going to tackle these as one, even if the titles are a little different. But many
organizations here are actually mandated to have one if they hit some requirements. And I don't
really know what those requirements are, but essentially the job is to review personal data
processing activities, handle data subject requests, liaise with regulators, and of course
privacy law and data law mapping, and of course good communication skills is really important here.
Moving into our penultimate section, I wanted to shine some light on the more research-oriented
roles, starting with the threat intelligence analyst, which arguably could be in the blue
team section. But hey, I decided to put it here instead, so let's crack on. Day-to-day, I think
this role is going to be monitoring intel feeds, mapping TTPs, and writing briefs for the SOC
analysts. And I don't have any direct experience here, but I suspect it involves a lot of reading,
keeping up to date with threat reports, and also giving some insight across different data points.
Next, we have our OSINT investigator, and of course here we're going to use a range of skills
and tools and creativity to compile reports on whatever it is we happen to be investigating at
the time. And I think this is a job for people who like to fall into rabbit holes and are able
to really comprehend the importance of small details. And finally, to wrap up the research
section, we have the vulnerability researcher, which I think here is also including the security
researcher role, which if you look on LinkedIn, you'll find so many people label themselves as
security researchers for some reason. But really, we might be looking at fuzzing binaries, reverse
engineering, crafting proof of concepts for exploits, et cetera, et cetera. And the tools
that researchers are going to use are going to vary based on the tech stack that they're working
with, but going deep into technologies and really understanding how they work and reading RFCs is
all part of this role. Now we move on to the home straight, and we're going to talk about a couple
of management or leadership roles. And let's start with the CISO, the Chief Information Security
Officer. Now CISO role varies wildly, like all of these roles do from organization to organization,
but typically they set the security strategy, they own the risk and they answer to the board. So this
means a lot of briefings and a lot of meetings and managing budgets and potentially overseeing
major incidents. Now, having worked with CISOs in the past, I think that all of them should have
some kind of background in security. And the best ones are people with great management and
leadership skills. And the worst ones are CFOs that are handed the title because they don't know
how to delegate. Now to wrap up, role number 20 is our Security Product Manager who owns the
roadmap for a security product or feature set. And a typical day might include gathering customer
pain points, prioritizing features, meetings with developers, and tracking releases. And this role
requires a mixture of skills like product vision, awareness of risks and threats, and good relationships
with stakeholders, and is really a blend of technical and business skills. And that's it for
this video. If you work in a role and have some advice or a story you want to share, then let us
know down in the comments below and I will catch you next time.
