|
Any one who has *allobj or *secadm or *secofr should have full auditing turned on. There for any thing they do is captured in the QAUDJRN. You should perform regular audits to make sure they do not disable auditing on their accounts. Best is to create a user with full authority to audit journals, yet no other authority on the system. This persons job is to audit your security officers, and the rest of the folks. You then give private authority of *exclude on the journal and receiver libraries for all of your security folks. All this is over and above the stuff Patrick mentioned. Security is two parts, part 1 control access, part 2 audit access. Control and Audit should be two different people. Chris Bipes Information Services Director CrossCheck, Inc. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Patrick Botz Sent: Thursday, November 17, 2005 2:35 PM To: Midrange Systems Technical Discussion Subject: Re: QAUDJRN Dave, You can also prevent *ALLOBJ/security officers from being able to change security related system values. In V5R2, as long as you control the service tools userIDs and the privileges that the other folks have, you can lock down security related system values using SST. You would also want to prevent service tools userIDs with a default password from being changed/logged into (another option in the service tools security menu). Doing so will prevent any *ALLOBJ user profile from being able to change your security related system values. It also prevents 3rd party applications from changing them "under the covers" during an install/upgrade. By using this AND using the audit journal, you can prevent others from changing security related system values and also track who is changing other non-security related system values.
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.