Add panorays solution

[shayn-creator]

Required items, please complete

Change(s):

• Added the new Panorays solution scaffold to the repository (SolutionMetadata.json, Solution_Panorays.json, ReleaseNotes.md, etc.).
• Addressed Copilot validation feedback regarding publisher, tier, versioning, and file paths.

Reason for Change(s):

• To allow Microsoft Sentinel users to integrate Panorays cyber risk data directly into their security workflows.

Version Updated:

• N/A (This is a new solution, not an update to an existing detection rule).

Testing Completed:

• Yes. Validated JSON formatting, paths, and CCF connector definitions.

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

• Yes.

[shayn-creator]

@shayn-creator 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).
   “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.

6. 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.
7. 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.
8. 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.
9. 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.
10. 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.

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

[v-maheshbh]

Hi @shayn-creator

BasePath Format:
Modify the BasePath to the following structure:
C:\GitHub\Azure-Sentinel\solutions\Solution Name

and Please refer to the CCF solution provided below and ensure the files are renamed as per the solution.

https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Cloudflare%20CCF

Thanks!

[shayn-creator]

Hi @v-maheshbh ,
Just a quick follow-up! I've implemented the requested changes for the BasePath and the CCF naming conventions, and all CI/CD validations are passing green.
Could you let me know if there is anything else needed on my end, or if this is ready for your final review and merge? Thanks again for your help!

[v-maheshbh]

Hi @shayn-creator

Kindly update the logo path in the data file to align with the master branch. Please refer to an existing solution for reference.

thanks!

[shayn-creator]

Hi, Done

[shayn-creator]

Hi team,
it looks like the playbooksValidator pipeline failed because the GitHub Actions runner hit an unauthenticated GitHub API rate limit (403 API rate limit exceeded).
Could a maintainer please trigger a re-run for me?
Many thanks, Shay

[v-maheshbh]

Hi @shayn-creator

Kindly attach a testing screenshot of the CCF data connector in the connected state for reference.

Thanks!

[shayn-creator]

Please see the screenshots attached

[Copilot]

Pull request overview

Adds a new Panorays solution scaffold to the repository, including the solution metadata, solution data manifest, and initial release notes.

Changes:

• Added Solutions/Panorays/SolutionMetadata.json to define solution identity, versions, publisher/offer info, and support metadata.
• Added Solutions/Panorays/Data/Solution_Panorays.json and Solutions/Panorays/ReleaseNotes.md to describe packaged assets and release history.
• (Changes under Solutions/**/Data Connectors/** and Solutions/**/Package/** are present but intentionally not reviewed per repo guidance.)

Reviewed changes

Copilot reviewed 13 out of 14 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
Solutions/Panorays/SolutionMetadata.json	Introduces core solution metadata (name/IDs/version/publisher/support/categories).
Solutions/Panorays/ReleaseNotes.md	Adds initial release notes entry for the solution.
Solutions/Panorays/Package/testParameters.json	Not reviewed (ignored path: Solutions/**/Package/**).
Solutions/Panorays/Package/mainTemplate.json	Not reviewed (ignored path: Solutions/**/Package/**).
Solutions/Panorays/Package/createUiDefinition.json	Not reviewed (ignored path: Solutions/**/Package/**).
Solutions/Panorays/Data/Solution_Panorays.json	Adds the solution “manifest” describing included assets and packaging flags.
Solutions/Panorays/Data Connectors/requirements.txt	Not reviewed (ignored path: Solutions/**/Data Connectors/**).
Solutions/Panorays/Data Connectors/Panorays_CCF/createUiDefinition.json	Not reviewed (ignored path: Solutions/**/Data Connectors/**).
Solutions/Panorays/Data Connectors/Panorays_CCF/Panorays_table.json	Not reviewed (ignored path: Solutions/**/Data Connectors/**).
Solutions/Panorays/Data Connectors/Panorays_CCF/Panorays_connectorDefinition.json	Not reviewed (ignored path: Solutions/**/Data Connectors/**).
Solutions/Panorays/Data Connectors/Panorays_CCF/Panorays_PollerConfig.json	Not reviewed (ignored path: Solutions/**/Data Connectors/**).
Solutions/Panorays/Data Connectors/Panorays_CCF/Panorays_DCR.json	Not reviewed (ignored path: Solutions/**/Data Connectors/**).
Solutions/Panorays/Data Connectors/Panorays_CCF/DeployInstance.json	Not reviewed (ignored path: Solutions/**/Data Connectors/**).

[Copilot]

The offerId / PackageId values contain a likely typo (panprays vs panorays). These IDs are used for publishing/packaging and should match the solution name/folder consistently (e.g., ...-panorays). Update both fields to the correct, consistent identifier.

Suggested change

	"offerId": "azure-sentinel-solution-panprays",
	"PackageId": "azuresentinel.azure-sentinel-panprays",
	"offerId": "azure-sentinel-solution-panorays",
	"PackageId": "azuresentinel.azure-sentinel-panorays",

[Copilot]

The solution version in SolutionMetadata.json (1.0.0) conflicts with the version used elsewhere in this PR (e.g., Solutions/Panorays/Data/Solution_Panorays.json and Solutions/Panorays/ReleaseNotes.md show 3.0.0). Use a single, consistent solution/package version across solution metadata, solution data, and release notes to avoid validation and packaging inconsistencies.

Suggested change

	"SolutionVersion":"1.0.0",
	"SolutionVersion":"3.0.0",

[v-maheshbh]

Hi @shayn-creator

Recently, SolutionMetadata was modified. Kindly repackage the solution so the updates are reflected in mainTemplate.json.
Please double‑check the changes made to offerId and other metadata fields, regenerate the package, and ensure the mainTemplate.json outside the ZIP matches the mainTemplate.json inside the ZIP.

"BasePath": "C:\GitHub\Azure-Sentinel\solutions\Panorays" this is correct path.

Thanks!

[shayn-creator]

Hello @v-maheshbh ,

Thank you for the feedback. I have updated the PR with the following changes to align with the latest Microsoft Sentinel solution requirements.
Note: I have used the V3 solution framework to build and package this version (3.0.0), ensuring full compatibility with the latest ingestion standards.
The solution has been verified with a successful end-to-end deployment and data ingestion in a live Sentinel environment. Please let me know if any further adjustments are required.

Many Thanks and best regards,
Shay

[v-maheshbh]

Hi @shayn-creator

Kindly rename the file ccpPanoraysCompanyFindingPOC.json to Panorays_ConnectorDefinition.json and update the same in the data file accordingly.
and Also, ensure that only the connector definition is added under the "Data Connectors" section in the data file.
and repackage the solution.

Thanks!

[shayn-creator]

Thank you @v-maheshbh. I have addressed all the feedback:
Renamed the connector definition file and updated all internal references.
Cleaned up the Data Connectors section in the manifest.
Repackaged the 3.0.0.zip to reflect these changes.
Ready for another look!

[v-maheshbh]

Hi @shayn-creator

Invalid domains: [Security - Other] provided.
Please refer link https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sentinel/sentinel-solutions.md?msclkid=9a240b52b11411ec99ae6736bd089c4a#categories-for-microsoft-sentinel-out-of-the-box-content-and-solutions for valid Domains and Verticals.

Thanks!

[shayn-creator]

Thank you for the clarification, @v-maheshbh
I have updated the domain to Security - Vulnerability Management, as it best describes the 'Findings' data provided by Panorays.