Defacement: External Defacement T1491.002

Tactic: Impact

An adversary may deface systems external to an organization in an attempt to deliver messaging, intimidate, or otherwise mislead an organization or users. External Defacement may ultimately cause users to distrust the systems and to question/discredit the system’s integrity. Externally-facing websites are a common victim of defacement; often targeted by adversary and hacktivist groups in order to push a political message or spread propaganda. External Defacement may be used as a catalyst to trigger events, or as a response to actions taken by an organization or government. Similarly, website defacement may also be used as setup, or a precursor, for future attacks such as Drive-by Compromise.

Authoring guide

Patterns shared across the 1 rule above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names 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 (7 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
Esql.aws_cloudtrail_request_parameters_object_key1ends_with 1.js
EventType1eq 1PutObject
Provider_Name1eq 1s3.amazonaws.com
aws::requestParameters1wildcard 1*static/js/*.js*
aws::userIdentity.type1in 1AssumedRole, IAMUser
data_stream.dataset1eq 1aws.cloudtrail
event.outcome1eq 1success

Top indicator values (8 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. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
Esql.aws_cloudtrail_request_parameters_object_keyends_with
.js
1
EventTypeeq
PutObject
14
Provider_Nameeq
s3.amazonaws.com
114
aws::requestParameterswildcard
*static/js/*.js*
1
aws::userIdentity.typein
AssumedRole
1
aws::userIdentity.typein
IAMUser
15
data_stream.dataseteq
aws.cloudtrail
1141
event.outcomeeq
success
1251

Exclusions (3 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.

FieldKindValueRules excluding
aws::userAgentcontains
ansible
1
aws::userAgentcontains
pulumi
1
aws::userAgentcontains
terraform
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.

Platform (all)
Domain (all)

Elastic 1 rule