Hi Julio, I should have said that we are auditing and depending on the interface I see some PW or GR entries but it appears that quite a few other ways exist to validate a password that do not produce audit entries. What I am looking for is the most complete solution. On the surface, using the invalid sign on attempt count on a profile seems complete as long as the person that is fishing for a password doesn't have *ALLOBJ authority. David Morris >>> Julio_Domingo@xxxxxxxxxxxxx 8/3/2004 2:31:11 PM >>> You can turn on security logging by changing the system values: QAUDCTL Auditing control QAUDENDACN Auditing end action QAUDFRCLVL Force auditing data QAUDLVL Security auditing level You can then print reports from the information produced. The only way that the user profile would not increment would be if profile was deleted and recreated. Julio Domingo "David Morris" <David.Morris@plumcre To: <security400@xxxxxxxxxxxx> Is there any way to system auditing to detect all invalid sign on attempts? The only way I can come up with is to look at the invalid sign on attempts a profile. Would that cover all cases or is it possible for an invalid sign on to not increment the invalid sign on attempts count?
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.