Microsoft Sentinel
OrbisID can send its findings, privileged accounts and KRI values to a Microsoft Sentinel (Log Analytics) workspace, so an analyst sees OrbisID context next to an alert without opening OrbisID. This is available in the Pro and Enterprise editions, and the Administrator role sets it up under Administration > Integrations > SIEM Export.
OrbisID sends the data with the Azure Monitor Logs Ingestion API, using the client credentials of a Microsoft Entra application you create. Changes are sent in the minutes after a scan or a KRI snapshot, in batches, and a delivery that fails is retried by the next run.
What is sent
Three streams, each into its own custom table. A record is sent when it changes, so a table holds the history; use arg_max(TimeGenerated, *) to read the latest state of each item.
| Stream | Default table | Sent when | One row per |
|---|---|---|---|
| Findings | OrbisIdFindings_CL | A finding is created or changes (status, owner, severity, due date) | Change to a finding |
| Privileged accounts | OrbisIdPrivilegedAccounts_CL | A privileged account is detected or updated by a scan or an override | Update to a privileged account |
| KRI values | OrbisIdKris_CL | A KRI snapshot is taken (up to 10 unsent snapshots per run, oldest first) | KRI per snapshot |
OrbisID never sends a password, key or secret. Findings and accounts carry names and the owner's name and email, so the workspace's access controls should be at least as strict as OrbisID's.
Columns
Findings: TimeGenerated, FindingId, KriCode, KriName, EntityType, EntityId, EntityName, SystemName, Severity, FindingStatus, OwnerName, OwnerEmail, OpenedAt, FirstSeenAt, DueAt, ResolvedAt, ReopenCount.
Privileged accounts: TimeGenerated, AccountId, AccountName, SystemName, SystemOsType, AccountType, NhiSubtype, Enabled, OwnerName, OwnerEmail, OwnerUsername, Ownership (OWNED, ORPHANED or NO_OWNER), PamRiskLevel, InPamVault, LastUsedAt, LastUsedSource, LastDetectedAt.
KRI values: TimeGenerated, SnapshotId, KriCode, KriName, GrossValue, AdjustedValue, DenominatorValue.
A value OrbisID does not know is left out, not sent as empty. Date columns are datetime, Enabled and InPamVault are boolean, ReopenCount is int, the three KRI value columns are long, and the rest are string.
Set it up in Azure
-
Create the tables. In the Log Analytics workspace, create the three custom tables (names must end in
_CL) with the columns above. Creating a custom table in the Azure portal also creates a data collection rule; you can instead use one rule for all three as below. Column names must start with a letter and be at most 45 characters. -
Create a data collection rule (DCR) of kind
Directin the same region as the workspace, with three input streams and three data flows. Each flow's transformation turns theEventTimecolumn OrbisID sends intoTimeGenerated. Abbreviated for the findings stream (repeat the pattern for the other two, naming their columns from the lists above):{
"location": "<region>",
"kind": "Direct",
"properties": {
"streamDeclarations": {
"Custom-OrbisIdFindings": {
"columns": [
{ "name": "EventTime", "type": "datetime" },
{ "name": "FindingId", "type": "string" },
{ "name": "KriCode", "type": "string" },
{ "name": "Severity", "type": "string" },
{ "name": "FindingStatus", "type": "string" }
]
}
},
"destinations": {
"logAnalytics": [ { "workspaceResourceId": "<workspace resource ID>", "name": "sentinel" } ]
},
"dataFlows": [
{
"streams": [ "Custom-OrbisIdFindings" ],
"destinations": [ "sentinel" ],
"transformKql": "source | extend TimeGenerated = todatetime(EventTime) | project-away EventTime",
"outputStream": "Custom-OrbisIdFindings_CL"
}
]
}
}Declare every column the stream carries, with the same types as the table. The DCR's logs ingestion URI and immutable ID (it starts with
dcr-) are shown in its JSON view. A data collection endpoint is only needed if you use private link. -
Register an application in Microsoft Entra ID and create a client secret. Note the application (client) ID, the directory (tenant) ID and the secret value.
-
Give the application access to the rule. On the DCR, open Access control (IAM) and add the Monitoring Metrics Publisher role for the application. A new assignment can take up to 30 minutes to take effect.
Set it up in OrbisID
Open Administration > Integrations > SIEM Export and enter the tenant ID, the client ID and secret, the logs ingestion endpoint (an https address ending in .monitor.azure.com), the DCR immutable ID and the three stream names (the defaults are Custom-OrbisIdFindings, Custom-OrbisIdPrivilegedAccounts and Custom-OrbisIdKris). The secret is stored encrypted and is never shown again; leave it blank to keep the saved one.
- Test sign-in checks the application's credentials with Entra. It sends no data.
- Send now sends what changed straight away. The first run sends all findings and privileged accounts and the latest KRI snapshot only; later runs send only changes.
- The panel shows the last run, the last success and the last error. After a failure the same records are sent again by the next run; nothing is skipped.
Data takes a few minutes to appear in the workspace, and longer the first time a table receives data. Only the public Azure cloud is supported. To send to Splunk instead, or as well, use the Splunk card on the same page.
If delivery fails
| Result | Meaning |
|---|---|
| HTTP 401 or 403 | The application lacks the Monitoring Metrics Publisher role on the rule, or the assignment has not taken effect yet |
| HTTP 404 | The endpoint, the immutable ID or a stream name is wrong |
| HTTP 413 | A call exceeded 1 MB (OrbisID splits batches below that, so this means an unusually large single record) |
| HTTP 429 | The rule is being throttled; OrbisID waits for the Retry-After time and tries again |
| HTTP 400 | A column in the data does not match the stream declaration or table |
Use it in Sentinel
These queries are starting points; adjust them to your tables and sign-in sources.
Enrich sign-ins with OrbisID context: successful sign-ins by privileged accounts that are not in a PAM vault, or whose owner has left.
let privileged = OrbisIdPrivilegedAccounts_CL
| summarize arg_max(TimeGenerated, *) by AccountId
| where Enabled == true and (InPamVault == false or Ownership != "OWNED")
| extend Upn = tolower(AccountName);
SigninLogs
| where ResultType == 0
| extend Upn = tolower(UserPrincipalName)
| join kind=inner privileged on Upn
| project TimeGenerated, UserPrincipalName, IPAddress, AppDisplayName, SystemName, InPamVault, Ownership, OwnerName, PamRiskLevel
Use the same query as an analytics rule (scheduled, for example hourly) to raise an incident when it returns rows. Accounts are matched on the account name, so this suits accounts whose name is their user principal name; for other directories join on the field your sign-in source carries.
Open findings by severity (for a workbook):
OrbisIdFindings_CL
| summarize arg_max(TimeGenerated, *) by FindingId
| where FindingStatus in ("OPEN", "IN_PROGRESS")
| summarize Findings = count() by Severity
Non-human identity hygiene over time (for a workbook):
OrbisIdKris_CL
| where KriCode in ("ORPHANED_NHI", "NHI_WITHOUT_OWNER", "EXPIRED_ACTIVE_CREDENTIALS", "LONG_LIVED_CREDENTIALS")
| summarize Value = max(AdjustedValue) by bin(TimeGenerated, 1d), KriName
| render timechart
Microsoft documentation
OrbisID's use of the API follows these Microsoft Learn pages: Logs Ingestion API in Azure Monitor (endpoint, headers, role, custom table rules), Tutorial: Send data with the Logs ingestion API (rule structure, role assignment), Sample code to send data using the Logs ingestion API (token request, api-version=2023-01-01, HTTP 204, troubleshooting) and Azure Monitor service limits (1 MB per call, 64 KB per field, throttling).