LAWL

I think that's a personal preference as long as you're doing behavioral analysis correctly. (isolated system, yadda yadda yadda) I find it easier to leverage my static analysis with my behavioral analysis. I'm sure there are people that cringe at the thought of running malware, but in my mind you're going to end up running it one way or another.

I enjoyed the first half of Professional Penetration Testing for its insight into the team/business aspect or pentesting. The second half was good as well.

Hacking Exposed was good. I'm thinking of picking up the wireless book. Its an easy read because its broken down into the different steps of a pen test, and then broken down further into tools/vectors. For someone like me who fits reading in here and there and not in big chunks, I could break it down easily and not have to stop mid thought.

Hacking: Art of Exploitation

Currently reading Reversing: Secrets of Reverse Engineering.

Hey,

I'd like to start off saying, Hi. I've been a long time reader of EH but a first time poster. I'm coming close to completing my undergrad in Electrical Engineering, however the bulk of my free time has been studying cyber security and what not. I currently work as a programmer (Java) for a start up company and love my job. Recently I "pre-interviewed" for a cyber security internship at a local R&D firm and  called in for a real interview in a few weeks.

The pre-interview went awesome, was paired up with someone from the team, talked a lot, he drilled me on my knowledge of reverse engineering and it went fine and dandy. Earlier in the year I started the OSCP training, made it through all the videos and exercises and played in the lab for my 30 days. Awesome time, but sadly got swamped between school work and work work to really hit the books hard and work out what i felt were my weakness, so i plan on re-uping my lab time for another 30 days during the summer before i take the exam.

My question is what do you expect/look for in an intern? I feel I have a good base in most things but i also feel like i lack some depth in some bigger things. The pre-interview was highly technical. None of that "where do you see yourself in 5 years?" mumbo jumbo. From his questions I'm assuming its mostly reverse engineering.

Any tips to what you expect an intern to understand at least? I'm kind of afraid of getting interview by a computer science type guy, seeing as this was an "interview call" for computer science and computer engineers, that's going to drill me more on those fundamentals that I've only been to exposed to in passing.

Thanks in advanced.

Super fun... and super frustrating... masochism at its finest.

EDIT: got the 'try harder'...... Choice words were yelled....