Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-Printer-SensitiveDocumentExfil.
Upgrade to ProDetect Data Exfiltration via Sensitive Document Printing in IBM QRadar
Adversaries and malicious insiders may print sensitive documents to physically remove them from a facility as paper output, bypassing network-based DLP, email egress filtering, and removable-media controls entirely. This is a physical-medium exfiltration path distinct from USB transfer (T1052.001): the print spooler renders the document and a hard copy leaves the building in a pocket, bag, or folder with no file ever crossing the network egress boundary. Detection correlates Windows Print Service telemetry for bulk print volume, sensitive-keyword document names, and after-hours printing patterns that suggest deliberate physical removal of data rather than routine office printing.
MITRE ATT&CK
- Tactic
- Exfiltration
QRadar Detection Query
SELECT
DATEFORMAT(starttime, 'YYYY-MM-dd HH:mm:ss') AS EventTime,
"Computer" AS Hostname,
username AS UserName,
QIDNAME(qid) AS EventName,
"Message" AS PrintDetails,
COUNT(*) AS PrintJobCount
FROM events
WHERE
LOGSOURCETYPENAME(devicetype) ILIKE '%print%'
AND starttime > NOW() - 1 DAYS
AND qid IN (SELECT qid FROM QID WHERE name ILIKE '%printservice%' OR name ILIKE '%document printed%')
GROUP BY "Computer", username
HAVING COUNT(*) > 25
ORDER BY starttime DESCQRadar AQL query flagging hosts/users with more than 25 Print Service document-printed events (Event ID 307) within a 24-hour window. Intended to be paired with a separate custom property extraction rule parsing document name from the Message field to add sensitive-keyword matching for full T1052 physical-print exfiltration coverage.
Data Sources
Required Tables
False Positives & Tuning
- Legal, HR, or finance staff producing high print volume as routine job duties
- Print server or managed-print-service log sources generating one QRadar event per job at high baseline volume
- Departments with print-heavy workflows (mailroom, records management) exceeding the raw count threshold routinely
Other platforms for THREAT-Printer-SensitiveDocumentExfil
Testing Methodology
Validate this detection against 3 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 1Bulk Print of Sensitive-Named Documents via PowerShell
Expected signal: Microsoft-Windows-PrintService/Operational Event ID 307 recorded 10 times within a short window, each RenderedDescription/Message containing a document name matching 'confidential_payroll_report_*' owned by the test user.
- Test 2High-Volume Print Job Outside Business Hours
Expected signal: Microsoft-Windows-PrintService/Operational Event ID 307 recorded with Total pages printed reflecting the multi-page document, timestamped outside the 06:00-20:00 window.
- Test 3Print Job with Sensitive Content but Innocuous File Name
Expected signal: Microsoft-Windows-PrintService/Operational Event ID 307 recorded for 'notes.txt' — document name carries no sensitive keyword despite sensitive content.
References (4)
- https://attack.mitre.org/techniques/T1052/
- https://learn.microsoft.com/en-us/troubleshoot/windows-server/printing/detailed-tracing-print-job-progress
- https://learn.microsoft.com/en-us/azure/azure-monitor/agents/data-collection-rule-azure-monitor-agent
- https://www.papercut.com/products/ng/manual/common/topics/security-print-tracking.html
Unlock playbooks & atomic tests with Pro
Get the full detection package for THREAT-Printer-SensitiveDocumentExfil — response playbook and atomic red team tests, plus investigation guidance and hunting queries.
df00tech Pro — £29/user/month