Skip to content

Add Claroty xDome CCF solution (initial submission v3.0.0) - #14911

Open
0ccupi3R wants to merge 1 commit into
Azure:masterfrom
0ccupi3R:master
Open

Add Claroty xDome CCF solution (initial submission v3.0.0)#14911
0ccupi3R wants to merge 1 commit into
Azure:masterfrom
0ccupi3R:master

Conversation

@0ccupi3R

Copy link
Copy Markdown
Contributor

Summary

  • Adds a new Microsoft Sentinel solution: Claroty xDome CCF.
  • Implements CCF pull-based ingestion from Claroty xDome API.
  • Includes connector package, parsers, workbook, analytic rules, hunting queries, and sample data.
  • Sets initial submission version to 3.0.0.

What is included

  • Data connector definition, DCR, and polling config
  • 7 destination tables
  • ASIM and VIM parsers
  • Workbook
  • 2 analytic rules
  • 3 hunting queries
  • Sample data
  • Solution metadata and package files

Non-impact statement

  • This PR introduces a separate solution and does not change the existing Claroty xDome solution.
  • IDs, offer/publisher metadata, and content paths are scoped to the new CCF solution.

Deployment

  • README includes Deploy to Azure button format aligned with Microsoft Learn guidance.
  • Package contains mainTemplate and createUiDefinition for manual deployment flow.

Versioning

  • Solution version set to 3.0.0 as initial submission.
  • Release notes updated accordingly.

Validation

  • JSON/package consistency checks completed.
  • Solution folder packaged for submission and review.

Checklist

  • Initial solution submission
  • Version aligned to 3.0.0
  • README simplified and deployment links updated
  • No changes to legacy Claroty xDome solution

@0ccupi3R
0ccupi3R requested review from a team as code owners August 13, 2026 19:56
@v-atulyadav
v-atulyadav requested a lite review from Copilot August 14, 2026 04:06
@v-atulyadav v-atulyadav added the New Solution For new Solutions which are new to Microsoft Sentinel label Aug 14, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds the initial Microsoft Sentinel solution package for Claroty xDome CCF (v3.0.0), including a CCF pull-based connector, tables, parsers, workbook, analytics, hunting, and sample data.

Changes:

  • Introduces CCF connector definition + polling configuration, plus 7 Log Analytics table resources.
  • Adds ASIM/VIM parsers, workbook, analytics rules, hunting queries, and solution packaging metadata/docs.
  • Provides sample data and release notes for initial submission.

Reviewed changes

Copilot reviewed 45 out of 46 changed files in this pull request and generated 15 comments.

Show a summary per file
File Description
Solutions/Claroty xDome CCF/Workbooks/ClarotyXDome.json Adds the solution workbook (tabs + KQL tiles/charts).
Solutions/Claroty xDome CCF/SolutionMetadata.json Adds solution marketplace metadata (publisher/offer/support).
Solutions/Claroty xDome CCF/Sample Data/ClarotyXDomeVulnerability_CL.json Adds sample vulnerability payloads.
Solutions/Claroty xDome CCF/Sample Data/ClarotyXDomeOTEvent_CL.json Adds sample OT activity event payloads.
Solutions/Claroty xDome CCF/Sample Data/ClarotyXDomeDevice_CL.json Adds sample device inventory payloads.
Solutions/Claroty xDome CCF/Sample Data/ClarotyXDomeDeviceVulnerability_CL.json Adds sample device-vulnerability relation payloads.
Solutions/Claroty xDome CCF/Sample Data/ClarotyXDomeDeviceAlert_CL.json Adds sample device-alert relation payloads.
Solutions/Claroty xDome CCF/Sample Data/ClarotyXDomeAuditLog_CL.json Adds sample audit log payloads.
Solutions/Claroty xDome CCF/Sample Data/ClarotyXDomeAlert_CL.json Adds sample alert payloads.
Solutions/Claroty xDome CCF/ReleaseNotes.md Adds initial release notes entry for v3.0.0.
Solutions/Claroty xDome CCF/README.md Adds solution README with deployment link and validation queries.
Solutions/Claroty xDome CCF/Parsers/vimNetworkSessionClarotyXDome.yaml Adds ASIM NetworkSession filtering parser (vim).
Solutions/Claroty xDome CCF/Parsers/vimAuditEventClarotyXDome.yaml Adds ASIM AuditEvent filtering parser (vim).
Solutions/Claroty xDome CCF/Parsers/vimAlertEventClarotyXDome.yaml Adds ASIM AlertEvent filtering parser (vim).
Solutions/Claroty xDome CCF/Parsers/CustomUnifyingParsers/Im_NetworkSessionCustom.json Adds custom unifying parser ARM template (Im_*).
Solutions/Claroty xDome CCF/Parsers/CustomUnifyingParsers/Im_AuditEventCustom.json Adds custom unifying parser ARM template (Im_*).
Solutions/Claroty xDome CCF/Parsers/CustomUnifyingParsers/Im_AlertEventCustom.json Adds custom unifying parser ARM template (Im_*).
Solutions/Claroty xDome CCF/Parsers/CustomUnifyingParsers/ASim_NetworkSessionCustom.json Adds custom unifying parser ARM template (ASim_*).
Solutions/Claroty xDome CCF/Parsers/CustomUnifyingParsers/ASim_AuditEventCustom.json Adds custom unifying parser ARM template (ASim_*).
Solutions/Claroty xDome CCF/Parsers/CustomUnifyingParsers/ASim_AlertEventCustom.json Adds custom unifying parser ARM template (ASim_*).
Solutions/Claroty xDome CCF/Parsers/ClarotyXDomeVulnerability.yaml Adds solution-specific parser function for vulnerabilities.
Solutions/Claroty xDome CCF/Parsers/ClarotyXDomeDeviceVulnerability.yaml Adds solution-specific parser function for device-vulnerability relations.
Solutions/Claroty xDome CCF/Parsers/ClarotyXDomeDevice.yaml Adds solution-specific parser function for device inventory.
Solutions/Claroty xDome CCF/Parsers/ClarotyXDomeAlert.yaml Adds solution-specific parser function for alerts.
Solutions/Claroty xDome CCF/Parsers/ASimNetworkSessionClarotyXDome.yaml Adds ASIM NetworkSession normalization parser (ASim*).
Solutions/Claroty xDome CCF/Parsers/ASimAuditEventClarotyXDome.yaml Adds ASIM AuditEvent normalization parser (ASim*).
Solutions/Claroty xDome CCF/Parsers/ASimAlertEventClarotyXDome.yaml Adds ASIM AlertEvent normalization parser (ASim*).
Solutions/Claroty xDome CCF/Package/testParameters.json Adds deployment test parameters artifact.
Solutions/Claroty xDome CCF/Package/createUiDefinition.json Adds Azure Marketplace-style createUiDefinition wizard for deployment.
Solutions/Claroty xDome CCF/Hunting Queries/ClarotyXDomeOtConfigChanges.yaml Adds hunting query for OT configuration/mode changes.
Solutions/Claroty xDome CCF/Hunting Queries/ClarotyXDomeInternetExposedOtDevices.yaml Adds hunting query for internet-exposed OT/IoT devices.
Solutions/Claroty xDome CCF/Hunting Queries/ClarotyXDomeInsecureProtocols.yaml Adds hunting query for insecure protocol usage.
Solutions/Claroty xDome CCF/Data/Solution_ClarotyXDomeCCF.json Adds solution package manifest listing assets and version.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/table_ClarotyXDomeVulnerability_CL.json Adds custom table resource for vulnerabilities.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/table_ClarotyXDomeOTEvent_CL.json Adds custom table resource for OT activity events.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/table_ClarotyXDomeDevice_CL.json Adds custom table resource for device inventory.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/table_ClarotyXDomeDeviceVulnerability_CL.json Adds custom table resource for device-vulnerability relations.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/table_ClarotyXDomeDeviceAlert_CL.json Adds custom table resource for device-alert relations.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/table_ClarotyXDomeAuditLog_CL.json Adds custom table resource for audit log.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/table_ClarotyXDomeAlert_CL.json Adds custom table resource for alerts.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/ClarotyXDomeCCF_PollingConfig.json Adds CCF poller resources for all data types.
Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/ClarotyXDomeCCF_ConnectorDefinition.json Adds the connector definition UI/behavior metadata.
Solutions/Claroty xDome CCF/Analytic Rules/ClarotyXDomeKevOnOtDevice.yaml Adds scheduled rule for KEV on OT devices.
Solutions/Claroty xDome CCF/Analytic Rules/ClarotyXDomeHighSeverityAlert.yaml Adds scheduled rule for high/critical severity device alerts.
Suppressed comments (1)

Solutions/Claroty xDome CCF/Data Connectors/ClarotyXDomeCCF_ccf/table_ClarotyXDomeAlert_CL.json:119

  • The Alerts table schema uses ID, UpdatedTime, and Category, while the ClarotyXDomeAlert parser/workbook content references AlertId, AlertUpdated, and AlertCategory. This mismatch will break the workbook tiles/visualizations and parser function results. Standardize the schema vs. parser naming (either update the table columns to the parser names, or update all downstream KQL to the table names).

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +4 to +5
"apiVersion": "2024-09-01",
"name": "[[concat(parameters('workspace'), '/Microsoft.SecurityInsights/ClarotyXDomeAlert', uniqueString(parameters('friendlyName')))]",
"dataType": "ClarotyXDomeAlert_CL",
"auth": {
"type": "APIKey",
"ApiKey": "[[parameters('apiKey')]",
"ApiKeyIdentifier": "Bearer"
},
"request": {
"apiEndpoint": "[[concat(parameters('apiRootUrl'), '/api/v1/alerts/')]",
"dataType": "Alerts"
}
},
"condition": "[[contains(parameters('selectedDataTypes'), 'ClarotyXDomeAlert_CL')]"
"type": "string"
},
{
"name": "UID",
Comment on lines +1 to +3
| **Version** | **Date Modified (DD-MM-YYYY)** | **Change History** |
|-------------|--------------------------------|--------------------|
| 3.0.0 | 13-08-2026 | Initial submission of the Claroty xDome CCF solution, including connector definition, DCR and polling configuration, seven destination tables, parsers, workbook, analytic rules, hunting queries, sample data, and package artifacts for deployment. |
Comment on lines +2 to +36
"location": {
"type": "string",
"minLength": 1,
"defaultValue": "[resourceGroup().location]",
"metadata": {
"description": "Not used, but needed to pass arm-ttk test `Location-Should-Not-Be-Hardcoded`. We instead use the `workspace-location` which is derived from the LA workspace"
}
},
"workspace-location": {
"type": "string",
"defaultValue": "",
"metadata": {
"description": "[concat('Region to deploy solution resources -- separate from location selection',parameters('location'))]"
}
},
"workspace": {
"defaultValue": "",
"type": "string",
"metadata": {
"description": "Workspace name for Log Analytics where Microsoft Sentinel is setup"
}
},
"resourceGroupName": {
"type": "string",
"defaultValue": "[resourceGroup().name]",
"metadata": {
"description": "resource group name where Microsoft Sentinel is setup"
}
},
"subscription": {
"type": "string",
"defaultValue": "[last(split(subscription().id, '/'))]",
"metadata": {
"description": "subscription id where Microsoft Sentinel is setup"
}
ActorUsername = Username,
ActorUsernameType = 'Simple',
ActorDisplayName = UserDisplayName,
SrcIpAddr = '',
Comment on lines +107 to +110
IpAddr = SrcIpAddr
| where (eventresult == '*' or EventResult =~ eventresult)
and (array_length(eventtype_in) == 0 or EventType in~ (eventtype_in))
and (array_length(srcipaddr_has_any_prefix) == 0 or has_any_ipv4_prefix(SrcIpAddr, srcipaddr_has_any_prefix))
Comment on lines +39 to +42
- entityType: Host
fieldMappings:
- identifier: HostName
columnName: DeviceUid
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

New Solution For new Solutions which are new to Microsoft Sentinel

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants