I wonder if I could have the benefit of your experience please. I have an 80gb hard drive to examine that has been encrypted using PointSec. I have access to the machine at the operating system level and can image using FTK Lite or Helix Pro 3.
I have sucessfully imaged the drive but when I try to load the image in WinHex I recieve and error message 'Traces of a 74.5 GB (156297216 sectors) NTFS partition found in sector 2048. Size not plausible. Will not be added to partition list.'
Is this message as a result of the encryption or some configurational issue when I imaged the drive?
Many thanks in advance
Richard
Hi Diesel,
No I did not; I assumed that the imaging process operating with the PointSec process running in the background would enable an image to be taken. One of my colleagues from our Canadian office believed this would work using FTK Lite.
But I do now have my doubts…… (
I have not worked on a Pointsec disk but have worked on a safeboot one and I could image it fine but could not do anything else until i decrypted it. Maybe that could be causing you an error when you load it in to winhex as it can not read the file system ?
Thanks Deisel, I suspect your right. I have done this kind of exercise before but have chosen to decrypt first before imaging and that worked just fine.
I will await other responses before doing anything further but it does worry me that we would have to go through this process of unencrypting before we can image.
Many thanks
Richard
You have two options
1. decrypt and image
2. Do a live image of the C\volume
There are some ways to boot to a Windows bootable CD and image but it still access the disk I believe but i have yet to test it that far.
FTK imager on a logged in machine works fine (albeit, not particularly forensically sound) on a Pointsec encrypted machine (but does require user credentials or an authenticated user session).
There's a Pointsec driver for Bart PE you can get from checkpoint that will let you boot from a PE CD which is better (still not great forensically, since PE is -not- modified to avoid changing the original disk). This method works just fine once you've built the CD but it can be a pain to get that far.
VMWare Live View is the preferred method, and Pointsec works fine in VMWare when emulated (although the OS detection will often fail since Liveview can't access the unencrypted disk to determine the OS type - just set it manually).
There's also a recovery disk that can be created with the original decryption key (if you have it) that will strip the encryption from the disk. Whatever method you choose, work on a copy and don't touch the original, since these are all pretty invasive.
If the Pointsec version is v6 or later, then there is a mounting tool from the manufacturer.
https://
If the Pointsec is not supported by the mount util, then
1) If you have the password and decryption cd or floppy. Decrypt the drive first and image as usual.
2) If you don't have the password or decrypt floppy, then not much you can do.
3) If you don't have password, but the system is logged in use FTK Imager to create a logical disk image.
I have done two of them, both were Pointsec v4 where I had to decrypt them first.
Good luck.
The Digital Forensics Solutions blog has a post about the examination of pointsec drive including obtaining the image.
http//
As another member mentioned, another option is to use the Pointsec Dynamic Mount Utility to acquire the image. In my experience this program wasn't stable in XP and Vista but works fine in Windows 7. You can get a copy of the program from the Pointsec installation media.
Corey Harrell
"Journey into Incident Response"
http//journeyintoir.blogspot.com
So far I have worked with BitLocker, TrueCrypt, and Utimaco.
Originally, I imaged at physical and logical, because I was concerned about the mounting of the physical image and decrypting it that way.
Turns out, it is simpler to get an image of the physical and mount it, and let the various encryption software recognize the drive. This keeps the original (allowing booting into a virtual machine), and then you can "live image" the mounted, attached, and encrypted image, without actually firing it up in a virtual machine.
Let me know what route you took, and how you mounted it.
Thank you all very much for taking the time to respond. I have imaged the drive using FTK Lite but when I try to add the image to my X-Ways Forensics tool I get the error about the unlikely sector size and that is what made me question if FTK was the correct tool. In reading your responses it would seem that something went wrong in the process rather than the approach being wrong. I will try the exercise again on another laptop and use another external hard drive to obtain the aquisition.
Once again, many thanks to you all.
Richard














