Configure Windows event logging to ensure the proper events are logged

This topic applies only to customers on the Splunk Cloud platform.

Configure Windows event logging to make sure that the events required for behavioral analytics service detections are logged.

Behavioral analytics service detections require 4688, 4103, and 4104 events in order to generate anomalies. See Supported data sources in behavioral analytics service for a complete list of supported Windows events.

Turn on command line process logging for 4688 events

Microsoft Windows 4688 events contain audit information for command line processes. To turn on 4688 events to be logged, perform the following tasks:

1. Turn on Audit Process Creation.
   1. Go to the policy editor on your local Windows machine. The policy is located at Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Configuration > Detailed Tracking.
   2. Select Audit Process Creation.
   3. Select both the Success and Failure checkboxes in the Audit Process Creation Properties window.
   4. Select OK. You can verify your setting if both Success and Failure appear in the Audit Events column, as shown in the following image:
      
2. Turn on Include command line in process creation events.
   1. Go to Computer Configuration > Policies > Administrative Templates > System > Audit Process Creation.
   2. Select Include command line in process creation events.
   3. Select the Activate / turn on checkbox to turn on the command line logging in process creation events.
      
   4. Select Apply.
   5. Select OK to dismiss the window.

If you are using automation software, such as Ansible, for remote configurations, use the following script to turn on command line process logging:

- name: Enable Command Line Audit for Windows Sec. Events 4688
  ignore_errors: yes
  when: win_4688_cmd_line == "1"
  win_regedit:
    key: "HKLM:\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Audit"
    value: ProcessCreationIncludeCmdLine_Enabled
    datatype: dword
    data: 1
- name: Enable New Process Creation. Events 4688
  ignore_errors: yes
  when: win_4688_cmd_line == "1"
  win_audit_policy_system:
    subcategory: Process Creation
    audit_type: success, failure

Turn on PowerShell logging for 4103 and 4104 events

PowerShell provides access to Windows API calls that attackers can exploit to gain elevated access to the system, avoiding antivirus and other security controls in the process. PowerShell is also internally utilized by popular hacking tools.

Perform the following tasks to properly turn on PowerShell logging:

1. On your local Windows system, go to Administrative Templates > Windows Components > Windows PowerShell.
2. Select Turn on Script Execution.
3. Select the Activated / Turned on checkbox.
4. Select an execution policy from the drop-down list in the Execution Policy field. In the following image, the Allow all scripts policy is selected.
   
5. Select Apply.
6. Select OK to dismiss the window.
7. Repeat the process and also turn on Turn on Module Logging, Turn on PowerShell Script Block Logging, and Turn on PowerShell Transcription. The following image shows the additional options:
   

If you are using automation software, such as Ansible, for remote configurations, use the following script to turn on PowerShell logging:

- name: Enable Windows Scriptblock Logging
  ignore_errors: yes
  win_regedit:
    key: "HKLM:\\Software\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlockLogging"
    value: EnableScriptBlockLogging
    datatype: dword
    data: 1
- name: Enable Windows Scriptblock Logging
  ignore_errors: yes
  win_regedit:
    key: "HKLM:\\Software\\Policies\\Microsoft\\Windows\\PowerShell\\ScriptBlockLogging"
    value: EnableScriptBlockInvocationLogging
    datatype: dword
    data: 1
- name: restart machine
  win_reboot:

See also

• For more information on command-line process auditing and auditing, see "Command line process auditing" in the Microsoft documentation.

• For more information on logging, see "About Logging Windows" in the Microsoft documentation.