Update NordStellar connector to version 3.0.1 - #14945
Conversation
- Set `TimeGenerated` to ingestion time to prevent rejection of historical events by retention checks. - Introduced a new `EventTime` column to preserve the original event timestamp. - Fixed `AssetType` for `CONSUMER_CREDENTIAL` events to be `DOMAIN` instead of the credential origin. - Updated documentation and queries to reflect these changes.
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the NordStellar Sentinel solution to v3.0.1, adjusting the DCR transform so historical events aren’t dropped due to ingestion-time limits while preserving original event timestamps in a new EventTime column.
Changes:
- Bumped solution and connector versions from 3.0.0 to 3.0.1 across packaging artifacts.
- Updated DCR transform to set
TimeGeneratedto ingestion time and addedEventTimefor original timestamps. - Adjusted
CONSUMER_CREDENTIALmapping (AssetType) and refreshed documentation/sample queries/schema descriptions.
Reviewed changes
Copilot reviewed 6 out of 8 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| Solutions/NordStellar/ReleaseNotes.md | Adds 3.0.1 release notes describing ingestion-time change, EventTime, and AssetType fix. |
| Solutions/NordStellar/Package/mainTemplate.json | Bumps versions, updates connector docs/sample queries, updates DCR transform and table schema to include EventTime. |
| Solutions/NordStellar/Data/Solution_NordStellar.json | Bumps solution version to 3.0.1. |
| Solutions/NordStellar/Data Connectors/NordStellar_ccf/table.json | Adds EventTime column and updates column descriptions for new semantics. |
| Solutions/NordStellar/Data Connectors/NordStellar_ccf/connectorDefinition.json | Updates description/sample queries/instructions to reference EventTime and ingestion-time semantics. |
| Solutions/NordStellar/Data Connectors/NordStellar_ccf/DCR.json | Updates transform KQL to set TimeGenerated to now(), add EventTime, and adjust AssetType mapping. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Hi mantasg-nordsec, Also, please share a screenshot showing that the connector is running successfully. If possible, please also shorten the release note description to make it more concise. Thanks |
|
Hi v-atulyadav ,
Let me know if there's anything else missing, thanks! |

Change(s):
NordStellar_CLDCR transform now setsTimeGeneratedto ingestion time instead of the event's original timestamp (date_added/detected_at). Historical events with timestamps older than the Log Analytics ingestion-time limit (~2 days) were previously rejected.EventTimedatetime column to theNordStellar_CLtable schema, preserving the original event timestamp (detected_atfor attack-surface/domain-permutation events,date_addedotherwise, envelopetimeas fallback).AssetTypeforCONSUMER_CREDENTIALevents: nowDOMAIN(the customer-owned domain inasset_value) instead of the credential origin (MALWARE_INFECTION/COMBO_LIST) leaking in fromsource_type.createSolutionV3.ps1); newPackage/3.0.1.zip.Reason for Change(s):
date_addedmonths or years in the past) had those events silently dropped becauseTimeGeneratedfell outside the allowed ingestion window. Using ingestion time guarantees delivery whileEventTimeretains the original timestamp for querying. This aligns the Sentinel connector with the behavior of NordStellar's other SIEM integrations.AssetTypeforCONSUMER_CREDENTIALevents was semantically wrong (showed the leak origin rather than the asset type).Version Updated:
Testing Completed:
IDs Should Be Derived From ResourceIDsfailure is the known false positive on tool-generatedcontentProductIdexpressions).date_added,detected_at,CONSUMER_CREDENTIALasset mapping); only operators from the supported transformation KQL subset are used.NordStellar_CLschema gains theEventTimecolumn, and pushed test events land withTimeGenerated= ingestion time andEventTime= original event timestamp.Checked that the validations are passing and have addressed any issues that are present: