Re: Sign on/security logging

      Hello David,
      If that works for you.  What is the action you are taking when
invalid sigh on attempts.  We disable the ID and very off the device they
are using.  We also require a number in the password and it must be at
least 8 characters long.  This causes a number of calls to the command
center when they are forced to change their passwords every 45 days, but I
don't have to take the calls.  Having thousands of users spread across the
US and the Caribbean is such fun.
   Julio


                                                                                
                                     
                      "David Morris"                                            
                                     
                      <David.Morris@plumcre        To:       
<security400@xxxxxxxxxxxx>                              
                      ek.com>                      cc:                          
                                     
                      Sent by:                     Subject:  Re: [Security400] 
Sign on/security logging              
                      security400-bounces@m                                     
                                     
                      idrange.com                                               
                                     
                                                                                
                                     
                                                                                
                                     
                      08/03/2004 03:44 PM                                       
                                     
                      Please respond to                                         
                                     
                      Security                                                  
                                     
                      Administration on the                                     
                                     
                      AS400 / iSeries                                           
                                     
                                                                                
                                     
                                                                                
                                     




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?
_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400)
mailing list
To post a message email: Security400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.