Sunday, June 24, 2012

No Windows 8 RT Management?



According to the above, now month-old Computerworld article by Preston Gralla, it looks like the version of Windows 8, called Windows 8 RT, and currently shipping with Microsoft's new tablet offering, cannot be managed by Active Directory Group Policy.  The RT version is the version that runs on the ARM processor, making Windows 8 attractive to enterprise users because of battery life and application compatibility.  In short, the Windows 8 RT tablet that most will request, if they're willing to give up their iPads, will be no more manageable than iPads or Android tablets. 

Traditional (non-tablet) Windows 8 running on Intel chips can be managed by Active Directory Group Policy.  I know this first hand in my early tests of the OS, but it's not entirely clear right now if any of the proposed Windows 8 Intel tablets can be managed.

Intel tablets are in the works and may ship with the version of Windows 8 that can be managed by AD, Intel: 20-plus Windows 8 tablets with Intel CPUs are in the works -- Engadget, but with a rumored PC-style processor, won't these devices repeat the battery life issues we saw with Windows tablets in 2002?

This issue goes beyond manageability.  Single sign-on will be an issue too, as it is today on non-Windows tablets, if Windows 8 tablets can't join the Active Directory domain.  This means users may experience a user name and password prompt when navigating to Microsoft AD-integrated websites like SharePoint, SQL Report Server, and Outlook Web Access.

The Windows 8 tablet family is not fully rolled-out yet and some of this is speculation, but if Microsoft is not endearing the platform to the enterprise, it's difficult to predict what feature will become the 'killer app' destined to unseat the iPad.

Sunday, June 10, 2012

Skills, skills, skills

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.

Monday, April 16, 2012

Transfer PopCap and TopSpin Game Profiles

Let me preface this entry by letting you know, I am not a gamer.  There are very important people in my life who seem to enjoy PopCap / SpinTop games like Bejeweled and the Amazing Adventure series of games.  Recently I purchased a nice new Solid State Drive (SSD) to breathe new life into an old laptop, and because I decided to go with a new Windows 7 Professional installation on the fast new SSD, there was a lot of profile transferring I had to do before I could get the user profile back to something similar what the user had been used to.

The Windows Easy Transfer Wizard does not transfer PopCap or SpinTop game profiles, which consist of scores and preferences.  A Google search brings back almost no viable profile transfer information except for some specific games like Bejeweled 3.  Even the PopCap support side wasn't comprehensive enough to provide profile transfer directions for all of their games.  Their general directions were only correct for about 20% of the games we reinstalled on the new system.  Also, PopCap recommends that you install the games and then create similar profiles, play the games for a while and then quit the games before transferring the profiles.  These steps are completely unnecessary and may even set you back further.

Through trial and error (lots of error) I persisted in figuring out how to do this and find every game's profile information - like any good forensics analyst.  In the interest of saving your time, I am posting the instructions here.

The following has been tested for Microsoft Windows 7 x64 Professional.  Please look in similar paths for finding profile directories in Windows XP Professional and prior.

***All of these directories are hidden by default.  Turn on the necessary settings in Windows Explorer to be able to see hidden folders.

Make sure you copy the following directories to a safe location and then copy from that safe location to the identical target paths on the destination system (the system to which you are moving.)  

All boot disks are assumed to be C:\ in the following examples.  

I have placed quotes around paths to contain any spaces.  Copy all directories (*.*) therein; even empty directories.

Select merge and overwrite when copying these directories to the destination path.

1. "C:\ProgramData\PopCap Games"
2. "C:\<user>\AppData\Local\PopCap Games\Bejeweled3"
3. "C:\<user>\AppData\Roaming\PopCap"
4. "C:\<user>\AppData\Roaming\SpinTop"

After copying and merging / overwriting these directories into the destination, as you start each game you may be prompted to insert the CD again and define which drive source contains the CD.  This is the last time you'll see this dialog.  Start each game to ensure you can see the transferred gamer profiles.  The last player's profile will be listed as "Welcome Back <Gamer's Name>."

Good luck!
 

 

Sunday, May 22, 2011

Simplify the Landscape with Virtualization - Part 1

Drive and memory image forensics on a small scale is not impossible on a small virtual machine, but performance may be an issue depending on the toolkit.  If you've seen the SIFT workstation offering, it only relies on high-end physical hardware; no doubt to speed up data collection and examination processing.  The latest version of FTK is a client server application, so for it, there is no 'all-in-one' portable version; however, why not virtualize all of the server components that front-end FTK?  Just be sure to give the front-end VM the hardware resources it needs.  While you're at it, think about virtualizing all of your infrastructure.  Last year I decided to virtualize almost server in my data center and was able to reduce my hardware footprint from five servers to two VMware ESX servers, a NAS and a firewall.  I could still virtualize the firewall, in fact my firewall provider makes a virtual appliance, an ISO with OS and app, or the standalone version for Windows.  I could simply P2V my existing firewall or spin up the lightweight virtual appliance and import my current firewall rules.  This, however, I would have to rely on ESXi's virtual VLAN as a layer-2 barrier between Internet and intranet traffic (the DMZ.)  I'm not ready to do that - yet.

So how do you get started?  Depending on your budget, try to pick the most standard hardware you can find - a generic server or workstation with an Intel i7 processor, as much memory as you can economically fit into your system, a discrete graphics card, Intel NICs, and a small and fast solid state system drive to host ESXi.  You can decide later if you want to use local storage for your VMs (forgoing vMotion) or using iSCSI on your NAS.  Download the vSphere ESXi Hypervisor.  Burn the ISO to your CD-R or DVD-R using your CD burning software and boot your hardware.  If the hardware works out, the installation should be a snap.  In my experience, ESXi is most finicky about NICs.  If you have an Intel PRO 1000, you should be fine.  Next, make sure you download and install the same version of vSphere client to connect to your ESXi server.

Once connected you may choose to start fresh by mounting an ISO and performing a new OS install, but if you have an existing physical machine you'd like to virtualize, use VMware Converter Standalone, which will copy your running machine directly to your ESXi server, as a VM.  If you can follow a wizard, you can do this.  It takes some time, but I have been successful with almost every physical machine I've virtualized.


In Part 2, I'll write about one of my absolute favorite things - virtual appliances and I'll also dive into virtualizing the forensics workspace as much as possible without interfering with the raw IO drive imaging requires.