T1200 Sumo Logic CSE · Sumo

Detect Hardware Additions in Sumo Logic CSE

Adversaries may physically introduce computer accessories, networking hardware, or other computing devices into a system or network to gain access or expand capabilities. Hardware additions range from passive network taps (Throwing Star LAN Tap) to active keystroke injection devices (USB Rubber Ducky, Bash Bunny, O.MG Cable), rogue wireless access points, DMA attack devices (PCILeech), and fully autonomous compute devices (Raspberry Pi, netbooks) providing persistent network footholds. Unlike purely software-based attacks, hardware additions require physical proximity to target systems and can bypass many software security controls by presenting as trusted peripherals. The DarkVishnya threat group is documented connecting Bash Bunny, Raspberry Pi, and inexpensive netbooks directly to victim organization networks to establish persistent access and conduct internal reconnaissance. Detection relies primarily on monitoring for unexpected device class connections via Windows Plug and Play audit events, correlating new HID device connections with subsequent automated keystroke injection patterns, and identifying new network interfaces with unknown MAC addresses appearing on internal segments.

MITRE ATT&CK

Tactic
Initial Access
Technique
T1200 Hardware Additions
Canonical reference
https://attack.mitre.org/techniques/T1200/

Sumo Detection Query

Sumo Logic CSE (Sumo)
sql
_sourceCategory=windows/security (EventCode=6416 OR EventID=6416)
| parse regex field=EventData "Name=\"ClassName\">(?P<ClassName>[^<]+)<"
| parse regex field=EventData "Name=\"DeviceId\">(?P<DeviceId>[^<]+)<"
| parse regex field=EventData "Name=\"HardwareIds\">(?P<HardwareIds>[^<]+)<"
| parse regex field=EventData "Name=\"ClassId\">(?P<ClassId>[^<]+)<"
| parse regex field=EventData "Name=\"SubjectUserName\">(?P<SubjectUserName>[^<]+)<"
| parse regex field=EventData "Name=\"SubjectDomainName\">(?P<SubjectDomain>[^<]+)<"
| eval IsKnownPentestVID = if(matches(HardwareIds, "(?i)(VID_2B04|VID_16D0|VID_2E8A|VID_2341|VID_1B4F|VID_221A|VID_04D8)"), 1, 0)
| eval IsLegitimateVendor = if(matches(HardwareIds, "(?i)(VID_045E|VID_046D|VID_05AC|VID_413C|VID_03F0|VID_17EF|VID_047D|VID_046A|VID_1B1C|VID_1532|VID_1038|VID_04B3|VID_04CA|VID_0461)"), 1, 0)
| eval IsHIDDevice = if(toLowerCase(ClassName) = "hidclass", 1, 0)
| eval IsNetworkDevice = if(matches(toLowerCase(ClassName), "(^net$|wlan|bluetooth|net service)"), 1, 0)
| eval IsSuspiciousHID = if(IsHIDDevice = 1 AND IsLegitimateVendor = 0, 1, 0)
| eval IsUSBNetDevice = if(IsNetworkDevice = 1 AND IsLegitimateVendor = 0 AND (matches(DeviceId, "(?i)USB") OR matches(HardwareIds, "(?i)USB")), 1, 0)
| eval SuspicionScore = (IsKnownPentestVID * 3) + IsSuspiciousHID + IsUSBNetDevice
| where SuspicionScore > 0
| eval RiskReason = if(IsKnownPentestVID = 1, "Known pentest/attack hardware VID detected",
    if(IsSuspiciousHID = 1, "Unknown vendor HID device — possible keystroke injector",
    if(IsUSBNetDevice = 1, "Unknown USB network adapter — possible LAN tap",
    "Suspicious device class connection")))
| fields _messagetime, _sourceHost, SubjectUserName, SubjectDomain, ClassName, ClassId, DeviceId, HardwareIds, IsHIDDevice, IsNetworkDevice, IsKnownPentestVID, SuspicionScore, RiskReason
| sort by SuspicionScore desc, _messagetime desc
high severity high confidence

Sumo Logic query detecting T1200 Hardware Additions via Windows Security Event 6416 (PnP Activity). Scores suspicious device connections by flagging known pentest hardware vendor IDs, unrecognized HID class devices that could be USB keystroke injectors, and unknown USB network adapters that may be rogue LAN taps or network implants. Requires Windows Security log collection via Installed Collector or Cloud Syslog Source.

Data Sources

Windows Security Event Log via Sumo Logic Installed CollectorWindows Event Log source with Security channel

Required Tables

windows/security (or equivalent _sourceCategory mapping)

False Positives & Tuning

  • Custom-built or OEM peripherals from small vendors whose VIDs are not in the legitimate vendor allowlist
  • USB docking stations with integrated NIC presenting as unknown USB network devices on hot-plug
  • Security researchers or red teamers using attack hardware in an authorized penetration testing engagement on the monitored network
Download portable Sigma rule (.yml)

Other platforms for T1200


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.

  1. Test 1Install Microsoft Loopback Network Adapter via devcon

    Expected signal: Windows Security Event ID 6416: ClassName=Net, ClassId={4d36e972-e325-11ce-bfc1-08002be10318}, DeviceId=ROOT\NET\0001 or similar, HardwareIds=*MSLOOP. Windows System Event IDs 20001 and 20003 in System log for driver installation. Entry in C:\Windows\INF\setupapi.dev.log with timestamp and INF path.

  2. Test 2Enumerate Connected HID Devices via PowerShell

    Expected signal: Sysmon Event ID 1: Process Create with Image=powershell.exe and CommandLine containing 'Get-PnpDevice' and 'HIDClass'. Security Event ID 4688 (if command line auditing enabled). PowerShell ScriptBlock Log Event ID 4104 with the full device enumeration script.

  3. Test 3Query USB Device Connection History via Registry

    Expected signal: Sysmon Event ID 1: Process Create for reg.exe with CommandLine containing 'HKLM\SYSTEM\CurrentControlSet\Enum\USB'. Sysmon Event ID 1 also for findstr.exe. Security Event ID 4688 (if enabled) for both processes. Registry access events may be logged depending on SACL configuration.

  4. Test 4Simulate Keystroke Injection via PowerShell SendKeys

    Expected signal: Sysmon Event ID 1: Process Create for powershell.exe initiated by the calling process, plus any processes spawned by the injected keystrokes. If Sysmon monitors for the parent process chain, keystrokes injected into an Explorer window will show explorer.exe as parent. PowerShell ScriptBlock Log Event ID 4104 for both the outer and any inner PowerShell sessions.

Unlock Pro Content

Get the full detection package for T1200 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections