|
There's the Service Tools sign on. We have more than one QSECOFR for different purposes.Even if you had a different one for each person authorized to do the stuff, a person with that authority can change the password on the others, or assign a new one. You could use DSPLOG data to track from which work station the QSECOFR signed on, and who has access to that work station.
However, when we have certain kinds of downage ... a work station is in the middle of something, we switch around which device has which designation, then recover the crashed job from a non crashed device. So you'd have to be able to track that activity also.
We have considered keeping it disabled and then enabling when we need to, but how would that impact a disaster recovery situation? Would you be able to log on as QSECOFR if no one else was around that could enable it first? Dave -----Original Message----- From: BLCDOM.GWIA.midrange-l@xxxxxxxxxxxx Sent: Thursday, February 23, 2006 2:22 PM To: midrange-l@xxxxxxxxxxxx; stenore@xxxxxxx Subject: Re: QSECOFR usage We address it with a program that changed the password for QSECOFR daily with a new one, the same program is the retrieve program which requires a help desk ticket to retrieve it (all custom created). works well and shuts down auditors, especially with the log file that contains who, what, when, where
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
