Potential Tunneling via AWS IoT Secure Tunneling Localproxy
Identifies AWS IoT Secure Tunneling localproxy started in destination mode that then resolves and connects to the Secure Tunneling data plane, data.tunneling.iot.<region>.amazonaws.com, on TCP/443. Destination mode…
Description
Identifies AWS IoT Secure Tunneling localproxy started in destination mode that then resolves and connects to the Secure Tunneling data plane, data.tunneling.iot.<region>.amazonaws.com, on TCP/443. Destination mode opens no listener; once the operator joins the tunnel the proxy forwards streams to a local service such as SSH on 127.0.0.1:22. Public red-team research shows this signed, documented binary used as post-exploitation C2 that resembles legitimate IoT device management. OpenTunnel and access tokens live in the operator's AWS account, not the victim's.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ESXiLinuxmacOSNetwork DevicesWindows
The rule states no platform. This is derived from the 3 ATT&CK techniques it maps to.
- Log source category
- event_index
Known benign triggers
- Support engineers and IoT operators may run localproxy on field devices or jump hosts that legitimately use AWS IoT Secure Tunneling. Confirm the host is an approved device-management asset, the parent process and binary path are expected, and the destination mapping points at an authorized local service. Allowlist by host, user, or signed install path where that use is documented.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| docs.aws.amazon.com/iot/latest/developerguide/local-proxy.html | Only this detection cites it |
| github.com/aws-samples/aws-iot-securetunneling-localproxy | Only this detection cites it |
| hackerhermanos.com/posts/aws-iot-secure-tunneling-red-teamer/ | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- deab559f-f3ab-4ce3-b17c-8f70c4169fd6
- Tagged by the source as
- Data Source: Elastic DefendDomain: EndpointDomain: NetworkDomain: OT/IoTOS: LinuxOS: macOSOS: WindowsPlatform: AWSPlatform: LinuxPlatform: macOSPlatform: WindowsResources: Investigation GuideRule Type: Event Correlation (EQL)Service: AWS IoTTactic: Command and ControlUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 29, 2026
- Version
- 1