Access DB File Encryption

[Guest]

We have a few access db's that we want to make sure can't be taken when
someone leaves..

I thought using windows 2003 encryption on the file as the admin would work
so if the mdb file were copied to a flash drive they would not be able to
read it..

Does anyone know if this will work, or will people have issues accessing the
db's ?

Any suggestions ?

 

[Guest]

I believe file encryption will only prevent a snoop from reading the contents
of your hard drive if the PC were stolen and someone attempted to access the
hard drive without the proper log-on credentials (for example, the hard drive
was installed into another PC as a slave drive).

At my place of employment, all PC's (desktop and laptop) were updated with
"Whole Disk Encryption", a software product that is not marketed by
Microsoft, but the intent of which is to encrypt the contents of the hard
disk drives. This was done due to some recent high publicity thefts of
laptops, where the employees involved had very sensitive information on the
computers (names, SSN's, addresses, etc. for thousands of employees).

I can tell you that with WDE installed and working, I have no problem
copying files from my encrypted HDD to my USB thumb drive, and transferring
these files to my PC at home. It is quite common for me to bring Access
applications home to work on, because it's just too noisy in cubical land.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Tom,

Thanks for the response, but I do not want someone to be able to take the
mdb file outside the office, and be able to read it.. So if that user was
planning on leaving the company but wanted to get the info from the db, then
copies it to a flash drive.. I don't want that to work..

So I think EFS would work.. ?

Thanks

 

[Guest]

Thanks for the response, but I do not want someone to be able to take the

mdb file outside the office, and be able to read it.

Then you have a case for using SQL Server, Oracle or another true
client-server database. If you give a person permission to access a JET
database, they have all the permissions they need to copy the database.

So I think EFS would work.. ?

I don't think so, but why don't you try it out for yourself? As I indicated
EFS will only prevent unauthorized access to a HDD. If the person involved is
still an employee at the time, and has a valid log-on, then they're in. You
can (and should) place the back-end (BE) data file on a shared drive, where
only those with a need-to-know have the permissions necessary to access this
folder.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Thanks,

That was my fear...

Then you have a case for using SQL Server, Oracle or another true
client-server database. If you give a person permission to access a JET
database, they have all the permissions they need to copy the database.


I don't think so, but why don't you try it out for yourself? As I indicated
EFS will only prevent unauthorized access to a HDD. If the person involved is
still an employee at the time, and has a valid log-on, then they're in. You
can (and should) place the back-end (BE) data file on a shared drive, where
only those with a need-to-know have the permissions necessary to access this
folder.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

One thing that you might consider is locking down the Windows permissions on
the PC, so that people are not allowed to copy files to any type of external
storage (floppy, USB thumb drive, CD, etc.). You'd also have to limit the
ability to send a file by e-mail. Probably a lot more hassle than it's worth.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

yeah that wouldn't work with our buisness plus like you said more hassle then
worth.. Since we use usb drives all the time in our biz

 

[aaron.kempf]

use SQL Server

MDB is a security nightmare; not as bad as spreadsheets-- but still a
threat.

MDB has been obsolete for a decade. Lose the training wheels. Use
Access Data Projects

 

[aaron.kempf]

ADP is friggin easy dude

give end users the run time so that they can't even export to Excel

-Aaron

 

[aaron.kempf]

ADP development is _EASIER_ than MDB development

I am sorry that you had some retard senile develop mission-critical
apps for you.
You should have known better; MDB has been obsolete for a decade.

Spit on anyone that tells you otherwise.

-Aaron

 

[aaron.kempf]

just use SQL Server you ****ing retard

Access Data Projects allow for an awesome, secure solution.

MDB is impossible to secure in any way, shape or form

-Aaron