[Synqly][Solution] Initial version of the Synqly Integration Connector

[lkwdwrd]

Change(s):

• Add a new Synqly Integration Connector for streamlined Sentinel setup with Synqly integrations. This connector enables push-based ingestion of ASIM normalized events to 10 built-in ASIM tables.

Reason for Change(s):

• Add a new solution containing The Synqly connector

Testing Completed:

• Uploaded the generated template to our Sentinel instance using the az CLI, and ran our end-to-end test suite against it. Events are flowing to the correct built-in ASIM tables.

Checked that the validations are passing and have addressed any issues that are present:

• Local KQL checks not running on mac, but the changes should not cause problems. Will double check with Github actions.

[lkwdwrd]

@microsoft-github-policy-service agree company="Synqly"

[v-maheshbh]

Hi @lkwdwrd

Kindly refer to the CCF folder naming conventions and follow the solution structure provided below.https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Cloudflare%20CCF/Data%20Connectors/CloudflareLog_CCF

Thanks!

[lkwdwrd]

Hi @v-maheshbh, I appreciate you taking a look. I am not quite sure what naming conventions/structure you are referring to? The link you provided is to the Cloudflare data connector, but I don't see specific guidance there, and other than some casing differences, the pattern looks more or less the same. I see that it is using an uppercase "_CCF" as opposed to the lowercase "_ccf". This does appear to be the more common casing, but there are other providers in the repo with lower-case versions. Is there a specific naming convention mentioned somewhere? Is there folder structure guidance beyond what is in the Solutions Readme? As far as I understand currently, I'm following the solution folder structure as documented.

I did push an update to uppercase CCF if that is what you are referring to. Thank you!