Re: Restricting ODBC access

John H. Frantz wrote: > Someone once mentioned making the role name a secret, i.e. the name of > the role itself becomes a sort of password which would be built into the > applications. Does this not work? > Sure, Only it will come back to haunt you, and still, even though its *sekret*, it doesn't really solve the problem. First, it could get *lost* meaning that over time your development team changes, and well, things are not always documented..... But while this is really minor, the exact oposite may occur. Developers have to know the role, and that role may be used by several different applications. So while you may limit the audience, you still have a threat of a disgruntled employee or someone going after different data that he or she is not normally allowed to see. By going to a three tier arch. you can limit direct access to your production data. You limit the access to the servers, you limit access to your app servers (if they are not the same machine.) Data is now more secure. Does it solve all the problems? No. But it reduces the threat risk. -Don't mind me, I'm paid to be paranoid. Mikey