|
Denis, PowerLock NetworkSecurity has a facility in it you may be able to utilize. Within NetworkSecurity there is a facility call Generic Exit point. I don't want to give a sales pitch so won't go into the details of how to use it. I will say this exit point can be utilized by your stored procedures or green screen apps to gain the full power NetworkSecurity offers. If you are interested you can contact us by going to our web site www.powertech.com or call 800-915-7700. Gary Monnier | Senior Software Developer 19426 68th Ave. S Kent, WA 98032 (253) 872-7788 ext. 308 gary.monnier@xxxxxxxxxxxxx www.powertech.com This email message and any attachments are intended only for the use of the intended recipient named above and may contain information that is privileged and confidential. If you are not the intended recipient, any dissemination, distribution, or copying is strictly prohibited. If you received this email message in error, please immediately notify the sender by replying to this email message or by telephone and delete the message from your email system. Thank you. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Denis Robitaille Sent: Friday, November 04, 2005 2:06 PM To: midrange-l@xxxxxxxxxxxx Subject: security vs sox question Hello all, As many of you, we are going trough the process to get certified for Sarbane oxley. Our setup is ok for "green screen" program. We use adopted autority so that, by themselve, the user do not have access to any files but the programs do. This way, our data can only be modified from our written and approved programs (no DFU or client access upload or dynamic SQL ...). But I wonder how to properly secure access for VB, Java, c# or any client/server programs that do not run on the Iseries. Since those program do not run on the Iseries, we can not use adopted autority. So we must grant more right to the user profil. But i we do so, we can not stop a user from using any program on his PC to access the data on the Iseries. I checked and the ODBC exit program can not know the name of the program that uses the connection, thus I can not validate the program that way. On the information center, they proposed the use of stored procedure with adopted autority. But what is stoping a user from calling those stored procedure from a home made program? We are looking at the use of swapp profile to increase security, but this is complex and not bullet proof. I am looking to hear from other as to how they handle that need of securing/controling access to Iseries data in client/server mode. Thanks in advance. Denis Robitaille Directeur services technique TI 819 363 6130 SUPPORT Jour (EST) Daytime : 819-363-6134 En-dehors des heures (EST) After hour : 819-363-6158 Network Status : 819-363-6157
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.