T1592.001

Hardware

Adversaries may gather information about the victim's host hardware that can be used during targeting. Hardware details may include types and versions of specific hosts, as well as the presence of additional defensive components such as smart card readers, biometric authentication hardware, TPM chips, and dedicated encryption co-processors. Adversaries gather this information via direct Active Scanning (ex: banner grabbing, SNMP enumeration), Phishing for Information, or by compromising third-party websites and deploying malicious JavaScript reconnaissance frameworks (such as ScanBox) that silently collect host hardware telemetry from visiting users. Hardware information may also be passively harvested from publicly accessible sources including job postings listing specific hardware requirements, LinkedIn profiles, assessment reports, equipment purchase invoices, and network topology diagrams. Collected hardware intelligence enables adversaries to tailor exploits for specific processor architectures, identify hardware vulnerabilities (e.g., Spectre/Meltdown variants), plan hardware supply chain attack opportunities (T1195.003), and understand the physical security posture of the target — including whether hardware-based authentication is in use.

Microsoft Sentinel / Defender
kusto
// T1592.001 — Gather Victim Host Information: Hardware
// Detects the minority of hardware reconnaissance activity visible within victim networks.
// PRIMARY LIMITATION: Most T1592.001 activity (Shodan scanning, OSINT, job postings, LinkedIn)
// occurs entirely outside the victim environment. This query targets the two detectable
// in-environment signals: ScanBox-style JavaScript fingerprinting exfiltration and
// SNMP/service enumeration attempts against managed hosts.
//
// Confidence is LOW due to fundamental external-nature of this PRE technique.

let ExcludedHostnames = dynamic([
    "microsoft.com", "office.com", "windows.com", "live.com", "microsoftonline.com",
    "google.com", "googleapis.com", "gstatic.com",
    "apple.com", "icloud.com",
    "mozilla.org", "firefox.com",
    "amazon.com", "amazonaws.com", "cloudfront.net",
    "akamai.net", "akamaized.net", "cloudflare.com",
    "fastly.net", "cdn77.com"
]);
// ScanBox and similar JavaScript reconnaissance framework URL patterns
let ScanBoxURLPatterns = dynamic([
    "/scanbox", "/fp.php", "/gate.php", "/collect.php", "/beacon.php",
    "/hwinfo", "/hardware", "/fingerprint", "/stat.php", "/track.php"
]);
// Hardware-identifying parameters exfiltrated by browser fingerprinting scripts
let HardwareFingerprintParams = dynamic([
    "hardwareConcurrency", "deviceMemory", "cpuClass",
    "hardwareinfo", "numCores", "screenDepth",
    "colorDepth", "pixelDepth", "touchPoints"
]);
// Branch 1: Proxy/Firewall (CommonSecurityLog) detecting ScanBox-style POST exfiltration
let Branch1 = CommonSecurityLog
| where TimeGenerated > ago(24h)
| where DeviceProduct has_any ("Proxy", "Web Gateway", "URL Filter", "Firewall", "WAF", "NGFW")
    or DeviceVendor has_any ("Palo Alto Networks", "Fortinet", "Zscaler", "iboss",
                              "Symantec", "McAfee", "Blue Coat", "Cisco", "F5", "Imperva")
| where RequestMethod =~ "POST"
| where BytesSent between (100 .. 50000)
| where RequestURL has_any (ScanBoxURLPatterns)
    or AdditionalExtensions has_any (HardwareFingerprintParams)
    or Message has_any (HardwareFingerprintParams)
| where not(DestinationHostName has_any (ExcludedHostnames))
| extend DetectionBranch = "ScanBox-POST"
| extend RiskIndicator = case(
    RequestURL has_any ("/scanbox", "/gate.php", "/fp.php"), "KnownScanBoxURL",
    AdditionalExtensions has_any ("hardwareConcurrency", "deviceMemory", "cpuClass"), "HardwareFingerprintParam",
    RequestURL has_any ("/collect.php", "/beacon.php") and BytesSent > 500, "FingerprintExfiltration",
    "SuspiciousFingerprintURL"
)
| project TimeGenerated, SourceUserName, SourceIP, DestinationHostName, DestinationPort,
          RequestURL, RequestMethod, BytesSent, BytesReceived,
          DeviceVendor, Activity, RiskIndicator, DetectionBranch;
// Branch 2: SNMP enumeration targeting hardware OIDs from external/unexpected sources
// SNMP OID 1.3.6.1.2.1.25.3.2 = hrDeviceType, OID 1.3.6.1.2.1.47 = ENTITY-MIB (hardware)
let Branch2 = CommonSecurityLog
| where TimeGenerated > ago(24h)
| where DestinationPort == 161 or DestinationPort == 162  // SNMP UDP ports
| where ipv4_is_private(SourceIP) == false  // Inbound from external
| extend DetectionBranch = "ExternalSNMPEnum"
| extend RiskIndicator = "ExternalSNMPHardwareEnum"
| project TimeGenerated, SourceUserName = "", SourceIP, 
          DestinationHostName, DestinationPort,
          RequestURL = "", RequestMethod = "SNMP", BytesSent, BytesReceived,
          DeviceVendor, Activity, RiskIndicator, DetectionBranch;
Branch1
| union Branch2
| sort by TimeGenerated desc
medium severity low confidence

Data Sources

Network Traffic: Network Traffic Content Network Traffic: Network Traffic Flow Application Log: Application Log Content

Required Tables

CommonSecurityLog

False Positives

  • Analytics and telemetry platforms (Mixpanel, Amplitude, Heap, FullStory) that legitimately collect browser device metrics including screen resolution, hardware concurrency, and device memory for UX analytics
  • Authorized vulnerability management tools (Qualys, Rapid7 InsightVM, Tenable Nessus, Qualys VMDR) performing scheduled asset inventory scans including SNMP hardware enumeration from known scanner IPs
  • Web application performance monitoring frameworks (Modernizr, feature-detective.js) that detect browser hardware capabilities for progressive enhancement and responsive design decisions
  • Internal IT asset management systems performing SNMP polling for hardware inventory, network management, or capacity planning — typically from known NMS IP ranges
  • Content delivery networks and web performance tools (New Relic Browser, Datadog RUM, Dynatrace) that collect device/hardware metrics as part of real user monitoring

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections