Add HoneyForge Threat Detection solution v1.0.0 - #14715
Conversation
|
@microsoft-github-policy-service agree company="BUI" |
|
@microsoft-github-policy-service agree company="BUI"
Sensitivity: Business - General
From: microsoft-github-policy-service[bot] ***@***.***>
Sent: Monday, 20 July 2026 14:20
To: Azure/Azure-Sentinel ***@***.***>
Cc: j.doe ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/Azure-Sentinel] Add HoneyForge Threat Detection solution v1.0.0 (PR #14715)
[https://avatars.githubusercontent.com/in/95686?s=20&v=4]microsoft-github-policy-service[bot] left a comment (Azure/Azure-Sentinel#14715)<#14715 (comment)>
@johndoebui<https://github.com/johndoebui> please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
* (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
* (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term "You" includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement ("Agreement") is agreed to by the party signing below ("You"),
and conveys certain license rights to Microsoft Corporation and its affiliates ("Microsoft") for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.
1. Definitions.
"Code" means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
"Project" means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org<http://www.opensource.org/>).
"Submit" is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as "Not a Submission."
"Submission" means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project's written
guidelines concerning Submissions.
4. Your Employer. References to "employer" in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term "You" in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
5. Licenses.
* Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
* Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
* Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
1. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
3. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.
-
Reply to this email directly, view it on GitHub<#14715?email_source=notifications&email_token=A75LLW472O4JJLW454NGO7T5FYE7TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGIYTINRTGI22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5022146325>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A75LLW2M73FVBIN4MOLYLM35FYE7TAVCNFSNUABFKJSXA33TNF2G64TZHMYTINJRHAZTENZRHNEXG43VMU5TIOJSHA4DKOBZGA22C5QC>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/A75LLW7BSBBJYHAQUGOO3635FYE7TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGIYTINRTGI22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/A75LLW443AHM5NLWTIJFLLL5FYE7TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGIYTINRTGI22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
BUI Disclaimer: This email and the information contained herein is BUI confidential and is protected by law. Use of this information or this email by any person for any purposes other than that for which it is intended is prohibited and may result in civil and/or criminal liability. This email is not to be shared with any 3rd parties not included within this email, without written consent of its Author
|
|
@microsoft-github-policy-service agree [company="BUI"]
Sensitivity: Business - General
From: microsoft-github-policy-service[bot] ***@***.***>
Sent: Monday, 20 July 2026 14:20
To: Azure/Azure-Sentinel ***@***.***>
Cc: j.doe ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/Azure-Sentinel] Add HoneyForge Threat Detection solution v1.0.0 (PR #14715)
[https://avatars.githubusercontent.com/in/95686?s=20&v=4]microsoft-github-policy-service[bot] left a comment (Azure/Azure-Sentinel#14715)<#14715 (comment)>
@johndoebui<https://github.com/johndoebui> please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
* (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
* (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term "You" includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement ("Agreement") is agreed to by the party signing below ("You"),
and conveys certain license rights to Microsoft Corporation and its affiliates ("Microsoft") for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.
1. Definitions.
"Code" means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
"Project" means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org<http://www.opensource.org/>).
"Submit" is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as "Not a Submission."
"Submission" means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project's written
guidelines concerning Submissions.
4. Your Employer. References to "employer" in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term "You" in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
5. Licenses.
* Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
* Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
* Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
1. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
3. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.
-
Reply to this email directly, view it on GitHub<#14715?email_source=notifications&email_token=A75LLW472O4JJLW454NGO7T5FYE7TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGIYTINRTGI22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5022146325>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A75LLW2M73FVBIN4MOLYLM35FYE7TAVCNFSNUABFKJSXA33TNF2G64TZHMYTINJRHAZTENZRHNEXG43VMU5TIOJSHA4DKOBZGA22C5QC>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/A75LLW7BSBBJYHAQUGOO3635FYE7TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGIYTINRTGI22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/A75LLW443AHM5NLWTIJFLLL5FYE7TA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSGIYTINRTGI22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
BUI Disclaimer: This email and the information contained herein is BUI confidential and is protected by law. Use of this information or this email by any person for any purposes other than that for which it is intended is prohibited and may result in civil and/or criminal liability. This email is not to be shared with any 3rd parties not included within this email, without written consent of its Author
|
|
@microsoft-github-policy-service agree company="BUI" |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new Microsoft Sentinel Content Hub solution (“HoneyForge Threat Detection” v1.0.0) to ingest HoneyForge CEF/Syslog events and provide out-of-box detections, hunting, parsing, and operational visibility.
Changes:
- Introduces HoneyForge solution metadata, ARM package, and createUiDefinition for Content Hub V3 deployment.
- Adds workbook content for operational visibility (overview/timeline/top sources/fleet health/severity/protocol/off-hours).
- Adds an ASIM NetworkSession parser plus an NRT analytic rule and five hunting queries based on
CommonSecurityLog.
Reviewed changes
Copilot reviewed 12 out of 13 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| Solutions/HoneyForge/Workbooks/HoneyForge.json | New operational workbook queries and visualizations for HoneyForge activity. |
| Solutions/HoneyForge/SolutionMetadata.json | Defines the solution’s marketplace metadata, support info, and publish dates. |
| Solutions/HoneyForge/Parsers/HoneyForgeEvent.yaml | Adds ASIM NetworkSession parser function HoneyForgeEvent. |
| Solutions/HoneyForge/Package/mainTemplate.json | ARM template to deploy solution metadata + connector + rule + parser + queries + workbook. |
| Solutions/HoneyForge/Package/createUiDefinition.json | Installer UX definition to select Log Analytics workspace for deployment. |
| Solutions/HoneyForge/Hunting Queries/HoneyForge_TopAttackingSources.yaml | Hunting query to identify top attacking source IPs. |
| Solutions/HoneyForge/Hunting Queries/HoneyForge_RepeatedProbes.yaml | Hunting query to find repeat probes separated into sessions. |
| Solutions/HoneyForge/Hunting Queries/HoneyForge_OffHoursActivity.yaml | Hunting query for off-hours sensor activity. |
| Solutions/HoneyForge/Hunting Queries/HoneyForge_HighFrequency.yaml | Hunting query for burst/high-frequency interactions. |
| Solutions/HoneyForge/Hunting Queries/HoneyForge_FleetCoverage.yaml | Hunting query for per-sensor coverage/health. |
| Solutions/HoneyForge/Data Connectors/HoneyForge.json | Data connector definition + instructions to forward CEF syslog via Linux forwarder. |
| Solutions/HoneyForge/Analytic Rules/HoneyForge_DeceptionSensorInteraction.yaml | NRT analytic rule to alert on HoneyForge sensor interaction. |
| { | ||
| "type": "Microsoft.OperationalInsights/workspaces/providers/contentTemplates", | ||
| "apiVersion": "2023-04-01-preview", | ||
| "name": "[concat(parameters('workspace'),'/Microsoft.SecurityInsights/''795b6ec0-3e9a-4b12-8f4d-1a2b3c4d5e6f-hq-',variables('_solutionId'))]", |
There was a problem hiding this comment.
Hi v-shukore, I've addressed all 3 CI failures from the previous run. Here's a summary of what was fixed:
1. KQL Validations (fixed in previous session)
- Moved
FunctionNamefrom insideFunctionParamsto the top-level parser function definition - Changed
ParserParamsfrom a single-line string to a proper YAML list format
2. Solution Validations — incorrect product branding
HoneyForge.json: replaced "Sentinel" → "Microsoft Sentinel" in two places in the data connector descriptionmainTemplate.json: applied the same branding fixes (the package file embeds the connector text)
3. ARM-TTK Validations — null values in package files
createUiDefinition.json: replaced"label": nullwith"label": "HoneyForge"and"text": nullwith a proper description string in the workbook section (these were generated as null by the V3 packaging tool due to missing workbook metadata)mainTemplate.json: replaced"defaultValue": nullwith"defaultValue": "HoneyForge"for theworkbook1-nameparameter
All fixes have been committed to the add-honeyforge-solution branch. Could you please approve the workflow run so CI can validate the changes? Thank you!
| { | ||
| "type": "Microsoft.OperationalInsights/workspaces/providers/contentTemplates", | ||
| "apiVersion": "2023-04-01-preview", | ||
| "name": "[concat(parameters('workspace'),'/Microsoft.SecurityInsights/''e4905b78-2c3d-4e5f-9a0b-1c2d3e4f5a6b-hq-',variables('_solutionId'))]", |
| { | ||
| "type": "Microsoft.OperationalInsights/workspaces/providers/contentTemplates", | ||
| "apiVersion": "2023-04-01-preview", | ||
| "name": "[concat(parameters('workspace'),'/Microsoft.SecurityInsights/''7bf37318-4d5e-6f7a-0b1c-2d3e4f5a6b7c-hq-',variables('_solutionId'))]", |
| { | ||
| "type": "Microsoft.OperationalInsights/workspaces/providers/contentTemplates", | ||
| "apiVersion": "2023-04-01-preview", | ||
| "name": "[concat(parameters('workspace'),'/Microsoft.SecurityInsights/''73cf5ff5-5e6f-7a8b-1c2d-3e4f5a6b7c8d-hq-',variables('_solutionId'))]", |
| { | ||
| "type": "Microsoft.OperationalInsights/workspaces/providers/contentTemplates", | ||
| "apiVersion": "2023-04-01-preview", | ||
| "name": "[concat(parameters('workspace'),'/Microsoft.SecurityInsights/''5a15c525-6f7a-8b9c-2d3e-4f5a6b7c8d9e-hq-',variables('_solutionId'))]", |
| "type": 3, | ||
| "content": { | ||
| "version": "KqlItem/1.0", | ||
| "query": "CommonSecurityLog\n| where {TimeRange}\n| where DeviceVendor =~ \"BUI\"\n| where DeviceProduct =~ \"HoneyForge\"\n| extend CustomerID = tostring(DeviceCustomString2)\n| where \"{CustomerID}\" == \"All\" or CustomerID =~ \"{CustomerID}\"\n| summarize\n TotalEvents = count(),\n UniqueSources = dcount(SourceIP),\n SensorsHit = dcount(iff(isempty(tostring(DeviceCustomString3)), tostring(Computer), tostring(DeviceCustomString3))),\n CustomersAffected = dcount(CustomerID)\n| extend\n TotalEventsLabel = tostring(TotalEvents),\n UniqueSourcesLabel = tostring(UniqueSources),\n SensorsHitLabel = tostring(SensorsHit),\n CustomersLabel = tostring(CustomersAffected)", |
| "type": 3, | ||
| "content": { | ||
| "version": "KqlItem/1.0", | ||
| "query": "CommonSecurityLog\n| where {TimeRange}\n| where DeviceVendor =~ \"BUI\"\n| where DeviceProduct =~ \"HoneyForge\"\n| extend CustomerID = tostring(DeviceCustomString2)\n| where \"{CustomerID}\" == \"All\" or CustomerID =~ \"{CustomerID}\"\n| summarize Events = count() by bin(TimeGenerated, 1h)\n| sort by TimeGenerated asc", |
| "isWizard": false, | ||
| "basics": { | ||
| "description": "<img src=\"https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Logos/HoneyForgeLogo.svg\" width=\"75px\" height=\"75px\">\n\n**Note:** Please refer to the following before installing the solution:\n\n• Review the solution [Release Notes](https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/HoneyForge/ReleaseNotes.md)\n\n • There may be [known issues](https://aka.ms/sentinelsolutionsknownissues) pertaining to this Solution.\n\n[HoneyForge](https://honeyforge.tech) is a hardware-based honeypot SaaS platform that deploys deception sensors across your network to detect malicious activity in real time. This solution ingests HoneyForge sensor events into Microsoft Sentinel via CEF syslog and provides an analytic rule, hunting queries, an ASIM parser, and an operational workbook.\n\n**Data Connectors:** 1, **Analytic Rules:** 1, **Hunting Queries:** 5, **Parser:** 1, **Workbooks:** 1\n\n[Learn more about Microsoft Sentinel](https://aka.ms/azuresentinel) | [Learn more about Solutions](https://aka.ms/azuresentinelsolutionsdoc)", | ||
| "subscription": { "resourceProviders": ["Microsoft.OperationsManagement/solutions", "Microsoft.OperationalInsights/workspaces/providers/alertRules", "Microsoft.Insights/workbooks", "Microsoft.Logic/workflows"] }, |
| // Apply dvcaction filter (no action in HoneyForge events, pass-through) | ||
| | where (array_length(dvcaction) == 0) | ||
| // Apply eventresult filter | ||
| | where (eventresult == '*' or EventResult =~ eventresult) |
…der, parser params
…ASCII, connector permissions
|
Hi johndoebui, please check copilot review comments and implement if required also resolve branch conflicts. Thanks! |
… add-honeyforge-solution
|
Hi v-shukore, thanks for the review! Copilot comments: All 9 comments are showing as "Outdated" — the specific lines they referenced were updated in subsequent commits (33feecf and c816951). No further changes are required as the underlying issues were addressed (ARM resource names, workbook TimeRange parameter, createUiDefinition providers, and parser filter logic). Branch conflicts: Resolved — merged upstream master into the branch (commit 192875a). ValidConnectorIds.json has been updated with both the upstream additions and our HoneyForge entry. CI is running on the latest commit. Thanks! |
|
Hi johndoebui, I noticed you’ve created three new solutions. To keep things clear, please include only one solution in this PR and raise separate PRs for the other two. Also, when creating the new solutions, please create just one package with version 3.0.0 and commit the changes. Thanks! |
84245cd to
63e39cd
Compare
|
Hi v-shukore, thanks for the feedback! I've addressed both points:
Please let me know if anything else needs adjusting. Thanks! |
|
Hi johndoebui, please resolve branch conflicts. Thanks! |
|
Hi v-shukore, branch conflicts resolved — merged latest upstream master into the branch. ValidConnectorIds.json now includes 340 entries (339 upstream + HoneyForge). No other conflicts. Please approve the workflow run when you get a chance. Thanks! |
|
Hi johndoebui, please use the V3 tool to package this new solution and create a new package at version 3.0.0. Please let us know which type of connector you are using for this solution. We would also be happy to help migrate your solution to CCF. To review the available options, please contact the Microsoft Sentinel Partners at AzureSentinelPartner@microsoft.com. If this connector is needed, please obtain approval from the azure app assure team by email and share the screenshot with us so we can proceed. Thanks! |
|
Hi v-shukore, fixes committed for all CI failures:
Note: DetectionTemplateSchemaValidation fails on vmw-sdwan-nsd-cssdown.yaml (pre-existing Azure master issue, not our PR). Please approve the workflow run. Thanks! |
|
Hi v-shukore, thanks for your patience. We've pushed two additional fixes to address the remaining CI failures: 1. 2. 3. 4. Could you please approve the workflow run so the full CI suite can execute against the latest commits? We want to confirm all checks pass before requesting your final review. Thank you! |
|
Hi johndoebui, The solution is missing the data file, so please add it, add all contents into that file, and repackage it using the V3 tool. For clarity, you can refer to the structure of any solution in the sentinel repo. since this solution includes a workbook, please add workbookmetadata for the newly added workbook at the location below Also, please clean up the metadata file by removing any unnecessary fields and keep only the required ones. Also, please let us know which type of connector you are using for this solution. We would also be happy to help migrate your solution to CCF. To review the available options, please contact the Microsoft Sentinel Partners at AzureSentinelPartner@microsoft.com. If this connector is needed, please obtain approval from the azure app assure team by email and share the screenshot with us so we can proceed. Thanks! |
|
Hi v-shukore, Thanks for the continued feedback. Here's our full status: Connector type: HoneyForge uses a CEF connector (CommonSecurityLog / syslog). The data type is Changes being pushed now:
Workbook preview images: We will provide V3 repackaging: We are aware of the V3 tool requirement. Given that all content item changes are correctly reflected in the mainTemplate.json, could you confirm whether a full V3 repackage is strictly required, or whether the manually-corrected mainTemplate is acceptable for this submission? Thank you! |
|
Hi johndoebui, For V3 tool packaging, generating maintemplate manually is acceptable, but the manual process can sometimes miss content. That is why we recommend using the V3 tool to generate the package. ZIP package generation is mandatory, because when you move this solution to Partner Center, the ZIP package must be uploaded there. Also, any preview images you add to workbookmetadata should be added in the location below as well. Please share screenshots of the running data connector here for reference. Also, please clean up the metadata file by removing any unnecessary fields you can take reference of any solution from repo and keep only the required ones and check the validation failures. |
ecfe529 to
d3b8ddb
Compare
…lution # Conflicts: # .script/tests/detectionTemplateSchemaValidation/ValidConnectorIds.json
|
Hi v-shukore, pushed one more fix — converted the parser's |


Change(s):
Reason for Change(s):
Version Updated:
Testing Completed:
Checked that the validations are passing and have addressed any issues that are present: