Detection rules › Kusto

Valence Security Alerts

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.

Status
available
Severity
high
Time window
5m
Source
github.com/Azure/Azure-Sentinel

'Valence Security Alerts'

Rule body kusto

id: d944d564-b6fa-470d-b5ab-a1a141878c5e
name: Valence Security Alerts
description: |
  'Valence Security Alerts'
severity: High
requiredDataConnectors:
  - connectorId: ValenceSecurity
    dataTypes:
      - ValenceAlert_CL
queryFrequency: 5m
queryPeriod: 5m
triggerOperator: gt
triggerThreshold: 0
eventGroupingSettings:
  aggregationKind: SingleAlert
status: Available
tactics: []
relevantTechniques:
query: |
  ValenceAlert_CL
alertDetailsOverride:
  alertDisplayNameFormat: 'Valence Alert: {{alertType_name_s}}'
  alertDescriptionFormat: '{{alertType_description_s}}'
  alertSeverityColumnName: alertType_severity_s
  alertDynamicProperties: []
customDetails:
  ValenceAlertName: alertType_name_s
  ValenceAlertDesc: alertType_description_s
  ValencePlatform: alertType_platform_s
  ValenceAlertSeverity: alertType_severity_s
  ValenceCreatedTS: createdTimestamp_d
  ValenceConnectorUids: connectorUids_s
version: 1.0.0
kind: Scheduled

Stages and Predicates

Stage 1: source

ValenceAlert_CL