Revision Summary Date Revision History Revision Class Comments 3/2/2007 1.0 Major Updated and revised the technical content. 4/3/2007 1.1 Clarified the meaning of the technical content. 5/11/2007 2.0 Major New format 6/1/2007 2.0.1 Editorial Changed language and formatting in the technical content. 7/3/2007 3.0 Major Added normative references; updated technical content. 8/10/2007 4.0 Major Updated and revised the technical content. 9/28/2007 4.0.1 Editorial Changed language and formatting in the technical content. 10/23/2007 4.0.2 Editorial Changed language and formatting in the technical content. 1/25/2008 4.0.3 Editorial Changed language and formatting in the technical content.
3/14/2008 4.0.4 Editorial Changed language and formatting in the technical content. 6/20/2008 5.0 Major Updated and revised the technical content. 7/25/2008 5.0.1 Editorial Changed language and formatting in the technical content. 8/29/2008 5.0.2 Editorial Changed language and formatting in the technical content. 10/24/2008 5.0.3 Editorial Changed language and formatting in the technical content. 12/5/2008 5.1 Minor Clarified the meaning of the technical content. 1/16/2009 5.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 5.1.2 Editorial Changed language and formatting in the technical content. 4/10/2009 5.1.3 Editorial Changed language
and formatting in the technical content. 5/22/2009 6.0 Major Updated and revised the technical content. 7/2/2009 6.1 Minor Clarified the meaning of the technical content. 8/14/2009 6.1.1 Editorial Changed language and formatting in the technical content. 9/25/2009 6.2 Minor Clarified the meaning of the technical content. 11/6/2009 6.3 Minor Clarified the meaning of the technical content. 12/18/2009 6.3.1 Editorial Changed language and formatting in the technical content. 1/29/2010 6.4 Clarified the meaning of the technical content. 3/12/2010 7.0 Major Updated and revised the technical content. 4/23/2010 7.0.1 Editorial Changed language and formatting
in the technical content. 6/4/2010 7.0.2 Editorial Changed language and formatting in the technical content. 7/16/2010 8.0 Major Updated and revised the technical content. 8/27/2010 9.0 Updated and revised the technical content. 10/8/2010 10.0 Major Updated and revised the technical content. 11/19/2010 11.0 Major Updated and revised the technical content. 1/7/2011 11.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 12.0 Major Updated and revised the technical content. 3/25/2011 13.0 Major Updated and revised the technical content. 5/6/2011 14.0 Major Updated and revised the
technical content. 6/17/2011 15.0 Major Updated and revised the technical content. 9/23/2011 15.0 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 16.0 Updated and revised the technical content. 3/30/2012 16.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 16.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 16.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 16.0 None No changes to the meaning, language, or formatting of the
technical content. 8/8/2013 17.0 Major Updated and revised the technical content. 11/14/2013 18.0 Major Updated and revised the technical content. 2/13/2014 19.0 Major Updated and revised the technical content. 5/15/2014 19.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 20.0 Major Significantly changed the technical content. 10/16/2015 20.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 20.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 20.0 None No changes to the meaning, language, or
only failures, both successes and failures, or to not audit these events at all (that is, neither successes nor failures). If Success auditing is enabled, an audit entry MUST be logged each time any user successfully accesses an Active Directory object that has a matching SACL specified. If Failure auditing is enabled, an audit entry MUST be logged each time any user unsuccessfully attempts to access an Active Directory object that has a matching SACL specified. AuditAccountLogon A security setting that determines whether the operating system MUST audit each time this computer validates the credentials of an account. Account logon events are generated whenever a computer validates the credentials of one of its local accounts. The credential validation can be in support of a local logon, or in the case of an Active Directory account on a , can be in support of a logon to another computer. Audited events for local accounts MUST be logged on the local security log
Index A Abstract data model 29 31 15 Administrative 29 higher-layer triggered events 29 29 30 message processing 30 30 29 30 29 sequencing rules 30 30 29 30 30 29 11 17 48 B 9 C 11 53 Client 31 31 31 47 message processing 34 event 40 40 45 46 39 36 32 33 42 registry 42 41 43 47 31 sequencing 34 40 40 45 46 39 36 32 33 42 registry 42 41 43 47 47 31 26 26 D Data model - abstract 29 31 E 27 27 28 18 18 17 17 48 9 F 11 24 24 25 G 6 Group membership ( 24, 48) 24 H Higher-layer triggered events administrative 29 31 I
50 50 9 Initialization 29 31 6 K 16 16 22 L 16 Local events 30 47 M Membership - group ( 24, 48) Message processing administrative 30 30 29 30 client 34 event 40 40 45 46 39 36 32 33 42 registry 42 41 43 47 Messages 18 17 24 24 16 21 22 21 23 12 13 12 25 N 8 O 9 P Parameters - security 50 50 50 Password policies ( 13, 48) Policies 15 17 18 17 16 16 password ( 13, 48) 17 17 10 10 21 21 51 28 R 8 9 8 Registry 22 21 22 21 10 21 S Security 9 24 50 50 17 Sequencing rules administrative 30 30 29 30 client 34 event 40 40 45 46 39 36