Techniques › T1219.003 › AN0447
AN0447 Analytic 0447
Linux · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Insertion of USB-based hardware proxies (e.g., PiKVM) which register under predictable names (e.g., tinypilot) or mount under known paths (e.g., /opt/tinypilot-privileged).</p>
- Detects
- T1219.003 Remote Access Hardware
- Part of
- DET0159 Detect Remote Access via USB Hardware (TinyPilot, PiKVM)
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| auditd:SYSCALL | udev events or drive enumeration involving TinyPilot paths or device classes | DC0042 Drive Creation |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
FriendlyName | Different hardware may present differently; names like 'TinyPilot' may need expanding to cover custom implants. |
MountPath | Path matching (e.g., /opt/tinypilot) is mutable based on distro, customization, and staging. |