|
Dennis - <Rant>There is a SPECIAL place in HELL (if you believe in an afterlife) for Mr. Sarbanes and Mr. Oxley. This law was a typical knee-jerk reaction by our Congress to the egregious conduct of executives in a small number of U.S. companies, most notably Enron.
The SOX law was probably written by lobbyists for the accounting firms/consulting firms that do the audits, just like the new U.S. bankruptcy law was written by lobbyists for the banking/credit card industry...
</Rant> Recommendation:I'd suggest that you purchase a software package like the PowerLock suite of tools from PowerTech. This gives you the ability to secure and audit your system/data. We use them to secure our iSeries system in a SOX-compliant fashion (we passed the SOX audit earlier this year), and they works GREAT!
(I don't receive any kickbacks from PowerTech...I'm just a consultant working for a satisfied customer)
See: http://www.powertech.com/pt-solutions.htmlYou can call me if you like, and I'll have the system administrator here call you to discuss the pros and cons of using PowerLock...
Regards, Steve Landess Austin, Texas (512) 423-0935----- Original Message ----- From: "Denis Robitaille" <denis_robitaille@xxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx> Sent: Friday, November 04, 2005 4:06 PM 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 --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.
midrange.com
