Query Details
id: b8c9d0e1-f2a3-4b4c-5d6e-7f8091122334
name: EasyVista - Orphaned Tickets Missing Sentinel Linkage
description: |
Hunts for EasyVista security tickets created via API (indicating Sentinel origin) that lack a valid EXTERNAL_REFERENCE.
May indicate playbook failures or manual ticket creation bypassing the automated workflow.
requiredDataConnectors:
- connectorId: EasyVistaITSM
dataTypes:
- EasyVista_Tickets_CL
tactics:
- Impact
query: |
EasyVista_Tickets_CL
| where TimeGenerated > ago(7d)
| where REQUEST_TYPE has_any ("Incident", "I")
| where ORIGIN == "API"
| where isempty(EXTERNAL_REFERENCE) or not(EXTERNAL_REFERENCE has "/subscriptions/")
| project TimeGenerated, RFC_NUMBER, ['TITLE'], STATUS_EN, SEVERITY_ID, REQUESTOR_NAME, ORIGIN, EXTERNAL_REFERENCE
| sort by TimeGenerated desc
This query is designed to identify potential issues with EasyVista security tickets that are supposed to be linked to Microsoft Sentinel but are missing the necessary linkage. Here's a simple breakdown:
Purpose: The query searches for security tickets in EasyVista that were created through an API, which suggests they originated from Microsoft Sentinel. It checks if these tickets are missing a valid external reference, which could indicate problems like playbook failures or manual ticket creation that bypasses the automated process.
Data Source: It uses data from the EasyVista IT Service Management (ITSM) connector, specifically looking at the EasyVista_Tickets_CL data type.
Time Frame: The query focuses on tickets generated in the last 7 days.
Filters:
EXTERNAL_REFERENCE field or do not contain a specific subscription path ("/subscriptions/").Output: The query outputs a list of relevant ticket details, including when they were generated, their RFC number, title, status, severity, requestor name, origin, and external reference.
Sorting: The results are sorted by the time they were generated, in descending order, so the most recent tickets appear first.

David Alonso
Released: April 16, 2026
Tables
Keywords
Operators