Impair Defenses T1629

Mobile Tactic: Defense Evasion

Authoring guide

Patterns shared across the 7 rules 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 (26 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
EventType3eq 3AUDIT, DEVICE, THREAT
Name3eq 3blockedattachments, enableipbasedcookiebinding, powerplatform.analytics.resource.tenant.isolation_policy.enabled
EntityName2eq 2organization
Message2eq 2Update
Value2eq 2False
AuditType1in 1CONFIGURATION_CHANGE, POLICY_CHANGE, SECURITY_SETTING_CHANGE
ChangeType1eq 1UPDATE
ClientIp1is_not_null 1
DeviceComplianceStatus1in 1Non-Compliant, Partial
DeviceSecurityStatus1in 1THREATS_HIGH, THREATS_MEDIUM
Entities1contains 1"appid":32780
EventOriginalType1eq 1EnvironmentPropertyChange, TenantIsolationOperation
HistoricalTime1lt 1LatestEvent
IPCount1gt 11
Identity1eq 1Microsoft Invitation Acceptance Portal

Top indicator values (36 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
EntityNameeq
organization
24
Messageeq
Update
25
Valueeq
False
23
AuditTypein
CONFIGURATION_CHANGE
1
AuditTypein
POLICY_CHANGE
1
AuditTypein
SECURITY_SETTING_CHANGE
1
AuditTypein
USER_MANAGEMENT
1
ChangeTypeeq
UPDATE
1
DeviceComplianceStatusin
Non-Compliant
1
DeviceComplianceStatusin
Partial
1
DeviceSecurityStatusin
THREATS_HIGH
1
DeviceSecurityStatusin
THREATS_MEDIUM
1
Entitiescontains
"appid":32780
1
EventOriginalTypeeq
EnvironmentPropertyChange
1
EventOriginalTypeeq
TenantIsolationOperation
1
EventTypeeq
AUDIT
1
EventTypeeq
DEVICE
1
EventTypeeq
THREAT
1
HistoricalTimelt
LatestEvent
1
IPCountgt
1
1
Identityeq
Microsoft Invitation Acceptance Portal
1
Nameeq
blockedattachments
1
Nameeq
enableipbasedcookiebinding
1
Nameeq
powerplatform.analytics.resource.tenant.isolation_policy.enabled
1
OperationNameeq
Update user
16
PropertyCollectioncontains
property: securitygroupid, old value: , new value:
1
StartTimegt
GroupRemovalTimestamp
1
StartTimegt
TenantIsolationRemovalTimestamp
1
Tacticscontains
exfiltration
12
ThreatActioneq
DETECTED
1

Exclusions (4 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.

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)

Kusto 7 rules