Generate Security Audits
Allows a process to generate audit entries in the security log.
- Policy path
- Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment
- Supported on
- Windows 10, Windows 11, Windows Server 2016 and later
Allows a process to generate audit entries in the security log. Security baselines recommend setting it to Local Service, Network Service only.
Description
Generate Security Audits is a Windows Group Policy setting located under Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment. It applies to the Computer Configuration branch and is classified as a Warning-level policy in the Local Policies category.
Allows a process to generate audit entries in the security log.
Microsoft sets the default value to Local Service, Network Service while industry security baselines (CIS, NIST, DISA STIG) recommend Local Service, Network Service only.
In-depth explanation
This setting has a meaningful impact on the security posture or operational stability of the system. Leaving it at the Microsoft default is acceptable for standalone or low-risk environments, but most security baselines (CIS, NIST, DISA STIG) explicitly call for hardening it before the device is exposed to untrusted users or networks.
The policy is grouped under Local Policies – User Rights, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).
The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.
Use cases
- Apply organization-wide hardening of local policies on all domain-joined Windows endpoints.
- Roll out a CIS Benchmark-aligned baseline targeting 'Generate Security Audits' via a dedicated GPO.
- Reduce attack surface for accounts that handle privileged credentials or sensitive data.
- Standardize the configuration across multiple customer tenants for an MSP-managed fleet.
Security implications
Leaving this policy at default does not directly grant an attacker access, but it widens the blast radius once initial access is obtained – passwords are easier to guess, lockout doesn't fire, audit trails are incomplete, or lateral movement is quieter. Most regulators and cyber-insurance underwriters now expect this control to be in place at least at the recommended level.
How to configure
- Open Group Policy Management Console (
gpmc.msc) on a domain controller or a workstation with RSAT installed. - Create or edit a GPO linked to the OU containing the target computer configurations. We recommend a dedicated baseline GPO (e.g. SEC – Local Policies) instead of editing Default Domain Policy.
- Navigate to
Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment. - Open Generate Security Audits and set it to
Local Service, Network Service only. - Click OK and close the editor.
- On the target endpoint, run
gpupdate /force(or wait for the next refresh cycle), then verify withrsop.mscorgpresult /h report.html.