Detection rules › Kusto
Cyble Vision Alerts Compromised Endpoint Cookies
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.
'Detects compromised browser cookies associated with monitored entities. Identifies exposed authentication cookies with future expiry, enabling potential session hijacking or persistent unauthorized access.'
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Credential Access | T1539 Steal Web Session Cookie |
| Lateral Movement | T1550 Use Alternate Authentication Material |
Rule body kusto
id: 33B07EAA-F451-4C38-AC9F-8AF3F7E99F0E
name: Cyble Vision Alerts Compromised Endpoint Cookies
description: |
'Detects compromised browser cookies associated with monitored entities. Identifies exposed authentication cookies with future expiry, enabling potential session hijacking or persistent unauthorized access.'
severity: Low
status: Available
requiredDataConnectors:
- connectorId: CybleVisionAlerts
dataTypes:
- CybleVisionAlerts_CL
enabled: true
queryfrequency: 30m
queryPeriod: 30m
triggerOperator: GreaterThan
triggerThreshold: 0
suppressionDuration: PT1H
eventGroupingSettings:
aggregationKind: AlertPerResult
tactics:
- CredentialAccess
- DefenseEvasion
relevantTechniques:
- T1539
- T1550
query: |
Alerts_compromised_endpoints_cookies
| where Service == "compromised_endpoints_cookies"
| extend MappedSeverity = Severity
incidentConfiguration:
createIncident: true
groupingConfiguration:
enabled: false
reopenClosedIncident: false
lookbackDuration: PT5H
matchingMethod: AllEntities
alertDetailsOverride:
alertDisplayNameFormat: Compromised Session Cookie {{CEC_Email}} {{CEC_URL}}
alertDescriptionFormat: |
A compromised browser session cookie associated with {{CEC_EmailDomain}} was detected for service {{CEC_URL}}. The cookie has not expired and may allow session hijacking. Session ID {{CEC_SessionID}}.
customDetails:
MappedSeverity: Severity
Status: Status
AlertID: AlertID
Service: Service
CookieEmail: CEC_Email
CookieDomain: CEC_EmailDomain
CookieSessionID: CEC_SessionID
CookieExpiry: CEC_Expiry
CookieURL: CEC_URL
entityMappings:
- entityType: Url
fieldMappings:
- identifier: Url
columnName: CEC_URL
- entityType: Account
fieldMappings:
- identifier: FullName
columnName: CEC_Email
version: 1.0.0
kind: Scheduled
Stages and Predicates
Stage 1: source
Alerts_compromised_endpoints_cookies
Stage 2: where
| where Service == "compromised_endpoints_cookies"
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 |