]
Subject: RE: Secure Database Design Part II
Hi
Firstly if your application is well designed then your data should not be accessible
by the wrong users - if you make sure that there is no way the wrong supplier id can
be allocated - put an extra 'are you sure this is correct' check, make it so
Design Part II
Hi Steven,
I believe I understand your concerns. I think the only way to reduce the risk
of associating the wrong data is tripple checking it by different persons or
even better make two tables which you can compare against each other. The
second table only readable to you
Hey folks -
Thanks to everyone who gave input to my concerns. Of course, we don't intend
to have the mysql port open to the world. We will have Apache/PHP connect on
a unix socket, or to another machine with a cross-cable on non-routeable
IPs.
But now I have another question. We are working on
Hi Steven,
I believe I understand your concerns. I think the only way to reduce the risk
of associating the wrong data is tripple checking it by different persons or
even better make two tables which you can compare against each other. The
second table only readable to you. This way you could
