Repository navigation
feat: migrate Fortinet FortiNDR Cloud, VMware Carbon Black Cloud, and Cisco Duo Security to Defender XDR - #15499
Open
Alon Karmona (alon-karmona1) wants to merge 2 commits into
Conversation
… Duo Security to XDR (v3.2.2) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8a658623-87aa-4754-bc2d-dbee1b6e8a34
github-actions
Bot
added
1P Solution
v-amolpatil
reviewed
Oct 30, 2026
Contributor
There was a problem hiding this comment.
Alon Karmona (@alon-karmona1) Please update the version as pipeline is failing for this.
Solutions/Fortinet FortiNDR Cloud/Analytic Rules/FortiNDR_Events_Detected.yaml is a detection
You **did not** change the version in this file: Solutions/Fortinet FortiNDR Cloud/Analytic Rules/FortiNDR_Events_Detected.yaml.
v-amolpatil
reviewed
Oct 30, 2026
Include the EventType string column in the Fortinet FortiNDR Cloud function result schema.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
End-to-end Defender XDR migration and V3.1 packaging (
v3.2.2) for 3 solutions:Solutions/Fortinet FortiNDR Cloud)Solutions/VMware Carbon Black Cloud)Solutions/CiscoDuoSecurity)1. Fortinet FortiNDR Cloud (
v3.2.2)XDR Detections/FortiNDR_Events_Detected.yaml): Converted Analytic Rule (1/1Defender XDR Custom Detection) and validated across static schema, Sentinel SDK, Sentinel Log Analytics, and live Graph Advanced Hunting (1/1passed).XDR Workbooks/FortinetFortiNdrCloudWorkbook.json): ConvertedWorkbooks/FortinetFortiNdrCloudWorkbook.jsonto Defender XDR Workbook (notebookschema) and registered inData/Solution_FortiNdrCloud.json.Sample Data/&Sample Data/Tables/): Added schema-valid synthetic sample data across all referenced tables (FortiNDRCloudEvents_CL,CommonSecurityLog).Package/): Updated solution version to3.2.2inData/Solution_FortiNdrCloud.json,SolutionMetadata.json, andReleaseNotes.md; packaged V3.1mainTemplate.json,createUiDefinition.json,testParameters.json, and3.2.2.zip.Evidence/):DeployCustomDetection=true,DeployDefenderWorkbook=true, rules disabled) and verified live read-back of Sentinel rules, workbooks, and Graph Custom Detections.pr-qualify --mode full --is-migrationverification with0waivers:Qualified(77 / 77applicable checks passed,4N/A,0failed,0waived)2. VMware Carbon Black Cloud (
v3.2.2)XDR Detections/*.yaml): Converted both Analytic Rules (CriticalThreatDetected.yaml,KnownMalwareDetected.yaml) to Defender XDR Custom Detections (2/2passed).XDR Workbooks/VMwareCarbonBlack.json): ConvertedWorkbooks/VMwareCarbonBlack.jsonto Defender XDR Workbook (notebookschema) and registered inData/Solution_VMware Carbon Black Cloud.json.Sample Data/&Sample Data/Tables/): Added schema-valid synthetic sample data across all referenced tables (CarbonBlackEvents_CL,CarbonBlackNotifications_CL,CarbonBlackAuditLogs_CL).Package/): Updated solution version to3.2.2inData/Solution_VMware Carbon Black Cloud.json,SolutionMetadata.json, andReleaseNotes.md; packaged V3.1mainTemplate.json,createUiDefinition.json,testParameters.json, and3.2.2.zip.Evidence/):DeployCustomDetection=true,DeployDefenderWorkbook=true, rules disabled) and verified live read-back of Sentinel rules, workbooks, playbooks, and Graph Custom Detections.pr-qualify --mode full --is-migrationverification with0waivers:Qualified(76 / 76applicable checks passed,5N/A,0failed,0waived)3. Cisco Duo Security (
v3.2.2)XDR Detections/*.yaml): Converted all 10 Analytic Rules (10/10Defender XDR Custom Detections) and validated across static schema, Sentinel SDK, Sentinel Log Analytics, and live Graph Advanced Hunting (10/10passed).XDR Workbooks/CiscoDuo.json): ConvertedWorkbooks/CiscoDuo.jsonto Defender XDR Workbook (notebookschema) and registered inData/Solution_CiscoDuoSecurity.json.Sample Data/&Sample Data/Tables/): Added schema-valid synthetic sample data acrossCiscoDuo_CL.Package/): Updated solution version to3.2.2inData/Solution_CiscoDuoSecurity.json,SolutionMetadata.json, andReleaseNotes.md; packaged V3.1mainTemplate.json,createUiDefinition.json,testParameters.json, and3.2.2.zip.Evidence/):DeployCustomDetection=true,DeployDefenderWorkbook=true, rules disabled) and verified live read-back of Sentinel rules, workbooks, and all 10 Graph Custom Detections.pr-qualify --mode full --is-migrationverification with0waivers:Qualified(77 / 77applicable checks passed,4N/A,0failed,0waived)