Detect Print Processors in IBM QRadar
Adversaries may abuse print processors to run malicious DLLs during system boot for persistence and/or privilege escalation. Print processors are DLLs that are loaded by the print spooler service, spoolsv.exe, during boot. Adversaries may abuse the print spooler service by adding print processors that load malicious DLLs at startup. A print processor can be installed through the AddPrintProcessor API call with an account that has SeLoadDriverPrivilege enabled. Alternatively, a print processor can be registered to the print spooler service by adding a Registry key under HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Print Processors with a Driver value pointing to the malicious DLL. The print spooler service runs under SYSTEM level permissions, therefore print processors installed by an adversary may run under elevated privileges.
MITRE ATT&CK
- Tactic
- Persistence Privilege Escalation
- Technique
- T1547 Boot or Logon Autostart Execution
- Sub-technique
- T1547.012 Print Processors
- Canonical reference
- https://attack.mitre.org/techniques/T1547/012/
QRadar Detection Query
SELECT DATEFORMAT(starttime, 'YYYY-MM-dd HH:mm:ss') AS event_time,
LOGSOURCENAME(logsourceid) AS log_source,
username,
"QIDNAME"(qid) AS event_name,
sourceip,
CATEGORYNAME(category) AS category_name,
"devicehostname" AS hostname,
"RegistryKey" AS registry_key,
"RegistryValue" AS registry_value,
"RegistryValueData" AS registry_data,
"TargetFilename" AS file_path,
"Image" AS process_image,
"ParentImage" AS parent_image,
"CommandLine" AS command_line
FROM events
WHERE LOGSOURCETYPEID(logsourceid) IN (SELECT id FROM log_source_types WHERE name ILIKE '%Sysmon%' OR name ILIKE '%Windows%')
AND starttime > NOW() - 86400000
AND (
(qid IN (SELECT id FROM qids WHERE name LIKE '%Registry%')
AND ("RegistryKey" ILIKE '%Control\\Print\\Environments%'
AND "RegistryKey" ILIKE '%Print Processors%'))
OR
(qid IN (SELECT id FROM qids WHERE name LIKE '%File Create%')
AND "TargetFilename" ILIKE '%\\spool\\prtprocs\\%'
AND "TargetFilename" ILIKE '%.dll%')
OR
(qid IN (SELECT id FROM qids WHERE name LIKE '%Process%')
AND "ParentImage" ILIKE '%\\spoolsv.exe'
AND "Image" NOT ILIKE '%\\splwow64.exe'
AND "Image" NOT ILIKE '%\\PrintIsolationHost.exe'
AND "Image" NOT ILIKE '%\\printfilterpipelinesvc.exe'
AND "Image" NOT ILIKE '%\\conhost.exe')
)
ORDER BY starttime DESC
LIMIT 500Detects print processor abuse (T1547.012) in QRadar by correlating three Sysmon event types: registry modifications to Print Processor paths (EventID 13), DLL creation in the print processor spool directory (EventID 11), and unexpected processes spawned by spoolsv.exe (EventID 1). The spooler service runs as SYSTEM, making hijacked print processors a high-privilege persistence mechanism.
Data Sources
Required Tables
False Positives & Tuning
- Printer driver packages from enterprise print management solutions may register new print processors as part of normal deployment workflows
- System administrators performing manual printer driver installation may trigger all three indicators simultaneously during legitimate maintenance
- Some antivirus or DLP products inject into the print spooler service and may spawn child processes from spoolsv.exe
Other platforms for T1547.012
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Print Processor Registry Key Creation
Expected signal: Sysmon Event ID 12: Registry Key Created for TestProcessor_df00tech subkey. Sysmon Event ID 13: Registry Value Set for Driver value with Details=winprint.dll. Security Event ID 4688 with CommandLine containing reg add and the full registry path.
- Test 2DLL Drop in Print Processor Directory
Expected signal: Sysmon Event ID 11: File Create with TargetFilename=C:\Windows\System32\spool\prtprocs\x64\df00tech_test_printproc.dll, Image=cmd.exe. DeviceFileEvents with ActionType=FileCreated in the prtprocs directory.
- Test 3PowerShell Print Processor Registration (Earth Lusca Style)
Expected signal: Sysmon Event ID 1: Process Create for powershell.exe with full command line. Sysmon Event ID 12: Registry Key Created. Sysmon Event ID 13: Registry Value Set. PowerShell ScriptBlock Log Event ID 4104 capturing the registry manipulation.
- Test 4Enumerate Existing Print Processors for Reconnaissance
Expected signal: Sysmon Event ID 1: Process Create for reg.exe with CommandLine containing reg query and Print Processors path. Security Event ID 4688 with same details. No registry modification events (read-only operation).
References (7)
- https://attack.mitre.org/techniques/T1547/012/
- https://docs.microsoft.com/en-us/windows/win32/printdocs/addprintprocessor
- https://learn.microsoft.com/windows-hardware/drivers/print/introduction-to-print-processors
- https://www.welivesecurity.com/2020/05/21/no-game-over-winnti-group/
- https://www.trendmicro.com/en_us/research/22/a/earth-lusca-employs-sophisticated-infrastructure-varied-tools-and-techniques.html
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1547.012/T1547.012.md
- https://github.com/SigmaHQ/sigma/tree/master/rules/windows/registry/registry_set
Unlock Pro Content
Get the full detection package for T1547.012 including response playbook, investigation guide, and atomic red team tests.