Detection rules › Kusto
Cyble Vision Alerts Website Defacement Keyword
This is a third-party alert feed, not a detection over modeled telemetry. The vendor product raised the finding; this rule forwards it into the SIEM. It is searchable for reference but is excluded from the detection-rule browse and the ATT&CK coverage matrix.
'Triggers when monitored defacement keywords appear on a website, indicating potential early signs of website compromise or defacement-related activity.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Reconnaissance | T1598 Phishing for Information |
| Impact | T1491 Defacement |
Rule body kusto
id: 754dbb50-8dc2-4b8b-86d8-a890a020ddc3
name: Cyble Vision Alerts Website Defacement Keyword
description: |
'Triggers when monitored defacement keywords appear on a website, indicating potential early signs of website compromise or defacement-related activity.'
severity: Low
status: Available
requiredDataConnectors:
- connectorId: CybleVisionAlerts
dataTypes:
- CybleVisionAlerts_CL
enabled: true
queryfrequency: 30m
queryPeriod: 30m
triggerOperator: GreaterThan
triggerThreshold: 0
eventGroupingSettings:
aggregationKind: AlertPerResult
tactics:
- Impact
- Reconnaissance
relevantTechniques:
- T1491
- T1598
query: |
Alerts_defacement_keyword
| where Service == "defacement_keyword"
| extend MappedSeverity = Severity
incidentConfiguration:
createIncident: true
groupingConfiguration:
enabled: false
reopenClosedIncident: false
lookbackDuration: PT5H
matchingMethod: AllEntities
alertDetailsOverride:
alertDisplayNameFormat: Defacement Keyword Detected {{DK_Keyword}} on {{DK_DomainName}}
alertDescriptionFormat: |
A defacement-related keyword was observed on the website. URL {{DK_URL}}. Frequency count {{DK_Frequency}}. This may indicate early-stage defacement activity.
customDetails:
MappedSeverity: Severity
Status: Status
AlertID: AlertID
Service: Service
DK_URL: DK_URL
DK_DomainName: DK_DomainName
DK_Keyword: DK_Keyword
DK_Frequency: DK_Frequency
DK_RecordID: DK_RecordID
entityMappings:
- entityType: Url
fieldMappings:
- identifier: Url
columnName: DK_URL
- entityType: Host
fieldMappings:
- identifier: HostName
columnName: DK_DomainName
version: 1.0.0
kind: Scheduled
Stages and Predicates
Stage 1: source
Alerts_defacement_keyword
Stage 2: where
| where Service == "defacement_keyword"
Stage 3: extend
| extend MappedSeverity = Severity
Indicators
Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.
| Field | Kind | Values |
|---|---|---|
Service | eq |
|
Output fields
Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.
| Field | Source |
|---|---|
MappedSeverity | extend |