The best options are probably: Security subroutines and named common switches (this was covered at U2U under "Data Security and Best Practises"
Use wIntegrate thin client (more flexible and secure for this than the thick client) and log from the wIntegrate server using wIntegrate scripting. Are you sure you really want to do this ? If you implement this type of logging it is fairly easy to take down the service by filling your file system - a DOS attack. I"ve seen different opinions from different "compliance" officers before. There has been some fairly inventive interpretation of guidelines and items that should be assessed as risks as being rules on what must be done. If you are going to log everything, then you should perform a risk assessment on how this exposes you. Remember that the logs themselves are a Data Protection time bomb and you will probably want to encrypt them securely and audit who can access and use the logs. Regards JayJay Sent from my iPad On 24 Apr 2013, at 21:34, Scott Zachary <szach...@gardensalive.com> wrote: > For PCI compliance, we are tasked to log/capture all TCL entries and > responses. I am familiar with COMO, which is one possible solution. > > 1) What other TCL logging methods are available in UniVerse besides COMO? > > 2) What AIX Unix tools are available to capture keyboard input and responses > at TCL? > > > > -- > View this message in context: > http://u2-universe-unidata.1073795.n5.nabble.com/TCL-input-and-response-logging-such-as-COMO-tp40528.html > Sent from the U2 - Users mailing list archive at Nabble.com. > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
