Mini Kabibi Habibi

Current Path : C:/Windows/System32/en-US/

Current File : C:/Windows/System32/en-US/auditpolmsg.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!v

�]r@ ,r8.rdata�@@.rsrc� t@@x��
T88x��$��8.rdata8x.rdata$zzzdbg �.rsrc$01�(�.rsrc$02 ���7�N���B>K����u���n���Vtx����(�@�0�H�`�x��� ��
����
��� �8�P�h��� ��&��'��(��)��*�+(�,@�-X�.p�/��0��1��2��4��� ( 8 H X h x � � � � � � � � ( 8 H X h x � � � � � � �&���&��L'�d)�|*@��+���-��|.@��/"��0���2��3J�45J��6f��6���7�"��Z�
��hr<��F"�H�T ���6�����d��
�H�f����H�%�<�.��j<�4~.�d���MUI������Qo���5��׾ �4g[۴�e�Ŀ��~���MUIen-USSuccessFailureSuccess and FailureNo AuditingNot ConfiguredAudit PoliciesSystem Audit PoliciesAccount ManagementAudit User Account Management!Audit Computer Account ManagementAudit Security Group Management#Audit Distribution Group Management"Audit Application Group Management%Audit Other Account Management EventsLogon/LogoffAudit LogonAudit LogoffAudit Account LockoutAudit IPsec Main ModeAudit IPsec Quick ModeAudit IPsec Extended ModeAudit Special LogonAudit Other Logon/Logoff EventsAudit Network Policy ServerAudit User / Device ClaimsAudit Group MembershipAudit Access Rights
Policy ChangeAudit Audit Policy Change"Audit Authentication Policy Change!Audit Authorization Policy Change%Audit MPSSVC Rule-Level Policy Change&Audit Filtering Platform Policy Change Audit Other Policy Change Events
Privilege UseAudit Sensitive Privilege Use!Audit Non Sensitive Privilege Use Audit Other Privilege Use EventsPADetailed TrackingAudit Process CreationAudit Process TerminationAudit DPAPI ActivityAudit RPC EventsAudit PNP ActivityAudit Token Right AdjustedSystemAudit Security State ChangeAudit Security System ExtensionAudit System IntegrityAudit IPsec DriverAudit Other System EventsPA
Object AccessAudit File SystemAudit RegistryAudit Kernel Object Audit SAMAudit Certification ServicesAudit Application GeneratedAudit Handle ManipulationAudit File Share$Audit Filtering Platform Packet Drop#Audit Filtering Platform ConnectionPA Audit Other Object Access EventsAudit Detailed File ShareAudit Removable Storage#Audit Central Access Policy StagingPA DS AccessAudit Directory Service AccessAudit Directory Service Changes#Audit Directory Service Replication,Audit Detailed Directory Service ReplicationPA
Account LogonAudit Credential Validation(Audit Kerberos Service Ticket Operations Audit Other Account Logon Events%Audit Kerberos Authentication ServicePA#Advanced Audit Policy ConfigurationPAAdvanced Audit ConfigurationMicrosoft Corporation.Configure granular audit policies for Windows.1.0lUser Account Management

This policy setting allows you to audit changes to user accounts. Events include the following:

A user account is created, changed, deleted; renamed, disabled, enabled, locked out, or unlocked.

A user account s password is set or changed.

A security identifier (SID) is added to the SID History of a user account.

The Directory Services Restore Mode password is configured.

Permissions on administrative user accounts are changed.

Credential Manager credentials are backed up or restored.

If you configure this policy setting, an audit event is generated when an attempt to change a user account is made. Success audits record successful attempts and Failure audits record unsuccessful attempts. If you do not configure this policy setting, no audit event is generated when a user account changes.

Volume: Low.

Default: Success.]Computer Account Management

This policy setting allows you to audit events generated by changes to computer accounts such as when a computer account is created, changed, or deleted.

If you configure this policy setting, an audit event is generated when an attempt to change a computer account is made. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a computer account changes.

Volume: Low.

Default on Client editions: No Auditing.

Default on Server editions: Success.kSecurity Group Management

This policy setting allows you to audit events generated by changes to security groups such as the following:

Security group is created, changed, or deleted.

Member is added or removed from a security group.

Group type is changed.

If you configure this policy setting, an audit event is generated when an attempt to change a security group is made. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a security group changes.

Volume: Low.

Default: Success.�Distribution Group Management

This policy setting allows you to audit events generated by changes to distribution groups such as the following:

Distribution group is created, changed, or deleted.

Member is added or removed from a distribution group.

Distribution group type is changed.

If you configure this policy setting, an audit event is generated when an attempt to change a distribution group is made. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a distribution group changes.

Note: Events in this subcategory are logged only on domain controllers.

Volume: Low.

Default: No Auditing.kApplication Group Management

This policy setting allows you to audit events generated by changes to application groups such as the following:

Application group is created, changed, or deleted.

Member is added or removed from an application group.

If you configure this policy setting, an audit event is generated when an attempt to change an application group is made. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when an application group changes.

Volume: Low.

Default: No Auditing.�Other Account Management Events

This policy setting allows you to audit events generated by other user account changes that are not covered in this category, such as the following:

The password hash of a user account was accessed. This typically happens during an Active Directory Management Tool password migration.

The Password Policy Checking API was called. Calls to this function can be part of an attack when a malicious application tests the policy to reduce the number of attempts during a password dictionary attack.

Changes to the Default Domain Group Policy under the following Group Policy paths:

Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy

Computer Configuration\Windows Settings\Security Settings\Account Policies\Account Lockout Policy

Note: The security audit event is logged when the policy setting is applied. It does not occur at the time when the settings are modified.

Volume: Low.

Default: No Auditing.PA_Audit Logon

This policy setting allows you to audit events generated by user account logon attempts on the computer.

Events in this subcategory are related to the creation of logon sessions and occur on the computer which was accessed. For an interactive logon, the security audit event is generated on the computer that the user account logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource. The following events are included:

Successful logon attempts.

Failed logon attempts.

Logon attempts using explicit credentials. This event is generated when a process attempts to log on an account by explicitly specifying that account s credentials. This most commonly occurs in batch logon configurations, such as scheduled tasks or when using the RUNAS command.

Security identifiers (SIDs) were filtered and not allowed to log on.

Volume: Low on a client computer. Medium on a domain controller or a network server

Default on Client editions: Success.

Default on Server editions: Success, Failure.�Logoff

This policy setting allows you to audit events generated by the closing of a logon session. These events occur on the computer that was accessed. For an interactive logoff the security audit event is generated on the computer that the user account logged on to.

If you configure this policy setting, an audit event is generated when a logon session is closed. Success audits record successful attempts to close sessions and Failure audits record unsuccessful attempts to close sessions.

If you do not configure this policy setting, no audit event is generated when a logon session is closed.

Volume: Low.

Default: Success.PA�Account Lockout

This policy setting allows you to audit events generated by a failed attempt to log on to an account that is locked out.

If you configure this policy setting, an audit event is generated when an account cannot log on to a computer because the account is locked out. Success audits record successful attempts and Failure audits record unsuccessful attempts.

Logon events are essential for understanding user activity and to detect potential attacks.

Volume: Low.

Default: Success.!IPsec Main Mode

This policy setting allows you to audit events generated by Internet Key Exchange protocol (IKE) and Authenticated Internet Protocol (AuthIP) during Main Mode negotiations.

If you configure this policy setting, an audit event is generated during an IPsec Main Mode negotiation. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated during an IPsec Main Mode negotiation.

Volume: High.

Default: No Auditing.%IPsec Quick Mode

This policy setting allows you to audit events generated by Internet Key Exchange protocol (IKE) and Authenticated Internet Protocol (AuthIP) during Quick Mode negotiations.

If you configure this policy setting, an audit event is generated during an IPsec Quick Mode negotiation. Success audits record successful attempts and Failure audits record unsuccessful attempts.If

you do not configure this policy setting, no audit event is generated during an IPsec Quick Mode negotiation.

Volume: High.

Default: No Auditing.1IPsec Extended Mode

This policy setting allows you to audit events generated by Internet Key Exchange protocol (IKE) and Authenticated Internet Protocol (AuthIP) during Extended Mode negotiations.

If you configure this policy setting, an audit event is generated during an IPsec Extended Mode negotiation. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated during an IPsec Extended Mode negotiation.

Volume: High.

Default: No Auditing.Special Logon

This policy setting allows you to audit events generated by special logons such as the following :

The use of a special logon, which is a logon that has administrator-equivalent privileges and can be used to elevate a process to a higher level.

A logon by a member of a Special Group. Special Groups enable you to audit events generated when a member of a certain group has logged on to your network. You can configure a list of group security identifiers (SIDs) in the registry. If any of those SIDs are added to a token during logon and the subcategory is enabled, an event is logged. For more information about this feature, see article 947223 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=121697).

Volume: Low.

Default: Success.�Other Logon/Logoff Events

This policy setting allows you to audit other logon/logoff-related events that are not covered in the Logon/Logoff policy setting such as the following:

Terminal Services session disconnections.

New Terminal Services sessions.

Locking and unlocking a workstation.

Invoking a screen saver.

Dismissal of a screen saver.

Detection of a Kerberos replay attack, in which a Kerberos request was received twice with identical information. This condition could be caused by network misconfiguration.

Access to a wireless network granted to a user or computer account.

Access to a wired 802.1x network granted to a user or computer account.

Volume: Low.

Default: No Auditing.�Network Policy Server

This policy setting allows you to audit events generated by RADIUS (IAS) and Network Access Protection (NAP) user access requests. These requests can be Grant, Deny, Discard, Quarantine, Lock, and Unlock.

If you configure this policy setting, an audit event is generated for each IAS and NAP user access request. Success audits record successful user access requests and Failure audits record unsuccessful attempts.

If you do not configure this policy settings, IAS and NAP user access requests are not audited.

Volume: Medium or High on NPS and IAS server. No volume on other computers.

Default: Success, Failure.User / Device Claims

This policy allows you to audit user and device claims information in the user's logon token. Events in this subcategory are generated on the computer on which a logon session is created. For an interactive logon, the security audit event is generated on the computer that the user logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.

User claims are added to a logon token when claims are included with a user's account attributes in Active Directory. Device claims are added to the logon token when claims are included with a device's computer account attributes in Active Directory. In addition, compound identity must be enabled for the domain and on the computer where the user logged on.

When this setting is configured, one or more security audit events are generated for each successful logon. You must also enable the Audit Logon setting under Advanced Audit Policy Configuration\System Audit Policies\Logon/Logoff. Multiple events are generated if the user and device claims information cannot fit in a single security audit event.

Volume: Low on a client computer. Medium on a domain controller or a network server

Default: No Auditing.�Group Membership

This policy allows you to audit the group memberships information in the user's logon token. Events in this subcategory are generated on the computer on which a logon session is created. For an interactive logon, the security audit event is generated on the computer that the user logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.

When this setting is configured, one or more security audit events are generated for each successful logon. You must also enable the Audit Logon setting under Advanced Audit Policy Configuration\System Audit Policies\Logon/Logoff. Multiple events are generated if the group membership information cannot fit in a single security audit event.

Volume: Low on a client computer. Medium on a domain controller or a network server

Default: No Auditing.�Access Rights

This policy allows you to audit system access right enforcement details during account logon. Events in this subcategory are generated on the computer on which account logons are performed. For an interactive logon, the security audit event is generated on the computer that the user logged on to. For a network logon, such as accessing a shared folder on the network, the security audit event is generated on the computer hosting the resource.

When this setting is configured for Success audits, one or more security audit events are generated for each successful logon. When this setting is configured for Failure audits, one or more security audit events are generated for explicitly denied logons.

When this setting is configured for Failure audits, no security audit events will be generated for implicitly denied logons.

You must also enable the Audit Logon setting under Advanced Audit Policy Configuration\System Audit Policies\Logon/Logoff. Multiple events are generated if the access right information cannot fit in a single security audit event.

Volume: Low on a client computer. Medium on a domain controller or a network server

Default: No Auditing.PA�Audit Policy Change

This policy setting allows you to audit changes in the security audit policy settings such as the following:

Settings permissions and audit settings on the Audit Policy object.

Changes to the system audit policy.

Registration of security event sources.

De-registration of security event sources.

Changes to the per-user audit settings.

Changes to the value of CrashOnAuditFail.

Changes to the system access control list on a file system or registry object.

Changes to the Special Groups list.

Note: System access control list (SACL) change auditing is done when a SACL for an object changes and the policy change category is enabled. Discretionary access control list (DACL) and ownership changes are audited when object access auditing is enabled and the object's SACL is configured for auditing of DACL/Owner change.

If you configure this policy setting, an audit event is generated when a remote RPC connection is attempted. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a remote RPC connection is attempted.

Volume: Low.

Default: Success.�Authentication Policy Change

This policy setting allows you to audit events generated by changes to the authentication policy such as the following:

Creation of forest and domain trusts.

Modification of forest and domain trusts.

Removal of forest and domain trusts.

Changes to Kerberos policy under Computer Configuration\Windows Settings\Security Settings\Account Policies\Kerberos Policy.

Granting of any of the following user rights to a user or group:

Access This Computer From the Network.

Allow Logon Locally.

Allow Logon Through Terminal Services.

Logon as a Batch Job.

Logon a Service.

Namespace collision. For example, when a new trust has the same name as an existing namespace name.

If you configure this policy setting, an audit event is generated when an attempt to change the authentication policy is made. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when the authentication policy is changed.

Note: The security audit event is logged when the group policy is applied. It does not occur at the time when the settings are modified.

Volume: Low.

Default: Success.�Authorization Policy Change

This policy setting allows you to audit events generated by changes to the authorization policy such as the following:

Assignment of user rights (privileges), such as SeCreateTokenPrivilege, that are not audited through the Authentication Policy Change subcategory.

Removal of user rights (privileges), such as SeCreateTokenPrivilege, that are not audited through the Authentication Policy Change subcategory.

Changes in the Encrypted File System (EFS) policy.

Changes to the Resource attributes of an object.

Changes to the Central Access Policy (CAP) applied to an object.

If you configure this policy setting, an audit event is generated when an attempt to change the authorization policy is made. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when the authorization policy changes.

Volume: Low.

Default: No Auditing.�MPSSVC Rule-Level Policy Change

This policy setting allows you to audit events generated by changes in policy rules used by the Microsoft Protection Service (MPSSVC). This service is used by Windows Firewall. Events include the following:

Reporting of active policies when Windows Firewall service starts.

Changes to Windows Firewall rules.

Changes to Windows Firewall exception list.

Changes to Windows Firewall settings.

Rules ignored or not applied by Windows Firewall Service.

Changes to Windows Firewall Group Policy settings.

If you configure this policy setting, an audit event is generated by attempts to change policy rules used by the MPSSVC. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated by changes in policy rules used by the MPSSVC.

Volume: Low.

Default: No Auditing.PA�Filtering Platform Policy Change

This policy setting allows you to audit events generated by changes to the Windows Filtering Platform (WFP) such as the following:

IPsec services status.

Changes to IPsec policy settings.

Changes to Windows Firewall policy settings.

Changes to WFP providers and engine.

If you configure this policy setting, an audit event is generated when a change to the WFP is attempted. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a change occurs to the WFP.

Volume: Low.

Default: No Auditing.Other Policy Change Events

This policy setting allows you to audit events generated by other security policy changes that are not audited in the policy change category, such as the following:

Trusted Platform Module (TPM) configuration changes.

Kernel-mode cryptographic self tests.

Cryptographic provider operations.

Cryptographic context operations or modifications.

Applied Central Access Policies (CAPs) changes.

Boot Configuration Data (BCD) modifications.

Volume: Low.

Default: No Auditing.#Sensitive Privilege Use

This policy setting allows you to audit events generated when sensitive privileges (user rights) are used such as the following:

A privileged service is called.

One of the following privileges are called:

Act as part of the operating system.

Back up files and directories.

Create a token object.

Debug programs.

Enable computer and user accounts to be trusted for delegation.

Generate security audits.

Impersonate a client after authentication.

Load and unload device drivers.

Manage auditing and security log.

Modify firmware environment values.

Replace a process-level token.

Restore files and directories.

Take ownership of files or other objects.

If you configure this policy setting, an audit event is generated when sensitive privilege requests are made. Success audits record successful requests and Failure audits record unsuccessful requests.

If you do not configure this policy setting, no audit event is generated when sensitive privilege requests are made.

Volume: High.�Non Sensitive Privilege Use

This policy setting allows you to audit events generated by the use of non-sensitive privileges (user rights).

The following privileges are non-sensitive:

Access Credential Manager as a trusted caller.

Access this computer from the network.

Add workstations to domain.

Adjust memory quotas for a process.

Allow log on locally.

Allow log on through Terminal Services.

Bypass traverse checking.

Change the system time.

Create a pagefile.

Create global objects.

Create permanent shared objects.

Create symbolic links.

Deny access this computer from the network.

Deny log on as a batch job.

Deny log on as a service.

Deny log on locally.

Deny log on through Terminal Services.

Force shutdown from a remote system.

Increase a process working set.

Increase scheduling priority.

Lock pages in memory.

Log on as a batch job.

Log on as a service.

Modify an object label.

Perform volume maintenance tasks.

Profile single process.

Profile system performance.

Remove computer from docking station.

Shut down the system.

Synchronize directory service data.

If you configure this policy setting, an audit event is generated when a non-sensitive privilege is called. Success audits record successful calls and Failure audits record unsuccessful calls.

If you do not configure this policy setting, no audit event is generated when a non-sensitive privilege is called.

Volume: Very High. Not used.PAProcess Creation

This policy setting allows you to audit events generated when a process is created or starts. The name of the application or user that created the process is also audited.

If you configure this policy setting, an audit event is generated when a process is created. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a process is created.

Volume: Depends on how the computer is used.�Process Termination

This policy setting allows you to audit events generated when a process ends.

If you configure this policy setting, an audit event is generated when a process ends. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a process ends.

Volume: Depends on how the computer is used.�DPAPI Activity

This policy setting allows you to audit events generated when encryption or decryption requests are made to the Data Protection application interface (DPAPI). DPAPI is used to protect secret information such as stored password and key information. For more information about DPAPI, see https://go.microsoft.com/fwlink/?LinkId=121720.

If you configure this policy setting, an audit event is generated when an encryption or decryption request is made to DPAPI. Success audits record successful requests and Failure audits record unsuccessful requests.

If you do not configure this policy setting, no audit event is generated when an encryption or decryption request is made to DPAPI.

Volume: Low.�RPC Events

This policy setting allows you to audit inbound remote procedure call (RPC) connections.

If you configure this policy setting, an audit event is generated when a remote RPC connection is attempted. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a remote RPC connection is attempted.

Volume: High on RPC servers.�PNP Activity

This policy setting allows you to audit when plug and play detects an external device.

If you configure this policy setting, an audit event is generated whenever plug and play detects an external device. Only Success audits are recorded for this category.

If you do not configure this policy setting, no audit event is generated when an external device is detected by plug and play.

Volume: Low�Token Right Adjustment Event

This policy setting allows you to audit events generated by adjusting the privileges of a token.

Volume: High.

Default: No Auditing.PA�Security State Change

This policy setting allows you to audit events generated by changes in the security state of the computer such as the following events:

Startup and shutdown of the computer.

Change of system time.

Recovering the system from CrashOnAuditFail, which is logged after a system restarts when the security event log is full and the CrashOnAuditFail registry entry is configured.

Volume: Low.

Default: Success.�Security System Extension

This policy setting allows you to audit events related to security system extensions or services such as the following:

A security system extension, such as an authentication, notification, or security package is loaded and is registered with the Local Security Authority (LSA). It is used to authenticate logon attempts, submit logon requests, and any account or password changes. Examples of security system extensions are Kerberos and NTLM.

A service is installed and registered with the Service Control Manager. The audit log contains information about the service name, binary, type, start type, and service account.

If you configure this policy setting, an audit event is generated when an attempt is made to load a security system extension. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when an attempt is made to load a security system extension.

Volume: Low. Security system extension events are generated more often on a domain controller than on client computers or member servers.

Default: No Auditing.�System Integrity

This policy setting allows you to audit events that violate the integrity of the security subsystem, such as the following:

Events that could not be written to the event log because of a problem with the auditing system.

A process that uses a local procedure call (LPC) port that is not valid in an attempt to impersonate a client by replying, reading, or writing to or from a client address space.

The detection of a Remote Procedure Call (RPC) that compromises system integrity.

The detection of a hash value of an executable file that is not valid as determined by Code Integrity.

Cryptographic operations that compromise system integrity.

Volume: Low.

Default: Success, Failure.�IPsec Driver

This policy setting allows you to audit events generated by the IPsec filter driver such as the following:

Startup and shutdown of the IPsec services.

Network packets dropped due to integrity check failure.

Network packets dropped due to replay check failure.

Network packets dropped due to being in plaintext.

Network packets received with incorrect Security Parameter Index (SPI). This may indicate that either the network card is not working correctly or the driver needs to be updated.

Inability to process IPsec filters.

If you configure this policy setting, an audit event is generated on an IPsec filter driver operation. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated on an IPSec filter driver operation.

Volume: Low.

Default: No Auditing.PA<Other System Events

This policy setting allows you to audit any of the following events:

Startup and shutdown of the Windows Firewall service and driver.

Security policy processing by the Windows Firewall Service.

Cryptography key file and migration operations.

Volume: Low.

Default: Success, Failure.�File System

This policy setting allows you to audit user attempts to access file system objects. A security audit event is generated only for objects that have system access control lists (SACL) specified, and only if the type of access requested, such as Write, Read, or Modify and the account making the request match the settings in the SACL. For more information about enabling object access auditing, see https://go.microsoft.com/fwlink/?LinkId=122083.

If you configure this policy setting, an audit event is generated each time an account accesses a file system object with a matching SACL. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when an account accesses a file system object with a matching SACL.

Note: You can set a SACL on a file system object using the Security tab in that object's Properties dialog box.

Volume: Depends on how the file system SACLs are configured.PRegistry

This policy setting allows you to audit attempts to access registry objects. A security audit event is generated only for objects that have system access control lists (SACLs) specified, and only if the type of access requested, such as Read, Write, or Modify, and the account making the request match the settings in the SACL.

If you configure this policy setting, an audit event is generated each time an account accesses a registry object with a matching SACL. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when an account accesses a registry object with a matching SACL.

Note: You can set a SACL on a registry object using the Permissions dialog box.

Volume: Depends on how registry SACLs are configured.�Kernel Object

This policy setting allows you to audit attempts to access the kernel, which include mutexes and semaphores.

Only kernel objects with a matching system access control list (SACL) generate security audit events.

Note: The Audit: Audit the access of global system objects policy setting controls the default SACL of kernel objects.

Volume: High if auditing access of global system objects is enabled.�SAM

This policy setting allows you to audit events generated by attempts to access to Security Accounts Manager (SAM) objects.

SAM objects include the following:

SAM_ALIAS -- A local group.

SAM_GROUP -- A group that is not a local group.

SAM_USER A user account.

SAM_DOMAIN A domain.

SAM_SERVER A computer account.

If you configure this policy setting, an audit event is generated when an attempt to access a kernel object is made. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when an attempt to access a kernel object is made.

Note: Only the System Access Control List (SACL) for SAM_SERVER can be modified.

Volume: High on domain controllers. For information about reducing the amount of events generated in this subcategory, see article 841001 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=121698).�Certification Services

This policy setting allows you to audit Active Directory Certificate Services (AD CS) operations.

AD CS operations include the following:

AD CS startup/shutdown/backup/restore.

Changes to the certificate revocation list (CRL).

New certificate requests.

Issuing of a certificate.

Revocation of a certificate.

Changes to the Certificate Manager settings for AD CS.

Changes in the configuration of AD CS.

Changes to a Certificate Services template.

Importing of a certificate.

Publishing of a certification authority certificate is to Active Directory Domain Services.

Changes to the security permissions for AD CS.

Archival of a key.

Importing of a key.

Retrieval of a key.

Starting of Online Certificate Status Protocol (OCSP) Responder Service.

Stopping of Online Certificate Status Protocol (OCSP) Responder Service.

Volume: Medium or Low on computers running Active Directory Certificate Services.XApplication Generated

This policy setting allows you to audit applications that generate events using the Windows Auditing application programming interfaces (APIs). Applications designed to use the Windows Auditing API use this subcategory to log auditing events related to their function.

Events in this subcategory include:

Creation of an application client context.

Deletion of an application client context.

Initialization of an application client context.

Other application operations using the Windows Auditing APIs.

Volume: Depends on the applications that are generating them.PA�Handle Manipulation

This policy setting allows you to audit events generated when a handle to an object is opened or closed. Only objects with a matching system access control list (SACL) generate security audit events.

If you configure this policy setting, an audit event is generated when a handle is manipulated. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when a handle is manipulated.

Note: Events in this subcategory generate events only for object types where the corresponding Object Access subcategory is enabled. For example, if File system object access is enabled, handle manipulation security audit events are generated. If Registry object access is not enabled, handle manipulation security audit events will not be generated.

Volume: Depends on how SACLs are configured.{File Share

This policy setting allows you to audit attempts to access a shared folder.

If you configure this policy setting, an audit event is generated when an attempt is made to access a shared folder. If this policy setting is defined, the administrator can specify whether to audit only successes, only failures, or both successes and failures.

Note: There are no system access control lists (SACLs) for shared folders. If this policy setting is enabled, access to all shared folders on the system is audited.

Volume: High on a file server or domain controller because of SYSVOL network access required by Group Policy.�Windows Filtering Platform Packet Drop

This policy setting allows you to audit packets that are dropped by Windows Filtering Platform (WFP).

Volume: High.BWindows Filtering Platform Connection

This policy setting allows you to audit connections that are allowed or blocked by the Windows Filtering Platform (WFP). The following events are included:

The Windows Firewall Service blocks an application from accepting incoming connections on the network.

The WFP allows a connection.

The WFP blocks a connection.

The WFP permits a bind to a local port.

The WFP blocks a bind to a local port.

The WFP allows a connection.

The WFP blocks a connection.

The WFP permits an application or service to listen on a port for incoming connections.

The WFP blocks an application or service to listen on a port for incoming connections.

If you configure this policy setting, an audit event is generated when connections are allowed or blocked by the WFP. Success audits record events generated when connections are allowed and Failure audits record events generated when connections are blocked.

If you do not configure this policy setting, no audit event is generated when connected are allowed or blocked by the WFP.

Volume: High.�Other Object Access Events

This policy setting allows you to audit events generated by the management of task scheduler jobs or COM+ objects.

For scheduler jobs, the following are audited:

Job created.

Job deleted.

Job enabled.

Job disabled.

Job updated.

For COM+ objects, the following are audited:

Catalog object added.

Catalog object updated.

Catalog object deleted.

Volume: Low.�Detailed File Share

This policy setting allows you to audit attempts to access files and folders on a shared folder. The Detailed File Share setting logs an event every time a file or folder is accessed, whereas the File Share setting only records one event for any connection established between a client and file share. Detailed File Share audit events include detailed information about the permissions or other criteria used to grant or deny access.

If you configure this policy setting, an audit event is generated when an attempt is made to access a file or folder on a share. The administrator can specify whether to audit only successes, only failures, or both successes and failures.

Note: There are no system access control lists (SACLs) for shared folders. If this policy setting is enabled, access to all shared files and folders on the system is audited.

Volume: High on a file server or domain controller because of SYSVOL network access required by Group Policy.`Removable storage

This policy setting allows you to audit user attempts to access file system objects on a removable storage device. A security audit event is generated only for all objects for all types of access requested.

If you configure this policy setting, an audit event is generated each time an account accesses a file system object on a removable storage. Success audits record successful attempts and Failure audits record unsuccessful attempts.

If you do not configure this policy setting, no audit event is generated when an account accesses a file system object on a removable storage.�Central Access Policy Staging

This policy setting allows you to audit access requests where the permission granted or denied by a proposed policy differs from the current central access policy on an object.

If you configure this policy setting, an audit event is generated each time a user accesses an object and the permission granted by the current central access policy on the object differs from that granted by the proposed policy. The resulting audit event will be generated as follows:

1) Success audits, when configured, records access attempts when the current central access policy grants access but the proposed policy denies access.

2) Failure audits when configured records access attempts when:

a) The current central access policy does not grant access but the proposed policy grants access.

b) A principal requests the maximum access rights they are allowed and the access rights granted by the current central access policy are different than the access rights granted by the proposed policy.

Volume: Potentially high on a file server when the proposed policy differs significantly from the current central access policy.

Default: No AuditingPA�Directory Service Access

This policy setting allows you to audit events generated when an Active Directory Domain Services (AD DS) object is accessed.

Only AD DS objects with a matching system access control list (SACL) are logged.

Events in this subcategory are similar to the Directory Service Access events available in previous versions of Windows.

Volume: High on domain controllers. None on client computers.

Default on Client editions: No Auditing.

Default on Server editions: Success.>Active Directory Domain Services Object Changes

This policy setting allows you to audit events generated by changes to objects in Active Directory Domain Services (AD DS). Events are logged when an object is created, deleted, modified, moved, or undeleted.

When possible, events logged in this subcategory indicate the old and new values of the object s properties.

Events in this subcategory are logged only on domain controllers, and only objects in AD DS with a matching system access control list (SACL) are logged.

Note: Actions on some objects and properties do not cause audit events to be generated due to settings on the object class in the schema.

If you configure this policy setting, an audit event is generated when an attempt to change an object in AD DS is made. Success audits record successful attempts, however unsuccessful attempts are NOT recorded.

If you do not configure this policy setting, no audit event is generated when an attempt to change an object in AD DS object is made.

Volume: High on domain controllers only.

Default: No AuditinghDirectory Service Replication

This policy setting allows you to audit replication between two Active Directory Domain Services (AD DS) domain controllers.

If you configure this policy setting, an audit event is generated during AD DS replication. Success audits record successful replication and Failure audits record unsuccessful replication.

If you do not configure this policy setting, no audit event is generated during AD DS replication.

Note: Events in this subcategory are logged only on domain controllers.

Volume: Medium on domain controllers. None on client computers.

Default: No Auditing.�Detailed Directory Service Replication

This policy setting allows you to audit events generated by detailed Active Directory Domain Services (AD DS) replication between domain controllers.

Volume: High.

Default: No Auditing.�Credential Validation

This policy setting allows you to audit events generated by validation tests on user account logon credentials.

Events in this subcategory occur only on the computer that is authoritative for those credentials. For domain accounts, the domain controller is authoritative. For local accounts, the local computer is authoritative.

Volume: High on domain controllers.

Default on Client editions: No Auditing.

Default on Server editions: Success.�Kerberos Service Ticket Operations

This policy setting allows you to audit events generated by Kerberos authentication ticket-granting ticket (TGT) requests submitted for user accounts.

If you configure this policy setting, an audit event is generated after a Kerberos authentication TGT is requested for a user account. Success audits record successful requests and Failure audits record unsuccessful requests.

If you do not configure this policy setting, no audit event is generated after a Kerberos authentication TGT is request for a user account.

Volume: Low.

Default on Client editions: No Auditing.

Default on Server editions: Success.%Other Account Logon Events

This policy setting allows you to audit events generated by responses to credential requests submitted for a user account logon that are not credential validation or Kerberos tickets.

Currently, there are no events in this subcategory.

Default: No Auditing.qKerberos Authentication Service

This policy setting allows you to audit events generated by Kerberos authentication ticket-granting ticket (TGT) requests.

If you configure this policy setting, an audit event is generated after a Kerberos authentication TGT request. Success audits record successful requests and Failure audits record unsuccessful requests.

If you do not configure this policy setting, no audit event is generated after a Kerberos authentication TGT request.

Volume: High on Kerberos Key Distribution Center servers.

Default on Client editions: No Auditing

Default on Server editions: Success.PA�4VS_VERSION_INFO��
aJ
aJ?(StringFileInfo040904B0LCompanyNameMicrosoft Corporationj!FileDescriptionAudit Policy MMC SnapIn Messagesn'FileVersion10.0.19041.5915 (WinBuild.160101.0800)DInternalNameAuditPolSnapInMsg�.LegalCopyright� Microsoft Corporation. All rights reserved.POriginalFilenameAuditPolMsg.DLL.MUIj%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.19041.5915DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD