Fog and AES-256 Drive Encryption
-
If you could limit the encryption to just User folder space then you will have less issues. OS and Program Files do not need to be encrypted, and doing so would actually degrade performance.
-
The trouble is we image our machines to a base level, and then join them to the domain, and throw them on the shelf to sit until someone needs to swap out. And we want the ability to browse the entire drive, securely by using the application on our support systems.
The performance hit should be negligible as all that needs to be entered at power on, would be the decryption key and power on password.
So it’s really a question of, will it work? I’m encrypting a system now and will test with a Raw image upload onto Fog and try to restore.
I’ll provide an update when its done in a few hours.
-
You should not need a “Raw” image format.
You’re encrypting the data on the drive, not the drive itself. So long as the drive is readable as ntfs,ext,etc… you should be fine.
-
When connecting an already encrypted drive to a Windows Machine, the system immediately tells me: “You need to format the disk in drive X: before you can use it.” meaning the entire drive is encrypted.
Using DiskCryptor to mount the drive (and provided the correct encryption key) I can then view the drive as any other USB device.
In Windows Disk Management the drive is listed as RAW
-
I suggest using BitLocker, or at least trying it to see if it it fits your needs better. You should also be able to specify via GPO to have any/all user folders encrypted by machine with BitLocker. That way it wouldn’t matter who you had log in to the laptop, their data would automatically be encrypted within their user folder.
-
Unfortunately Bitlocker isn’t available for Windows 7 Pro, and we really don’t want to purchase it for all of our computers.
-
I think need2 may be on the better track here especially if it is an AD environment you should be able to control everything via policy and still use re-sizable images or even syspreped universal images. You will want to limit encryption to home directory’s because there is a performance hit whenever you access encrypted data.
-
You’re right. I was thinking more of EFS. The following is dated, but relevant.
[url]https://technet.microsoft.com/en-us/magazine/2007.02.securitywatch.aspx[/url]
-
Windows 7 ultimate and Enterprise include bitlocker as well as windows 8 and 10.
-
We are running windows 7 professional, and are not going to update to windows 8, windows 10 maybe when it drops.
[quote=“Joseph Hales, post: 46729, member: 18131”]Windows 7 ultimate and Enterprise include bitlocker as well as windows 8 and 10.[/quote]
-
[quote=“Tom Elliott, post: 46717, member: 7271”]You should not need a “Raw” image format.
You’re encrypting the data on the drive, not the drive itself. So long as the drive is readable as ntfs,ext,etc… you should be fine.[/quote]
Yeah. re-sizable, everything. I don’t think there’s a need at all to use RAW for this. Also, the earlier comment about encrypting just the user data is a good one. Win7Pro has built in encryption… you can set it with policy.
Also, if you used user-based enumeration shares (windows server 12 and up), you can specify encryption of the redirected user data on the server itself, and have the user files NOT EVEN EXIST on the local machines. That’s how my environment is set up. It’s done through GPOs.
-
[quote=“Wayne Workman, post: 46752, member: 28155”]Also, if you used user-based enumeration shares (windows server 12 and up), you can specify encryption of the redirected user data on the server itself, and have the user files NOT EVEN EXIST on the local machines. That’s how my environment is set up. It’s done through GPOs.[/quote]
That too is how we have ours set up. I really, really love not worrying about someone’s files when a drive dies anymore.
