Having worked in catalog sales we used to spike our lists with fictional names using address's of co-worker before loaning/renting out the lists for limited use. Everytime a piece of mail was r'cvd for that name, the co-worker would simply bring it in for the list manager and he'd double check to make sure that our list was being used by authorized person's only. Or that our outsourced list broker was properly compensating us.
I like the idea of taking this old technique and updating it for data access. The one drawback is how will you know if the person actually accessed the file maliciously or by mistake? Database endusers sometimes need to browse records to verify and compare information.
Slashdot Mirror
Having worked in catalog sales we used to spike our lists with fictional names using address's of co-worker before loaning/renting out the lists for limited use. Everytime a piece of mail was r'cvd for that name, the co-worker would simply bring it in for the list manager and he'd double check to make sure that our list was being used by authorized person's only. Or that our outsourced list broker was properly compensating us. I like the idea of taking this old technique and updating it for data access. The one drawback is how will you know if the person actually accessed the file maliciously or by mistake? Database endusers sometimes need to browse records to verify and compare information.