Re: Database security from PC applications.

[Patrick Botz <pcbotz@xxxxxxxxx>]

My experience with implementing these types of changes is that NO 
application changes are necessary.
Administrators can do the required changes themselves.

Patrick Botz
President, Botz&  Associates, Inc.
Home/Office: 1-507-319 5206
Mobile     : 1-507-250-5644
mailto:pcbotz@xxxxxxxxx

___________________________

CONFIDENTIALITY NOTICE: This email message and any attachment to this email message contain information that may be privileged and confidential. This email and any attachments are intended solely for the use of the individual or entity named above (the recipient) and may not be forwarded to or shared with any third party. If you are not the intended recipient and have received this email in error, please notify us by return e-mail or by telephone at 507-285-9048 and delete this message. This notice is automatically appended to each email message leaving Botz&  Associates, Inc. Thank You.


On 12/9/2010 3:46 PM, Alan Campin wrote:
> I have been recently tasked with looking into users making changes to our
> AS/400 tables from PC applications and how to prevent this.
>
> I seem to recall that there might have been some discussions of this in the
> past.
>
> I know that the usual way to do something like this is to create all
> database tables with a db owner and exclude *PUBLIC from any access. Then
> when the user starts a program the system grants them access to the
> application for the duration of the session and when the session ends the
> authority is revoked.
>
> The problem is that requires everything to be set up that way and major
> application work which they are not willing to do given the AS/400 is toast
> in a year.
>
> Any other ways people have accomplished this? I believe there is a database
> exit program. Any other ideas?
>
> Thanks for any help.