|
Janet, You appear to be headed in the right direction. In addition to the other feedback, things to consider: 1) Secure your exit programs from inside/outside tampering. Probably *USE authority on the executable objects and *EXCLUDE on the source and documentation. 2) Keep a handle on failed signon attempts. I don't believe FTP pays attention to QMAXSIGN; but limits attempts to five. Review your security audit logs and QHST (or QSYSMSG) for failures. If you are not using QSYSMSG, look into it and use it. 3) I suggest you keep exact details of what you are or are not doing internal and on a need-to-know basis. Regards, Jerry Jewel "Better living through fine code and hot coffee!" -----Original Message----- ...What other things should we look at to close any holes into our system that might occur with this setup?... ___________________________________________________________________________ Visit http://www.visto.com/info, your free web-based communications center. Visto.com. Life on the Dot. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.