As a follow-on to my previous post with this title, I wanted to keep the story going; in fact, there are likely to be several more posts in this series, so stay tuned.
And hey, I’m not the only one sharing my journey! Check out Josh’s blog, particularly his recent post about how he broke into cybersecurity! I might have been drawn to Josh’s post because, like me, he’s a former Marine, although I can say that I was in the Corps back before computers were in common usage, back when we used radios that were 1950s tech, built in the 1970s. We didn’t cross paths…I was off of active duty 12 yrs before Josh went to boot camp, but even so, there’s some commonality in shared traditions and experiences.
Okay…back to it!
Programming
Programming is talked about a great deal within the industry, particularly within DFIR. Some folks will say that you absolutely need to be able to program, and even have very strong feelings about the language of choice, and others will do just fine with basic shell scripting and batch files. I’ve met some folks who are really great programmers, coming up with either individual projects, or more team or community based ones, like Volatility. A lot of the programming very often seems specialized, like HindSight, while other projects and contributions might be a bit more general. Even so, some of the absolute best DFIR analysts I’ve ever worked with have had minimal programming capabilities, not going much beyond shell scripting and regexes.
As a result, when it comes to programming, your mileage may vary. I will say this, though…the experience of programming, in whichever language or framework you opt for, has the benefit of helping you understand how to break things down into manageable “chunks”. Whether you’re writing some code to manage logs, or you’re leading an IR engagement, you’ll realize that to get from A to Z, you first have to get from A to B, then to C, and then to D, and so on. Accomplishing a task by writing code forces you to approach the problem in that manner, and as such, has benefits outside
[…]
Content was cut in order to protect the source.Please visit the source for the rest of the article.
Read the original article: