Detection rules › Kusto
Armorblox Needs Review 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.
'This rule generates an alert for an Armorblox incident where the remediation action is "Needs Review".'
Rule body kusto
id: 322d4765-be6b-4868-9e3f-138a4f339dd6
name: Armorblox Needs Review Alert
description: |
'This rule generates an alert for an Armorblox incident where the remediation action is "Needs Review".'
severity: Medium
status: Available
requiredDataConnectors:
- connectorId: Armorblox
dataTypes:
- Armorblox_CL
queryFrequency: 10m
queryPeriod: 10m
triggerOperator: GreaterThan
triggerThreshold: 0
tactics: []
relevantTechniques: []
query: |
Armorblox_CL
| where remediation_actions_s contains "Needs Review"
| extend users_json = parse_json(users_s)
| extend Name = users_json[0].name, Email = users_json[0].email
| project-away users_json
entityMappings:
- entityType: Mailbox
fieldMappings:
- identifier: MailboxPrimaryAddress
columnName: Email
- identifier: DisplayName
columnName: Name
eventGroupingSettings:
aggregationKind: AlertPerResult
alertDetailsOverride:
alertDisplayNameFormat: Alert from Armorblox
alertDescriptionFormat: 'Incident {{id_s}} generated at {{date_t}} needs review '
alertSeverityColumnName: priority_s
customDetails:
IncidentId: id_s
RemediationAction: remediation_actions_s
version: 1.0.2
kind: Scheduled
Stages and Predicates
Stage 1: source
Armorblox_CL
Stage 2: where
| where remediation_actions_s contains "Needs Review"
Stage 3: extend
| extend users_json = parse_json(users_s)
Stage 4: extend
| extend Name = users_json[0].name, Email = users_json[0].email
Stage 5: project-away
| project-away users_json
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 |
|---|---|---|
remediation_actions_s | contains |
|
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 |
|---|---|
Email | extend |
Name | extend |