Monday, June 2, 2008

TechnoSecurity Day 1





I arrive at the marriot in my smelly clothes, hauling my backpack full of travel gear and I find my way to registration...can you say lack of directional signs?

The registration process was simple. Last name only and they verify on a check-sheet. Hmm a security conference and the only verification is done by last name? No other authentication mechanism, such as presenting a receipt, or confirmation email? My how interesting.

Anyways I got my fancy padfolio and badge - kind of cool by the way - and an obnoxious bag from a sponsor. Sorry guys but that's rediculous. I thought to myself "what the hell am I supposed to do with this huge bag?" I dumped the bag as soon as I could.

Quotes from the day:

"Did you see that cop's wrist? Harley accident in the mountains, he hit black ice and was dead for 27 seconds."

I did a massive double take on that one. Did I hear that right? I ended up meeting said cop on day two. I'll have to confirm that story with him. Nice guy by the way..will add comments on that discussion later.


First talk of the day:

Roel Schouwenberg(sp?) from Kaspersky labs talking about Malware Ecosystems and their evolution.

Takeaways from his talk:
The threat is not changing (people like to say that), it already has changed.
Malware authors are using search engines optimization to get their hacked sites rated higher on google searches so it's more likely the links will be clicked.
They are expecting 20 million threats this year (ouch)
He spoke on a Criminal to Criminal business model - kind of like the B2B model but for criminals. There are multinational rings involved and the players take roles such as (translators, money mules, R&D, Spammers).

I found that particularly interesting in that he exposed a little bit about the organization of the criminals, which is to say that it's a pretty impressive mode of operation.

Roel surmised that the next large area of focus for criminals will be mobile banking. Which is to say banking from a mobile device will be very interesting shortly.

Talk 2:
James Aquilina - Stroz Friedberg - Malware investigations and their legal implications. This talk was a lot of lawyerese, but he made some very interesting points and had good information.

If you didn't know, James was the prosecutor in the Anchetta case (botnet related, received a lot of press). James had a very amusing talk at first. He had great graphics designed to make complex topics understandable by judges and non-technical people.

Some interesting stuff on the implications of using packet sniffers for investigations such as collection beyond the scope of the investigation so, instead of doing a full packet capture at a choke point, you should only do the capture against the affected victim computer and the attacker. Doing the full capture could be outside the scope of the investigation, this could come in to play in many cases. Other points:

When investigation/prosecuting a minor who's a malcode author you may not refer to them by name in any notes. This could be construed as releasing their name and identifying a minor is a no-no.

I have a lot of post processing of his talk to do.


Talk 3: Chris Mellen - AccessData - Volatile and memory analysis in a network environment.

I actually ended up taking no notes during this talk. It quickly seemed to turn in to a "this is AD enterprise and here's how we do memory analysis" talk. The talk ended early which allowed me to sneak in to a great talk..

Talk 4: Jack Wiles - Social engineering in progess.

Wow what a good talk. I ended up not taking notes here either, mainly because I was focused on Jack. Lot's of props and even some sleight of hand tricks to illustrate the point that as adults our minds have been trained to ignore the "sleight of hand" or the tricks of the social engineer. Very interesting stuff from a social sciences standpoint of looking at human relationships and trust.


Thoughts from today:

When did it become ok for us to trojan corporate systems with "forensic tools" that utilize rootkit hiding mechanisms?

Techno Security - Travel

I had such an exciting adventure attempting to get down to Techno Security that I decided I needed to have a dedicated blog entry about it. Please note this is a break from IR and forensics.

My day began at 6 am. I arrived in Philadelphia for my connecting flight to Myrtle Beach around 1pm. My flight was scheduled to leave at 3:30. No worries, just a 2 hour layover...yeah right. And that's when things went awry.

As an experiment in not just awareness but self-amusement I decided to take my notebook with me on my trip so I could take notes on what happened during my trip and write down any observations at the same time. So without further ado, here are some observations, quotes and other stories from my beleaguered trip down.


The following is from my Airport of Origin:


Observation: 9:15am

"8 TSA guys at baggage check. One spinning in chair getting dizzy, standing up then attempting to walk. Other TSA employees standing by laughing".

- comment - tax dollars hard at work, no problem with homeland security here.

At the security check I attempt to add a little humor to the screening process.

TSA Guard:"How are you today"
Me:"Overdressed apparently" This in reference to the de-robing that passengers must undergo.
TSA Guard:"I take it you have to pee"
Me:"No not really".

She clearly did not get my brand of humor.

-comment- Why is it that I can't take a certain size container of "liquids or gel" onboard but I can take bomb making components - copper wire, batteries, tools etc.

-comment- Oh great a turboprop, I love massaging chairs.

Observation:
10:00am Young man across the way using a macbook sets it down on the chair next to him, and goes to bathroom.
10:05am Young man returns
10:18 Old man across the way using an Asus EEEPC sets it down on chair next to him, and walks down the hallway.
10:23 Old man returns

-comment- Can people really be that trusti..stupid?

I refer to Johnny Long at this point...No Tech Hacking all the way.


There were two women sitting behind me at the airport having a very candid discussion about HR issues in a corporation. I won't get in to details but let's just say people need to be more aware of the conversations they have in public. We do pay attention even if we appear to be "pre-occupied". I was pre-occupied with capturing their conversation.

The following is from Philadelphia:

After 2 hours of the following comment our plane arrived...
Woman at Gate: "The flight to Myrtle Beach is running behind schedule due to weather. As soon as it arrived it will need to be fueled, cleaned and catered. As soon as that's done we'll begin the boarding process".

After a relatively short boarding process the captain gets on and says (by the way you never want to hear this)
Pilot flight 3245: "Ladies and gentlemen, unfortunately we can't push off yet, it looks like we took a bird in the #2 engine and maintenance just needs to take a look at it".

Observation - The maintenance crew pulls up and "takes a look at it" and essentially confirmed "yep there's a bird in the engine" and drove off.

My plane finally pushes off from the gate and we make it out to the tarmac for taxi and as we are pulling near the runway I look out the window and see approximately 15 airplanes stacked up in holding positions. Uh-oh that can't be good...

Pilot Flight 3245: "Folks this is the captain on the flight deck. I have bad news, they're holding up all the southbound flights at this time. There's a line of thunderstorms over virginia that's slowly moving east. It's going to be about 15 minutes before they update us".

25 minutes later...

Pilot Flight 3245: "Folks, we're headed back to the gate. They've found us a new flight path that will take about 2 hours but we don't have enough fuel. We need to head back to the gate to refuel and we'll be on our way. Thank you for your patience, we're trying to get you to Myrtle Beach as soon as possible."

At the gate some time later...

Pilot Flight 3245: "I know it's a pretty depressing situation folks. The flight attendant's will bring around water if you need a drink."

30 minutes later still at the gate...

Flight attendant (speaking to woman nearby):"No Ma'am I have no idea, I've been in the back there and know less than you." This in reference to what's taking so long and when we're going to leave.

The plane finally pushes off again and as we are being backed up so we can begin to taxi, the plane is all of a sudden heading back to the gate..my how odd. When we get back to the gate the co-captain opens the flight deck door and gets on the radio and says..

Co-captain:"Ladies and gentlemen I have a bit of bad news...we've missed our flight window and the big wigs upstairs have said we can't go. We missed our flight window, your crew has been in service for 15 hours and the FAA won't let us fly because we've timed out. Please bear with us, we're going to try to find a new crew."

Meanwhile, the baggage loading vehicle has approached the plane and is unloading us...

Flight attendant: "Ladies and gentlemen we have some good news to bring a smile to your faces. I'm breaking out the liquor cart. Ya'll have put up with more than you should have to today to I'm going to bring around the liquor cart."

The flight attendant made it through the first 1/3rd of the plane before they de-planed the passengers. Great I didn't even get a drink.

And this folks is where we start to have some real fun. Emergency planning 101: HAVE A PLAN.

At this point there are over 100 angry passengers that have spent the last 4 hours, waiting for their plane to take off. Not a lot of happy people... The airline set up three gates to re-ticket passengers, provide hotel and food vouchers and handle issues.
Fantastic..except it took about 15 minutes per passenger. Now what you ask did they do about the angry passengers? That's right they called security on them. By the time I arrived at the desk, all hotel vouchers had been used and they couldn't find me a hotel room anywhere. Another 30 minutes of waiting..

I walk over to the Airport Marriot at 9:15 or so and check myself in.

The next morning I arrived at security. My Driver's license was viewed as suspicious by TSA..why? Because my address had been crossed off on the front and was written by hand on the back on a DMV sticker. Apparently in NY this is acceptable, but not in Philadelphia. Interesting...TSA has different policies in different areas? Note if you will that TSA said nothing in the NY airport. Maybe the guards should have done more than spin in chairs and get dizzy.

I arrived in Myrtle Beach a day late - the day the conference started. My bag as it turns out was on a different flight..one that got delayed. So, I was in two day old clothes, full of airplane stink and I couldn't check in to my hotel room because it was too early..so what else could I do but hit the conference?

The airline you ask? US Airways...

Wednesday, May 14, 2008

Headed to Techno Security

Looks like I am headed to Techno Security 2008 in Myrtle Beach. I'm looking forward to meeting up with some people and sitting in on some interesting talks. Good times...

Monday, May 12, 2008

Spot the fake

When I've instructed people on IR I have run them through a live response scenario where the scenario is fairly obvious (I provide a friendly popup). My favorite thing to do to folks is transposition of letters in commonly associated programs and services. Apparently attackers still like doing this. Can you spot the fake? What are the inconsistencies between the two? Which one is real?
Finally..why does this work? Read this paper if you're interested.


Service Name: Event Log

Description: Enables event log messages issued by Windows-based programs and components to be viewed in Event Viewer. This service cannot be stopped.

Path to Executable:
C:\windows\system32\services.exe

Logon:
LocalSystem

Service Name: Events Log

Description: Enables event logs messages issued by Windows-based programs and components to be viewed in Event Viewer. This service cannot be stopped.

Path to Executable:
C:\WINDOWS\system32\drivers\csrss.exe -k NetworkService

Logon as:
.\Administrator

My arch-nemesis

Over the weekend my honeynet got pwned. I mean that in every sense of the word. I'm looking at a 50% rate of compromise. I contained the honeynet and planned on dealing with it this morning. While performing some live response on what I'd targeted as patient-0 my screen went black and my room suddenly got quiet. My office usually hums at about 70DB so when my poweredge server, firewall, precision workstation, switches, kvm, mac mini, 2 workstations AND MY HONEYNET go quiet it's pretty noticeable. I had been in the process of collecting physical memory and...poof.

At first I thought I had popped the breaker. Let's face it I have quite a bit plugged in. Then my thought process started up again...wait I've never popped the breaker..why all of a sudden?

There was a bit of shouting and people started running down the hall to see if I'd broken something..kind of funny. I then remembered something..electricians had been sighted early in the day. My subordinate confirmed this.

"I just saw someone run from that office in to the other room" he said pointing further down the hall.



I walked to the next office and poked my head in..

ME: "Hey are the electricians screwing with stuff?"

COWORKER: "They shouldn't be".

ME: "Well my office just went dark, where are they?"

COWORKER: "Oh, they're next door, let's go talk to them"

ME: "Probably a good idea".

We both poke our heads in to the next room and I spot a power whip laying in the middle of the floor as if to mock me and display the prowess of the master electrician and 3 guys looking at prints. On the wall I spot an open single gang box with wires mashed in a wire nut. That wall is the exact wall where I get power...

ME: "Are you guys messing with power in here?"

ELECTRICIAN: "We saw a few extra wires attached to that whip and had to disconnect it" he says looking at me sheepishly.

...silence...
...silence...
...silence..

ME: "You just took down my office".

ELECTRICIAN: "Yeah sorry about that, that's my bad. I had to disconnect the leads on that whip".

I was lost for words. My arch-nemesis killed all reasonable hope of me collecting information. The vm on bootup gave me some corrupted filesystem errors and the other virtual machines I had running had obviously lost power as well.

Why is the electrician my arch-nemesis you ask? Let's just say this isn't the first time they've struck.

Thursday, April 24, 2008

my workstation...the porcupine

I was working on a case the other day and took a quick break and when I looked down at my workstation I thought to myself "my how my workstation looks like a porcupine". I had 5 USB dongles sticking out of the thing - one for each vendor who forces us to use dongles. In the old days of dongles we used to have the leaning tower of pisa because the parallel port dongles were so large. Is there no end to the dongle insanity? Why must each vendor require their own dongle - instead of forming a consortium, sitting down at a table and figuring out a few things. I know my life would be a little bit easier if I didn't have to keep track of all those porcupine quills.

Wednesday, April 23, 2008

Ripping the Registry Live

So I have been quiet lately and there's been quite a bit happening. First off, Harlan Carvey released RegRipper. This tool is impressive and awfully useful, not to mention NEEDED. If you haven't checked it out, do so. Harlan has said this tool is not designed for live response but I've been dying to get it in to a live response methodology. Well with F-Response I can do it now. Here goes ripping the registry live...sorry for my camtasia-fu or lack of.





A few things if you haven't registered with F-response.

The field kit requires that you put the dongle in the target system - This video starts after I've done that.
The connection is not encrypted - yet.

In addition, there's a new version of regripper out. This is just one of the many tools that F-response can facilitate the use of. See why it's so cool?

EDIT: I put the video up on youtube..blogger's video was just too small.
EDIT: Harlan corrected this statement for me: "Harlan has said this tool is not designed for live response." This should read "RegRipper is NOT intended to be run on live Registry hive files".
EDIT: I realized an error in the previous video. The new one is correct.