Detection rules › Kusto
Cyble Vision Alerts Domain Expiry Alert
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 a monitored domain is about to expire. Expired domains risk service disruption, takeover, or misuse by adversaries.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Impact | T1499 Endpoint Denial of Service |
Rule body kusto
id: 81404e99-ce27-45aa-aa19-a276a3d4c645
name: Cyble Vision Alerts Domain Expiry Alert
description: |
'Triggers when a monitored domain is about to expire. Expired domains risk service disruption, takeover, or misuse by adversaries.'
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
relevantTechniques:
- T1499
query: |
Alerts_domain_expiry
| where Service == "domain_expiry"
| extend MappedSeverity = Severity
incidentConfiguration:
createIncident: true
groupingConfiguration:
enabled: false
reopenClosedIncident: false
lookbackDuration: PT5H
matchingMethod: AllEntities
alertDetailsOverride:
alertDisplayNameFormat: Domain Expiration Imminent {{DE_Domain}}
alertDescriptionFormat: |
The monitored domain is expiring soon. Expiry Date {{DE_ExpiryDate}}. Due in {{DE_DueDays}} days. Alert Type {{DE_TypeText}}. Immediate renewal is recommended to avoid service disruption or domain hijacking.
customDetails:
MappedSeverity: Severity
Status: Status
AlertID: AlertID
Service: Service
DE_Domain: DE_Domain
DE_DueDays: DE_DueDays
DE_ExpiryDate: DE_ExpiryDate
DE_TypeText: DE_TypeText
entityMappings:
- entityType: DNS
fieldMappings:
- identifier: DomainName
columnName: DE_Domain
version: 1.0.0
kind: Scheduled
Stages and Predicates
Stage 1: source
Alerts_domain_expiry
Stage 2: where
| where Service == "domain_expiry"
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 |