Using truecrypt with MS SQL Server -


i'm trying create ms sql server database on truecrypt volume. need system have following property: if truecrypt volume not mounted impossible access data in database or database log files. doing following create database:

create database test1 containment=partial on (name='test1_data', filename='d:\sqldata') log on (name='test1_log', filename='d:\sqldatalog'); go 

where d: mounted trucrypt volume. seems work fine in creates specified files , useable database. however, not confident secure. think storing data somewhere other d: volume. can following:

use test1; go create table persons (id int, name varchar(255)); go  insert persons values (1, 'jason'); go 

then close db client, unmount volume, reopen client (sqlcmd), , do:

use test1; go select * persons; go 

and data put in. means there storage happening outside truecrypt volume. doing wrong, misunderstanding something, or i'm trying not viable ms sql server?

this solution insecure. data can automatically spilled sql server tempdb in various scenarios (e.g. during sorting or hashing) may end leaking content wanted protect. i'd step away truecrypt in case , use transparent database encryption if possible (which automatically encrypts tempdb after first database encrypted). or, if want use tc, protect tempdb truecrypt , make sure nobody force dismount volumes. otherwise ask database corruption , data loss.


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -