How Reliably Is the Data in a Multiple Client System Isolated?
To guarantee exclusive access to the data of a client, you need to take extra data access logic precautions as well as categorizing the data correctly. A customer who logs on to his or her client in the system must have all activities restricted to his or her customer data, and be denied access to the data of other clients (the customer must be under the impression that the entire database is only open to him or her). Data isolation is guaranteed if each time you access client-specific tables, you are implicitly restricted to the active logon client within the database interface, and unable to manipulate this access from the application program level or at runtime. Four questions arise from this: • Question 1: Is there a way to prevent the implicit selection of clients? The logic of the database interface is a piece of fixed code and cannot be accessed from outside. Dynamic client selection is triggered only by the table attribute client-specific table, which is a fixed attribute of th
