Skip to content
Home » Server Hardening & Event Logs » Recommended Windows Audit Policy for Small Businesses

Recommended Windows Audit Policy for Small Businesses

Windows can record almost everything that happens on your server: every sign-in, every wrong password, every new account, every new service. Out of the box, though, the Windows audit policy leaves some of the most useful security events switched off. When something goes wrong, the evidence you need was never written down.

This is a copy-paste Windows audit policy baseline for small business servers. It takes about ten minutes, works on Windows Server 2016 and later (and Windows 10 and 11), and records the events that matter without burying you in noise.

What the defaults miss

The defaults are better than their reputation. According to Microsoft’s audit policy recommendations, a Windows Server install already audits sign-ins (success and failure) and, on success only, sign-outs, account lockouts, user account changes, security group changes and changes to the audit policy itself.

The gaps are elsewhere. By default Windows does not audit Credential Validation (password checks against local accounts), Other Account Management Events, Security System Extension (new services), process creation, Remote Desktop reconnects and disconnects, or changes to Windows Firewall rules. Those are what the baseline below adds.

Two rules shape it. First, do not trust whatever the server has now: an old Group Policy or an earlier admin may have changed it, so set the policy explicitly. Second, more auditing is not better auditing. Switch everything on and the Security log fills with thousands of file-access entries an hour, burying the one event that mattered. The baseline audits a small set of high-signal subcategories and leaves the noisy ones off.

The baseline: copy-paste version

Open Command Prompt as Administrator and paste the block below. The :: lines are comments and are safe in Command Prompt. (In PowerShell, paste only the auditpol lines; PowerShell does not accept :: comments.) Each line sets one audit subcategory with Windows’ built-in auditpol tool.

:: --- Sign-ins: who gets in, who fails, who gets locked out ---
auditpol /set /subcategory:"Logon" /success:enable /failure:enable
auditpol /set /subcategory:"Logoff" /success:enable
auditpol /set /subcategory:"Account Lockout" /success:enable /failure:enable
auditpol /set /subcategory:"Special Logon" /success:enable
auditpol /set /subcategory:"Other Logon/Logoff Events" /success:enable /failure:enable

:: --- Credential checks: password guesses against local accounts ---
auditpol /set /subcategory:"Credential Validation" /success:enable /failure:enable

:: --- Account changes: new users, group membership, persistence moves ---
auditpol /set /subcategory:"User Account Management" /success:enable /failure:enable
auditpol /set /subcategory:"Security Group Management" /success:enable /failure:enable
auditpol /set /subcategory:"Other Account Management Events" /success:enable /failure:enable

:: --- Tampering: changes to the audit policy and to firewall rules ---
auditpol /set /subcategory:"Audit Policy Change" /success:enable /failure:enable
auditpol /set /subcategory:"Authentication Policy Change" /success:enable
auditpol /set /subcategory:"MPSSVC Rule-Level Policy Change" /success:enable

:: --- System integrity: security subsystem, new services ---
auditpol /set /subcategory:"Security State Change" /success:enable
auditpol /set /subcategory:"Security System Extension" /success:enable /failure:enable

The subcategory names are in the Windows display language. On a server installed in another language, run auditpol /list /subcategory:* to see the local names.

Two of these lines are worth explaining. Other Logon/Logoff Events records Remote Desktop sessions being reconnected and disconnected (events 4778 and 4779) and the screen being locked and unlocked, which helps when you reconstruct who was on the server and when. MPSSVC Rule-Level Policy Change records Windows Firewall changes: a rule added (4946), changed (4947) or deleted (4948), and a firewall setting changed (4950). Attackers often open a port or switch the firewall off before doing anything else; without this subcategory, the firewall changes and the log says nothing.

Optional: record every program that runs

Process creation auditing records every program launched (event 4688). It adds a moderate amount of log volume and is invaluable during an investigation. The second line adds the full command line to each event, so you see not only that PowerShell ran but what it was told to do:

auditpol /set /subcategory:"Process Creation" /success:enable
reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Audit" /v ProcessCreationIncludeCmdLine_Enabled /t REG_DWORD /d 1 /f

One caution: if anyone types a password into a command line, it ends up in the log too. Pair this with PowerShell script block logging for full visibility into scripts.

Make the log big enough to matter

The Security log defaults to 20 MB. With auditing on, a busy server or one under password-guessing attack can wrap that in a day or two, so an attack you discover on Friday may already have overwritten Monday’s evidence. Give it room:

wevtutil sl Security /ms:536870912

That sets the Security log to 512 MB. How many days that holds depends on how busy the server is, so check rather than guess. In an elevated PowerShell window, this shows the oldest event still in the log:

Get-WinEvent -LogName Security -Oldest -MaxEvents 1

The target to aim for in India is 180 days. CERT-In’s Directions of 28 April 2022 require the organisations they cover to keep logs of their ICT systems for a rolling 180 days, within India. If 512 MB does not reach that, increase it further, or keep regular exports of the log somewhere safe. Disk is cheap; missing evidence is not.

Prefer Group Policy? The same baseline via GPO

If you manage more than one machine, set the policy centrally. Open gpmc.msc (domain) or gpedit.msc (single server) and go to:

Computer Configuration > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policies

Enable the same subcategories as above; they are grouped under Account Logon, Account Management, Detailed Tracking, Logon/Logoff, Policy Change and System. Then set one companion option under Security Settings > Local Policies > Security Options: enable “Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings”. Without it, older category-level settings can silently override the subcategories you chose.

Verify it took effect

Never assume a policy applied. Two checks:

  1. Run auditpol /get /category:* and confirm each subcategory above shows “Success” or “Success and Failure”, not “No Auditing”.
  2. Make a test event. Sign in over Remote Desktop or at the console, then look in Event Viewer > Windows Logs > Security for a fresh event 4624 with your account name. Type one deliberately wrong password and confirm a 4625 appears (our guide to event 4625 explains every field).

What this baseline unlocks

With the policy applied, the Security log records the events that expose real attacks. For a wider tour of the logs, see what Windows event logs are and why they matter.

  • 4624 / 4625: successful and failed sign-ins. The raw material for spotting password-guessing attacks and after-hours access. Logon type 10 means Remote Desktop.
  • 4740: account locked out. Someone is guessing hard enough to trip your lockout policy.
  • 4720 / 4726 / 4732: account created, deleted, added to a group. The classic moves an attacker makes to keep a way back in.
  • 4672: special privileges assigned to a new sign-in. Written every time an account with admin-level rights signs in, including SYSTEM and service accounts, so expect many a day (Microsoft). Do not alert on it by itself; use it to see which sign-ins carried admin rights.
  • 4778 / 4779: Remote Desktop session reconnected or disconnected. Fills the gaps between sign-in and sign-out when people leave sessions open.
  • 4946 / 4947 / 4948 / 4950: firewall rule added, changed, deleted, or a firewall setting changed. A new rule opening a port, or the firewall switched off, deserves a question every time.
  • 4697 (Security log) and 7045 (System log): service installed. Attackers install services to survive reboots; on a stable server these are rare.
  • 4719: audit policy changed. Attackers turn auditing off before doing damage; this is often the last event before a gap.
  • 1102: audit log cleared. Almost never legitimate. Treat it as an incident until proven otherwise.
  • 4688: process created (if you enabled it). What ran, when, and with what command line.

What we deliberately left out

Object Access auditing (file and registry access) generates enormous volume and only makes sense pointed at specific sensitive folders, not switched on broadly. Directory Service auditing applies only to domain controllers. Detailed Tracking beyond process creation is more than a small office needs day to day.

Treat this baseline as a floor. For Indian firms, the relevant rules are CERT-In’s 180-day log retention and 6-hour incident reporting (Directions of 28 April 2022), and the Digital Personal Data Protection Rules 2025, whose main duties apply from May 2027 and expect reasonable security safeguards, including keeping logs for at least a year. If your auditor or a client contract asks for more, add it on top. This is not legal advice.

Logging is half the job

This baseline makes your server record the right evidence. It does not make anyone look at it: event 4625 sends no emails, and a 1102 at 2 AM does not escalate itself. Whether you review the Security log weekly by hand, script your own checks, or use a tool, decide who or what is watching before you call the job done.

Prixl Warden reads these events on the server and emails plain-English alerts about password-guessing, sign-ins outside office hours, new accounts and admin-group changes, new services, a cleared log, the firewall being switched off and firewall rule changes. It also switches on the audit subcategories it relies on, including Logon, Account Lockout, account and group management, Audit Policy Change and MPSSVC Rule-Level Policy Change, and switches them back on if someone turns them off. Start your 30-day free trial to see what your server’s log has been saying.

Related reading

Leave a Reply

Your email address will not be published. Required fields are marked *