Since taking a management job in corporate America, I'm constantly making sure that my technical skills are up to speed. There's a lot of self-doubt going on because I can't always be hands-on during the day.
What I've come to find out when I do pitch in, is that none of my technical strengths have atrophied. If anything, the tedium of management has inspired me to learn more and more in my free time.
I get to interview lots of candidates who claim to have the skills required for the most senior-level technical positions. It becomes even more of a challenge when I know I am going to hire a temp, because I can't spend the money to send a temp to training. My initial interaction with folks that post good-looking resumes is usually a 'pull no punches' over-the-phone tech screen.
My questions include, "Take me through the steps of an intrusion. Tell me how you'd break into my company and please go light on the scanning. Give me an example of a web pen now and later give me an example of a 'Layer 8' or social engineering combo tech attack at the endpoint."
The answer to these questions vary wildly, although they really shouldn't. There are frameworks for this kind of thing, but I am not looking for someone to read out of a book. What I want to understand is, how does this person think? Do they have an understanding of perimeter security technologies? Do they have an understanding of the stack? Can they read a packet trace? Do they know TCP/IP internals? Are they familiar with routing and switching? How many tools do they know about and do they have a basic understanding of how and when to use each one? Do they know what kind of information trips alarms and raises eyebrows? Do they understand the concept of software vulnerabilities or how to exploit one?
In short, it becomes obvious when a person says they have experience driving a tractor trailer, and they freeze when you sit them behind the wheel of a big-rig after you ask them to back into a loading dock. This does not happen when someone drives trailers for a living.
These answers should be second-nature to any qualified candidate. There are a dozen ways to 'skin a cat' and there can be more than one way to get a remote shell on a Windows endpoint, but I want to know they know of the tools that can get them there.
So many candidates are either policy wonks pretending to know the hands-on or network jockeys that can get as far as, "Okay to start I'll scan the network for open ports..." Duh, really, oh no, that won't get anyone's attention. Why not DDoS them while you're at it? Come on now, don't waste my time. I don't care if you're an nmap ninja, you're going to trip an alarm. Don't scan! Most companies have between 1 and 120 web listeners. Do a little research (hint LinkedIn, whois, and DNS) and find out what's hosting these services and take me in at layer 7. Now that's what I'm talkin' about!
Oh an you'd better know how to pivot off that web server without 'uploading your toolz."
The next question, which takes most candidates 15 minutes to answer is, "The network jockeys hand you a noisy IP address on the private-network side of the firewall. It's clogging a remote link on it's way to a C&C in China. Without asking anyone where this address is used, Geo-locate it on our 120 site network. Oh and BTW, you have read access to all routers and switches globally and the firewall log is being sysloged to Splunk. Figure out who this noisy bastard is, and tell me what you do once you find it."
The answer may require a few more questions of yours truly, but beyond that, if I don't hear tracerout, ARP cache, show mac-address-table, or even switch cache, I'm going to start winding down the conversation.
What happens when they get past step one? Okay, now you've found it big fella, what's next? Call the local IS guy to snap the memory with FTK imager? What's that, it's hosed and no one can do anything with it?
Okay, option two, lose the memory but get the box off the network? Good! Now what? Package that sucker and send it back to the team? Bingo.
Now FedEx drops it at your desk - talk to me. Remember, what you do from here on out might end up being repeated to a jury, so take it easy junior. I want to hear about evidence collection sheets, RO imaging, and hashing.
Now you've followed all the steps, tell me what you're looking for. Do you have a replay sandbox? Can you data carve in slack space? What's a mutex? How do you hash out all known files? Is any file injected and doesn't check out?
My point here is don't bluff. Just say, "I don't know" or "I'm not right for the job."
Knowing all of these things comes with knowing you don't know everything, but you've been exposed to a lot. You're always learning. That's okay.
Maybe you were a systems admin for ten years before getting into real info sec, and that's perfect. You know about Microsoft Sysinternals (psexec), joeware.net tools, the Foundstone tools, Elcomsoft, Hyena, and free UNIX utilities ported to Windows like nc and grep. You know your way around a 'NIX shell and you know the difference between old school System V commands and the kinder / friendlier Debian-based distributions.
In short, if someone was to brain dump all the pieces and how to put them together, that wouldn't help 99% of the people and the book would be 2000 pages long. You've got to do it yourself and experience it first hand. You're not going to learn this at ITT Tech or Clark. You've had to have gone through the experience of automating yourself out of a job with Perl and batch cmd. Boredom is good as long as it leads to discovery through an innate hunger for knowledge.
It's all about the skills my friend.
No comments:
Post a Comment