Library · ATT&CK · T1218.011

Detecting Rundll32 in AWS, Azure, and GCP

01 What is T1218.011?

Adversaries may abuse rundll32.exe to proxy execution of malicious code.

a13e DCV ships 1 validated detection rule for T1218.011 across windows-sysmon. The rule emits in splunk dialect, generated by CloudSigma from the upstream Sigma corpus and validated against representative log samples. Every rule below carries an integrity badge (reviewed) and a Verify in CloudSigma deep link so you can run a fresh translation against your environment without leaving a13e.com.

T1218.011 sits inside MITRE ATT&CK's enterprise matrix; adversaries reach it via initial access or credential-access steps and pivot from it into impact, lateral movement, or persistence. Cloud blueprints — AWS CloudTrail, Azure Sign-in, GCP Audit Logs — are the high-fidelity observation surfaces where T1218.011 most reliably surfaces in production. DCV maps each cloud-native finding type to the technique so an a13e coverage scan tells you whether your existing detection controls cover T1218.011 before an adversary exercises it.

02 Coverage in DCV

DCV maps 1 detection across 1 cloud provider to T1218.011. Coverage by source:

Source Cloud Findings mapped Avg confidence
splunk windows 1 0.00

03 Detect with CloudSigma

CloudSigma has coverage metadata for 1 T1218.011 rule across 1 platform. The linked platform page remains the canonical rule surface; this page will embed an example after a rule clears the public embed bar.

CloudSigma has coverage metadata for T1218.011, but no public example rule clears the embed bar for this page yet. Generate a fresh starting-point rule in CloudSigma from the relevant advisory or threat-research input, then validate it against your local telemetry before enabling it in production.

04 Related techniques

05 FAQ

What is T1218.011?

Adversaries may abuse rundll32.exe to proxy execution of malicious code. Using rundll32.exe, vice executing directly (i.e. Shared Modules), may avoid triggering security tools that may not monitor execution of the rundll32.exe process because of allowlists or false positives from normal operations. Rundll32.exe is commonly associated with executing DLL payloads (ex: rundll32.exe {DLLname, DLLfunction}). Rundll32.exe can also be used to execute Control Panel Item files (.cpl) through the undocumented shell32.dll functions Control_RunDLL and Control_RunDLLAsUser. Double-clicking a .cpl file...

Which cloud platforms does a13e DCV cover for T1218.011?

a13e DCV currently maps T1218.011 to windows-sysmon. Each platform exposes one or more cloud-native finding types that DCV correlates back to the technique; the coverage table above lists the per-platform rule count and average confidence score reported by the DCV inventory at build time.

Which SIEMs support T1218.011 detection via a13e CloudSigma?

a13e CloudSigma emits T1218.011 rules in splunk dialect today. Translation is done at build time by the CloudSigma corpus + pysigma backends; every rule passes SigmaHQ validation and target-SIEM conversion before it appears on this page. New SIEM dialects light up automatically as the CloudSigma corpus extends.

How many rules does a13e ship for T1218.011?

1 rule across the platforms listed above. The count grows when CloudSigma ships new rules tagged to T1218.011 or when DCV adds a new cloud-native finding type that maps to the technique. Both cadences feed the same inventory artefact this page is built from.

How do I instrument T1218.011 detection in my own environment?

Run a free coverage scan in a13e DCV: it inspects your AWS, Azure, and GCP detection content + maps each existing detection to MITRE ATT&CK. Where T1218.011 is uncovered, DCV surfaces the gap with an actionable Sigma rule template you can copy into your SIEM. CloudSigma generates a fresh translation per SIEM dialect on demand.

Where can I see live coverage for my environment?

Run a free coverage scan in a13e DCV at https://app.a13e.com. The scan reads your existing detection content (Splunk, Sentinel, Chronicle, Elastic) and reports a per-technique coverage map against MITRE ATT&CK. The output highlights which techniques your DCV instance currently catches and which ones need new rules from CloudSigma.