|
Tom Liotta wrote on 06/29/2006 02:45:13 PM:
Nevertheless, this is fairly a novel idea and is well worth being made known to everyone. It clearly demonstrates that proper precautions must be taken. It provides a textbook example of why, for example, debug access to production tasks is a serious issue. The discussion illustrates for everyone who is learning from this list why the related precautionary guidelines exist.
I agree. I will add that one of those precautions might be to turn on *SERVICE auditing in the QAUDLVL or QAUDLVL2 system value. This will cause an ST audit record to be written to the security audit journal when some service or debugging tools are used. The Char(2) Service Tool field in this audit record indicates which service or debugging tool was used. The value "SJ" stands for STRSRVJOB. The complete list of the values for the Service Tool field can be found in the description of the ST audit record in Appendix F of the Security Reference manual. Ed Fishel, edfishel@xxxxxxxxxx
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.