ATT&CK coverage › Technique

Web Service: Bidirectional Communication T1102.002

Adversaries may use an existing, legitimate external Web service as a means for sending commands to and receiving output from a compromised system over the Web service channel. Compromised systems may leverage popular websites and social media to host command and control (C2) instructions. Those infected systems can then send the output from those commands back over that Web service channel. The return traffic may occur in a variety of ways, depending on the Web service being utilized. For example, the return traffic may take the form of the compromised system posting a comment on a forum, issuing a pull request to development project, updating a document hosted on a Web service, or by sending a Tweet.

Events covered

3 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon22DNSEvent (DNS query)
Security-Auditing4688A new process has been created.

Authoring guide

Patterns shared across the 3 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (6 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
Image1ends_with 1\Runner.Worker.exe, \Runner.Listener.exe
OriginalFileName1eq 1Runner.Worker.dll, Runner.Listener.dll
CommandLine1match 1configure, spawnclient, run
query1eq 1"api.telegram.org"
process_name1ne 1"telegram.exe"
EventID1eq 122

Top indicator values (10 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
Imageends_with\Runner.Worker.exe1
CommandLinematchrun1
CommandLinematchspawnclient1
OriginalFileNameeqRunner.Listener.dll1
CommandLinematchconfigure1
OriginalFileNameeqRunner.Worker.dll1
Imageends_with\Runner.Listener.exe1
EventIDeq22115
queryeq"api.telegram.org"1
process_namene"telegram.exe"1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 1 rule

Splunk 1 rule

Kusto Query Language 1 rule