312-39 practice question 5 of 35

John, SOC analyst wants to monitor the attempt of process creation activities from any of their Windows endpoints. Which of following Splunk query will help him to fetch related logs associated with process creation?

Full set: 100 questions
Answer options
A: index=windows LogName=Security EventCode=4678 NOT (Account_Name=*$) .. .. ... ..
B: index=windows LogName=Security EventCode=4688 NOT (Account_Name=*$) .. .. .. Correct answer
C: index=windows LogName=Security EventCode=3688 NOT (Account_Name=*$) .. .. ..
D: index=windows LogName=Security EventCode=5688 NOT (Account_Name=*$) ... ... ...
Correct Answer:
B. index=windows LogName=Security EventCode=4688 NOT (Account_Name=*$) .. .. ..
Explanation

In Windows environments, Event ID 4688 is generated in the Security Log whenever a new process is created, provided that "Audit Process Creation" is enabled. A SOC analyst would query for this specific event code to monitor for potentially malicious or unauthorized software execution on endpoints. The Splunk query index=windows LogName=Security EventCode=4688 correctly targets these events. The additional NOT (AccountName=$) is a common filter to exclude processes created by system accounts, which often end with a dollar sign, helping to reduce noise.

Why Incorrect

A. EventCode=4678: This event ID corresponds to "A privileged service was called," which is a different activity from process creation.
C. EventCode=3688: This event ID is related to Schannel (TLS/SSL) errors and is not associated with process creation events.
D. EventCode=5688: This is not a standard, documented Windows Security Event ID for process creation.

References

1. Microsoft Corporation. (2023, February 23). 4688(S): A new process has been created. Windows Security Auditing Documentation. Retrieved from Microsoft Learn. Section: "Event Details" and "Security Monitoring Recommendations."

2. Splunk Inc. (2022). Splunk Security Essentials. Splunk Documentation. The "Process Creation with Command Line" detection search uses EventCode 4688 as the primary indicator for Windows process creation.

3. MITRE. Command and Scripting Interpreter. MITRE ATT&CK Framework, T1059. The "Procedure Examples" and "Detection" sections frequently reference monitoring process creation events like Windows Event ID 4688.

Question breakdown

Tests
Splunk queries for Windows Security event IDs
Difficulty
Easy

Key idea: Windows Security Event ID 4688 records the creation of a new process, so it is the event to query when monitoring process creation.

How to reach the answer

  1. The clue is 'process creation' on Windows endpoints.
  2. Windows Security event 4688 means 'A new process has been created'.
  3. The other IDs are either different events or not valid Security log process events.
  4. The filter NOT Account_Name=*$ excludes machine accounts, which reduces noise.

Each option

  • AIncorrect. 4678 is not the process creation event.
  • BCorrect. EventCode 4688 is the Windows Security event for new process creation.
  • CIncorrect. 3688 is not a Windows Security process creation event ID.
  • DIncorrect. 5688 is not the process creation event.

Common trap: The distractors share the same '688' suffix, so candidates who only half-remember the ID can pick the wrong prefix.

In practice: SOC analysts hunt for suspicious executions, such as encoded PowerShell, using 4688 with command-line auditing enabled, or Sysmon Event ID 1.

Remember: 4688 = process created; 4689 = process exited.

Drafted with AI assistance and checked against the answer key.

Keep practicing

Take the free 312-39 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test

More questions

Other 312-39 practice questions

Scroll to Top