Feeling behind in cybersecurity
It's easy to feel behind when every new topic leads to several more. I'm trying to make my learning a little more manageable.
Taking shape. Has structure and at least one real source or experiment.
Finishing a HackTheBox machine can leave me with a longer list of things to learn than I had when I started. I’ll get something working, then realise there are several tools, protocols, or assumptions involved that I barely understand.
I like that there’s so much to explore, but it can also make progress difficult to recognise. Instead of enjoying what I worked out, I start thinking about everything I should apparently have known already.
That feeling gets stronger when I spend time reading about security online. Someone has found a vulnerability, someone else has finished a difficult box, and another person is casually discussing a technique I’ve never heard of. I end up comparing my own work with a collection of different people’s best moments.
What I’m comparing myself with
A feed doesn’t show me how long each person has spent on their area, what they needed help with, or which parts of security they rarely touch. I know that, but it’s still easy to read the whole thing as a picture of what one competent person should know.
I’ve written about the assumptions I bring to what I see online elsewhere. Here, the assumption is that everyone else has a complete understanding of the field and I’m the one trying to catch up.
That isn’t a useful way to judge my progress. I do have gaps to work on, but I need to identify them in relation to what I’m trying to do. Feeling overwhelmed doesn’t tell me which one matters next, and feeling confident wouldn’t prove I’d filled them.
Choosing something I can work on
I’d like to spend more time following one area deeply enough to become comfortable with it. That might be web security, Active Directory, or cryptography, depending on the work in front of me. I can branch out as questions arise instead of treating every unfamiliar topic as an emergency.
The practical skill I’m after is being able to investigate something I don’t yet understand. Comparing how a system is meant to behave with what it actually does gives me somewhere to start, although I still need technical knowledge to make sense of what I find.
CTFs are useful practice for that combination. I get to look things up, test a hypothesis, make a mistake, and use the result to choose the next step. I don’t have to remember every possible technique before I begin.
My note on allocating research time asks a related question: how much attention should I give one problem before moving on? I’d like to make that choice deliberately, rather than changing direction every time I see something interesting.
Making the next session manageable
For now, that means deciding on a task small enough to work on in one sitting and leaving a note about where to continue. It’s the same kind of adjustment I’m exploring in my HackTheBox setup.
I also want to leave space for being pleased with a result before turning it into another reading list. Rooting a box doesn’t mean I’ve learned everything involved, but it does mean I worked something out that I couldn’t do before.
There will still be days when I feel behind. I’d like to use those days to check my plan and expectations, rather than assume the feeling is a reliable verdict on whether I belong here.
Paths that lead here
- Getting comfortable sharing my thoughts · Waiting until I've finished learning would be a very long wait, especially in security.
- Learning in public · In security, there's always another thing I don't know, so making complete confidence a condition for writing would leave this site fairly empty.
- Making time for the life I want · I've written about feeling behind in security, but this is the part that reaches beyond learning.
- Why I keep rereading sentences · Learning unfamiliar material is going to involve some slow work, and I'd rather make room for it than rush through and discover later that I missed the important part.
Where this note points
- Why the internet sometimes feels fake · Bots and repetitive content can make the web feel strange, but I don't want suspicion to become my default response to everyone.
- Thinking like an attacker · I'm interested in the gap between how a system is supposed to work and what its parts allow it to do.
- How much time should I give a bug hunt? · I'm wondering whether the Kelly criterion can help me think about research time, and where that comparison breaks down.
- Making HackTheBox easier to start · The study ideas I'm trying for ADHD, including an Anki deck and a shell setup that help me return to a session.
More from these beds
- Building a chess openings trainer · I'm often improvising by move ten, so I'm exploring a trainer that helps me practise opening decisions.
- How I think about this site's security · What I want to protect on this site, the choices I've made, and the risks that still need attention.
- Learning about quant trading · I want to learn the maths and testing behind trading, while keeping real money out of the experiment.
- Learning to explain things better · Someone told me I wasn't a good explainer, and it made me think about how often I talk past people.