Infosec researcher | writes @ https://shellsharks.com

Mastodon: @[email protected]

  • 181 Posts
  • 224 Comments
Joined 1 year ago
cake
Cake day: May 9th, 2023

help-circle








  • There’s no one path in to be sure. But there’s lots of ways to educate yourself and build a “hireable” portfolio from home and without getting a typical 4-year degree. Learn to code, get some applicable certifications, start a website (as your digital portfolio), contribute to open source or spin up your own project(s), etc… The IT/software/cyber market is not at its peak (in terms of opportunity), but we’re definitely still here and there are openings. It’s still a great field with a lot of perks if you can weather the challenges of “breaking in”. It’s also not going anywhere, despite what some may lead you to believe given the advent of “AI”. For those of us in tech, we’ll be the first to tell you that our jobs are pretty safe.

    If it’s infosec you might be interested in, you may find this guide I put together and typically share interesting - https://shellsharks.com/getting-into-information-security.

    Good luck!













  • Overall, yes. Day to day y’know it varies. Pure “security work” is, for me, genuinely interesting and I spend legit personal time learning and working on projects, for no other reason than they are kinda fun. What I do as a security engineer for a corporation day-to-day and week-to-week doesn’t always translate to the “fun stuff”. So my answer is somewhat nuanced. Yes, I do like cybersecurity. But no, I don’t always like the work in terms of how it manifests in corporate life.









  • I wouldn’t worry about certs to start, especially not OSCP. Since you are in the software/dev space, I would consider security roles in the AppSec or CloudSec space as places to jump first. For that, consider going through PortSwigger’s web security academy (free) training online to learn more about web vulns, their impact, how to mitigate, etc… If you want a cert, consider one from a cloud vendor and apply to jobs that use that vendor. If you can do even basic scripting, understand app-related vulns and use a few appsec tools then you should be an easy hire for a lot of places. (That said, I’ve been hearing the market for infosec is atrocious right now).




  • Not a bug bounty hunter myself, but it seems like one of those things that you just have to jump into and start trying to do. So many bounties seem to be pretty low-hanging fruit type of stuff. The payouts might be either LOW or non-paid, just recognition type stuff, but seeing an accepted bounty submission come back does a lot for your confidence. It’s like CTFs in a way. Getting into CTFs seems intimidating at first, but then when you go actually do one and you have some level of success, it starts to feel a bit more approachable, you get more XP and you do better the next time.

    You could also check this out https://www.bugbountyhunter.com/zseano/ and anything/everything from https://portswigger.net as that team is the best I know in terms of cutting-edge web app research.



  • That’s a loaded question 😅. One that can be answered in a few different ways… From a technical perspective, “infosec” is a relatively vast field comprised of a lot of sub-disciplines, so from a tooling and procedural perspective, it varies from job to job. Some would argue a lot of what we do is just theater, and for many orgs and many “pros”, this may very well be true. At the root of it all though, you could say our job is to ensure the Confidentiality, Integrity and Availability (classic CIA triad) of data/systems, keeping in mind the balance/tradeoffs between security needs and business requirements. To do so, we employ a variety of tactics, techniques, tools, methodologies, frameworks, etc… Another way to boil down what security folks do is in the lens of “risk”. Most business and IT decisions in general come down to risk-based decision making and security is no different. Security teams should understand the risk introduced by the threat landscape coupled with the respective data, attack surface, business assets, etc… to help inform the business how to reduce security risk to acceptable levels.

    Hopefully this answer isn’t too vague and non-answer-ey!