Habr•July 21, 2026•🇷🇺Translated from Russian

Advanced Windows Auditing Configuration Guide for Effective Incident Response in SOC Environments

When beginning work in a SOC (Security Operations Center), it quickly becomes clear that default Windows logging provides limited visibility into system activities. Events such as logons, process creation, and policy changes are either not recorded or appear in a heavily truncated form.

The service responsible for managing auditing is LSASS (Local Security Authority Subsystem Service), which runs at startup and resides in memory to handle user sessions, authentication requests, and protection of sensitive data. LSASS writes audit information to the Security event log according to configured policies.

Windows offers two auditing levels: basic auditing with nine categories configured via secpol.msc and advanced auditing with 53 subcategories managed through the auditpol utility. The article focuses on advanced auditing because it allows precise control, for example enabling only Logon and Special Logon without cluttering logs with irrelevant Kerberos or IPsec events on standalone machines.

Key Subcategories and Corresponding Event IDs

The most important subcategories for incident response include:

  • Logon – successful logons (Event ID 4624)
  • Logoff – session termination (Event IDs 4634, 4647)
  • Account Lockout – lockout events (Event ID 4740)
  • Special Logon – privilege escalation via runas (Event ID 4648)
  • User Account Management – account creation and deletion (Event IDs 4720, 4726)
  • Security Group Management – group membership changes (Event IDs 4732, 4728)
  • Process Creation – executable launches (Event ID 4688)
  • Audit Policy Change – modifications to auditing itself (Event ID 4719)
  • Other System Events – log clearing (Event ID 1102)

Each subcategory has a fixed GUID that can be used with auditpol when localized names cause issues.

Enabling Advanced Auditing and Additional Logging

After opening an elevated command prompt on a clean Windows 10 Pro 22H2 virtual machine running under VMware Workstation 17 Pro, the author enables a baseline set of subcategories using multiple auditpol commands. Verification is performed with auditpol /get /category:* to confirm success and failure auditing is active for each item.

PowerShell logging is enabled via registry modification under HKLM\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ScriptBlockLogging, activating Script Block Logging that records decoded script content in the Microsoft-Windows-PowerShell/Operational log (Event IDs 4104 and 4103).

Command-line auditing for process creation events is activated by setting the registry value ProcessCreationIncludeCmdLine_Enabled under HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Audit, ensuring the Command Line field in Event ID 4688 is populated.

Practical Testing of Configured Auditing

Five hands-on tests illustrate the value of the configuration. A successful interactive logon produces Event ID 4624 showing Logon Type 2, account name, workstation name, and the responsible process. Failed logon attempts generate Event ID 4625 with failure reason codes such as 0xC000006A for incorrect password.

Process creation with arguments is demonstrated by running whoami /all, resulting in a detailed Event ID 4688 that includes Creator Process ID, New Process ID, and the full command line. Account creation and administrative group membership changes produce Events 4720 and 4732, revealing subject and target account details along with group names.

The article emphasizes performing all changes on virtual machines to prevent excessive log growth or interference with installed applications on production hosts.

Related articles

Habr•Policy & Regulation

Three Hypotheses on Information Security Risk Assessment: Where Automation Truly Saves Time at Avito

Avito expert Irina Sozinova details how the company tested automation in its risk assessment process after scaling issues emerged with thousands of risks in the GRC system. The team formulated and piloted three hypotheses focused on automating typical risks, eliminating manual team preparation, and validating data to reduce InfoSec workload. Results showed a 16% drop in total risks registered, zero preparation time for teams, and improved coverage and context quality, though overall expert time savings were partially offset by new post-processing tasks. The pilot confirmed that automation works best on repeatable scenarios with stable data sources rather than promising immediate proportional time cuts. Avito plans to complete automation of context collection and finding classification this year to expand risk assessments across the company next year.

Habr•Policy & Regulation

Integrating OAuth 2.0 with PDP Architectures Without Modifying Core Authorization Engines

The article explores how to combine OAuth 2.0 delegated access with traditional PEP/PDP authorization systems. It proposes an OAuth-aware PDP layer that translates access tokens into standard PDP checks while preserving the original PDP implementation. Three main use cases are analyzed: stored user grants, tenant-level administrative grants, and scopes carried directly inside tokens. The design relies on synthetic subjects such as u+c and t+c pairs, ephemeral policies for token-embedded scopes, and optional OAuth-aware PAP components. Special attention is given to token contents, policy storage via PAP, and the need for deterministic subject identifiers. The approach supports both classic scope models and structured RAR-style authorizations while maintaining separation between OAuth grants and subject permissions.

Habr•Policy & Regulation

Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks

The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.

Habr•Policy & Regulation

Russian Court Convicts Former IT Director for Unauthorized Access to Huawei Storage After Moving Servers Offsite

A former IT director at an Omsk manufacturing plant was found guilty under Part 3 of Article 272 of the Russian Criminal Code for blocking and modifying data on a Huawei Dorado 3000 v6 storage array after relocating the entire server infrastructure to a privately rented office. The court relied heavily on detailed logs from the Huawei system that recorded the exact sequence of disk removals, reinsertions in altered order, and the shutdown command, even after the administrator attempted to delete portions of the event journal. The incident occurred on the same day new management took over, causing immediate loss of access to corporate email, 1C systems, design software, and shared network resources. Despite the defendant's claims that he was preparing the array for cloud backup and that a script had frozen, the court rejected the explanation based on audit concealment, lack of notification to owners, and post-incident behavior. The ruling imposed a 400,000-ruble fine and a one-year ban on computer-information work involving protected secrets, while leaving a civil claim for 18.27 million rubles in recovery costs for separate proceedings. The case highlights how storage-array logs can serve as decisive forensic evidence and underscores the legal risks of retaining physical or logical access after employment ends.