From what I have read about security, it is pretty easy to have a missing security scheme. Years ago database security was simpler. Just keep the disks the database is on in a locked cabinet. If the database was too big then the database is stored in a room called a glass house. No one but authorized persons were allowed in the room. Business became dependant on this data and it became the administrator�s job to secure the database. This is where authentication when connecting to a server became important. I know in my organization we had customers calling in for months updating their credit cards because a bunch of American Express cards were recalled because of a security breach (not in our company thank goodness.) In my company the results of a security breach is a bit vague though, it is usually referenced with men with guns and undefined jail or prison sentences. As for how difficult it would be to recover from having the data breached, I think it really comes down to the extent of the breach and if it was malicious or not. A breach would mean a work stoppage for me, definitely, and my computer would have to be re-imaged. If it went to outside sources though, it would mean notifying the authorities and a possible loss of service level agreements (SLA�s) that we have set with our customers. That could mean millions. If we lost the contract with enough of these events were looking at billions of dollars. Just something to keep in mind I guess when designing a schema.