SOURCE GUIDE / SKYKICK CUSTOMER REFRESH / 29 OCTOBER 2026

Start here: identify your customer tenant, source, UTC start, recorded end, and retention. Verify one known service-principal sign-in and one directory change against the original source. Missing records are not a negative finding. These are read-only hunt starters; no tenant or vendor engine execution is claimed.

1. Microsoft Sentinel or Log Analytics: queries/skykick-hunt-starters.kql has five blocks: 01A, 01B, 02, 03, and 04. Requires AADServicePrincipalSignInLogs and AuditLogs ingested through configured Microsoft Entra diagnostic settings, the relevant categories, workspace access, and any applicable Entra/Azure licensing and ingestion charges. The workspace's TenantId is not the customer's AADTenantId. Set TenantFilter to the customer Entra tenant GUID; an empty filter searches every visible tenant. KQL here belongs in Sentinel/Log Analytics, not automatically Defender Advanced Hunting. Set the portal picker to include the full explicit query interval. Table existence is not proof of continuous collection.

2. Splunk, LogScale/Falcon Next-Gen SIEM, and Sumo Logic: the new graph-directoryaudit files parse Microsoft's documented Graph v1.0 directoryAudit JSON directly. They are audit-only routes. They do not supply or infer service-principal sign-ins. GS/GL/GU01 selects five broad directory categories; GS/GL/GU02 selects a listed application as the recorded initiating application. The actor route is not a target application search, self-assignment finding, or maliciousness verdict. Missing actor fields remain in the broad category route. User actors, empty target arrays, failed results, and unknown results are not filtered out by that broad route.

Use real retained Graph directoryAudit exports already collected, or configure an authorized Microsoft Graph collection workflow. GET https://graph.microsoft.com/v1.0/auditLogs/directoryAudits supports AuditLog.Read.All as the least privileged API permission; delegated access also needs a supported directory role. Follow @odata.nextLink until all pages are retrieved. Export the individual objects from value[] as UTF-8 JSON lines. Preserve every property, nested initiatedBy, targetResources, modifiedProperties, original event ID, collection time, and customer identity in protected collection metadata. Never save bearer tokens in event content. This package has no collector and does not create historical data.

Each SIEM event must be one original directoryAudit object, not a wrapper, value[] response, Event Hub envelope, Azure Monitor uppercase-schema row, or Microsoft 365 Management Activity record. If your integration supplies another event format, use its documented parser and corresponding query. Do not silently treat that envelope as Graph JSON. These searches parse real Microsoft keys; their few output aliases are direct query-local extractions, not a new event schema.

Splunk: ingest the JSON lines using your managed file/HEC route; configure event boundaries and _time from activityDateTime, retaining _raw. Replace both index and sourcetype with the verified, customer-scoped source. SPL spath explicitly extracts each key. Check extraction limits on long events, field collisions with automatic extractions, and inspect the original record for every result. The shipped block is SPL, not SPL2.

LogScale: ingest the same JSON objects into an authorized repository or view with a JSON parser and @timestamp parsed from activityDateTime. Select that exact customer source in the UI before running GL01 or GL02. parseJson(field=@raw) extracts the original keys at query time; no dc_* normalization is used. Retain @raw and view complete events. These blocks deliberately omit select() so that a default projection does not hide nested evidence; verify result/export limits for a full timeline. A Falcon endpoint sensor alone does not collect this cloud feed.

Sumo: ingest those objects using an existing documented Local File or HTTP Logs and Metrics Source route. Replace _sourceCategory with the configured customer-scoped source category; this literal is a selector, not a built-in feed or table. Configure one JSON object per message and event time from activityDateTime. Explicit json ... nodrop extraction preserves missing keys. Inspect the Messages view and raw record, including all nested targets. The HTTP transport alone is not telemetry: Graph records must actually be collected, paginated, and delivered first. No custom Deception Check event producer is required or implied.

For all three Graph routes, verify customer attribution from the configured source and protected export manifest. directoryAudit does not provide a universal tenantId field. Never substitute a workspace, repository, or organization identifier for a source tenant. Select October 13, 2026 00:00 UTC to a recorded end for the historical indicator-led investigation; extend to October 1 only where retained history permits. When old exports are reingested, ensure event-time parsing is correct and widen the picker if ingest time and event time differ. Treat the seven IDs and three IPs as the October 19 advisory snapshot, not a refreshed current indicator list. Confirm current vendor guidance before action.

3. Sophos: queries/skykick-sophos-searches.json contains six query strings for Fusion Advanced Search (C00-C04, N01); it is not a policy import. Configure the Microsoft Entra Activity Reports integration with ServicePrincipalSignInLogs and AuditLogs when using Event Hubs. For Graph-based integration, verify service-principal login collection explicitly; interactive sign-ins and directory audits are defaults in the documented integration setup. Confirm current Sophos entitlement, integration health, customer scope, and source categories on a known event. auth/cloudaudit are documented Sophos logical schemas, not a package-defined feed. C00 counts alone do not prove the right auth source. C02-C04 inspect original text; GUID roles require manual confirmation. Sophos documents a 20-day raw access limit: older raw-dependent searches may be unavailable even when some normalized data remains. Use retained exports when needed.

Sophos Data Lake SQL: skykick-sophos-m365-datalake.sql has L00-L02 over the documented xdr_identity_o365 table from the Microsoft 365 Management Activity integration. This is a distinct audit feed, not dedicated service-principal sign-in history. Verify organization_id/customer scope and query_name partitions. Endpoint SQL: skykick-sophos-endpoint.sql has E01-E03 for authorized Windows Live Discover endpoints. Network/process journals provide supporting local history; sophos_pid is not the Windows numeric PID. Endpoint snapshots are not a tenant-wide cloud ledger. Run the exact dialect in its named editor.

4. Sigma: two experimental Azure auditlogs rules keep standard source fields and Deception Check in author. Nested InitiatedBy.app field extraction needs a verified backend mapping. App-initiated does not mean self-assigned, successful, or unauthorized. Preserve outcomes. YAML parsing, source fixtures, and successful backend conversion are different checks; no backend or tenant execution is claimed for this refresh.

5. ADVANCED: retained October 19 dc_* mapping, normalized SPL/CQL, full portable pseudocode, and explanation. This is engineering reference for teams deliberately maintaining that mapping. It is not the primary customer route. Do not deploy these as stock vendor-field searches.

Interpret findings: keep listed app OR reported address paths independent; retain IPv6, failed, and unknown outcomes. Examine credential, owner, role, and consent changes across all applications. Follow verified identities and key IDs into available Microsoft Graph and Microsoft 365 resource records. Compare event time with the specific customer's containment time. A recorded attempt is not proof of success; a permission change is not proof of data access. No validated malicious file or memory sample supports a YARA signature here.

Primary references (checked 29 October 2026 for new JSON routes; prior incident snapshot retained):
https://learn.microsoft.com/en-us/graph/api/resources/directoryaudit?view=graph-rest-1.0
https://learn.microsoft.com/en-us/graph/api/directoryaudit-list?view=graph-rest-1.0
https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/aadserviceprincipalsigninlogs
https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/auditlogs
https://learn.microsoft.com/en-us/entra/identity/monitoring-health/howto-configure-diagnostic-settings
https://help.splunk.com/en/splunk-enterprise/spl-search-reference/9.4/search-commands/spath
https://library.humio.com/crowdstrike-query-language/functions-parsejson.html
https://library.humio.com/crowdstrike-query-language/functions-in.html
https://help.sumologic.com/docs/search/search-query-language/parse-operators/parse-json-formatted-logs/
https://help.sumologic.com/docs/send-data/installed-collectors/sources/local-file-source/
https://help.sumologic.com/docs/send-data/hosted-collectors/http-source/logs-metrics/
https://docs.sophos.com/fusion/customer/help/en-us/ManageYourProducts/XDRSecOps/Integrations/Products/MicrosoftEntra/ActivityReports/Setup/index.html
https://docs.sophos.com/fusion/customer/help/en-us/ManageYourProducts/XDRSecOps/Search/DataLakeSearch/QueryLanguage/index.html
https://docs.sophos.com/fusion/customer/help/en-us/ManageYourProducts/XDRSecOps/Integrations/Products/Microsoft365/ManagementAPI/index.html
https://docs.sophos.com/central/References/schemas/schemas/xdr_identity_o365_schema_docs.json
https://docs.sophos.com/central/References/schemas/schemas/endpoint_schema.json
https://www.connectwise.com/company/trust/advisories
