Posted in Cybersecurity Careers

If you're trying to get started in cybersecurity, build things and show your work. Pick something that…

Daniel O. — Senior Cybersecurity Consulting Engineer | EDR/XDR · Zero Trust · Architecture & Engineering | CISSP · CCSP · GIAC

If you're trying to get started in cybersecurity, build things and show your work. Pick something that interests you and build a project around it. Document what you did, and post it on GitHub or a blog so others can see it.

Here's the part most people skip. If you're studying pen testing, you've seen hacking lab walkthroughs everywhere, and those have their place. Be different. Write yours up as the deliverable, not the diary. That means a report, as if a customer paid for an engagement and this is what you handed them at the end. Don't forget to label it as a lab exercise so nobody mistakes it for leaked client work.

A walkthrough shows you can document steps. A report shows you can explain what your findings mean to someone who has to act on them, and that's the reason we get hired to work in cyber.

That's one example. The longer article this came from (link in the comments) has project ideas for identity, GRC, offense and defense if you need a starting point.

If you're using a lab platform, check the rules before you publish. Some only allow writeups for retired content.

I still do this, just for different reasons. I code as a hobby. It isn't about building my career at this point. I enjoy it, and publishing my projects might help someone else.

My most recent public project is a set of lab build scripts that go from an ISO to a fully populated AD domain. I built them because I was tired of manual builds, and of other people's automation that wanted half a dozen side tools deployed before I could even start the build.

I'm now working on a much larger security project that, if I ever manage to finish it, will be my biggest public release yet. Same motivation. It's a geek (me) building the tool I wish I could download.

And yes, my GitHub link is in my profile on purpose. Public work is evidence, and it points people back to me when a client looks me up.

Projects do two jobs. Building one teaches you, and publishing it is proof you learned something useful.

So build something, anything. Write it up like someone paid for it and put it where people can find it. Then do it again.

If you're trying to get started in cybersecurity, build things and show your work. Pick something that…

3 reactions · 1 comments

Comments

Daniel O.: This one started as a section of a longer article on getting into cybersecurity. The full article covers more ground, and it links to every post pulled from it. https://www.linkedin.com/pulse/theres-one-true-path-cybersecurity-here-few-anyway-daniel-Daniel O.-dqene/

Read and join the discussion on Cyberr