SECURITY CONCERT - BACKUP

I am trying to find a way to limit the ability for employees with limited access to the backup function.

Is the Administrator password necessary when restoring a file, or can any employee do a restore?

Reply to
Rick Cassel
Loading thread data ...

Look in your version of QB help for information on backup. In the version I use, QB 2003 contractor, you *CAN* set a password that will be required to backup the file, so long as you are NOT on windows ME or windows 98.

Anyone can do a restore. Your options are to keep the remote media locked and under your control, and any copies on seperate HD's or computers in pw protected file folders.

Reply to
L

My concern is an employee burning a back to CD then taking off with the data.

Reply to
Rick Cassel

As I posted. You *CAN* put a pw on the backup command.

It will not protect you from employee theft, however.

The QB file can just as easily be copied as backed up. If the employee copies the QB file folder, s/he has all the information s/he needs to re-create the file on another computer.

As others have pointed out - employee password changes are more common. Just google a bit and see how many folks post they are unable to get into their files after the bookkeeper was fired.

Reply to
L

Well, better worry about an employe FTPing the file off to his machine at home too. Once he's got the file there are plenty of places where he can get password crackers to get the admin password for the file. Not all are as "prove this is your file" as QB is either.

Better people skills are the much better data safety practice. Make sure your employees are gruntled.

Reply to
Golden California Girls

Rick,

Any employee that can run QB has access to the single QB file that stores all your data. All that is needed is a cheap USB flash drive and 30 seconds of unsupervised time. The type of security you require can only be found when you move up the software food chain to systems where only the accounting program has access to the data files and not the users.

Reply to
Allan Martin

They don't have to have the ability to actually RUN the program.... they need only access to any computer than can access the QB files.

Reply to
HeyBub

  1. Set up a new account for an offshore bank. Deposit a fictious 0,000 in it.
  2. Pick a trusted employee. A relative, if possible.
  3. Each month, write this employee a BIG bonus check (say, 00). Don't GIVE them the check. In fact, keep them completely in the dark.
  4. Wait.
  5. Someone will complain. As soon as they do, fire their skanky ass.

------- There exists file encryption software. The software encrypts/decrypts data back and forth, invisible to the user. A backup or a copy of the data files would then be useless to the thief.

-------- Files in NTFS record a "date last read/accessed." If that date differs from the date the file was created, you've got a leak.

Reply to
HeyBub

If the employee can run the program then they must also have full access to the folder on the server that contains the data file. If security is in place then employees that do not run the program should not have access to the folder and therefore would not be able to get their little grubby hands on it. In addition if security is in place then employees that have access to the QB folder would not leave their workstations unattended and open to evil doings by others.

Reply to
Allan Martin

We had this thread a few months back. It should be a firing offense to walk away from a logged in computer, absent a door lock.

Reply to
Golden California Girls

Off with their heads said the Golden California Girls.

Reply to
Allan Martin

Someone once approached Winston Churchill with the lament: "(political opponent so-and-so) died! Whatever shall we do?"

Churchill replied: "Cremate him. Scatter the ashes. Take no chances."

Reply to
HeyBub

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.