Thanks for all the questions. I stumbled on my own solution that I think is somewhat unique. It has the benefit of taking heed to the cautions above (not fiddling with company stuff -- at least not much), leaves everything encrypted, dual boots, and lets both OSs access shared data. In short, the solution was like so:
- Defrag
- Use Windows 7 partition table to shrink itself as small as possible (ended up being about 130G for me)
- Create three more partitions form the resultant unallocated space:
- 64M for Linux /boot
- 30G for Linux
- The rest for TrueCrypt
- Use MiniTool Partition Wizard Home Edition to set the partition types that will be Linux based as having IDs of 0x83 (from their created ID of 0x7 for NTFS)
- Use EasyBCD to create a Linux boot entry in the Windows boot options menu
- Install Linux with LUKS/dm-crypt encryption
- Install grub to the /boot partition, not the MBR
- Create a TrueCrypt encrypted device from the last partition from either Win or Linux for shared storage
So... perhaps I've still "violated" the IT policy via the letter of the law -- I'm not positive, but don't really think this is the case based on talking about my plans with someone reasonably high in IT.
I've thought more about it, though, and called to mind that my company has no issues with people using their personal MacBooks at work, and I know on IT guy who uses one and uses TrueCrypt (or maybe it was FireVault) to encrypt his work files on it. Many probably don't encrypt at all, I would suspect.
So, if the issue is purely that this is "company property" vs. my personal computer, I may be an offender. If the issue is due diligence to protect everything, I've say I've covered the bases. Even more so, I've exceeded what I hoped for above -- the SafeBoot partition and default MBR are all still exactly as they were, safe being shrunk and a slightly modified partition table. I've verified that company patches still work, and thus I should be "on the grid" to the fullest with this setup.
I think all in all it was quite successful.
I wrote up the procedure HERE, as I hadn't seen anyone use this particular method in my searching. Thanks for all the comments.