Skip to content

New BigID DSPM CCF connector#12929

Merged
rahul0216 merged 5 commits into
Azure:masterfrom
mhebrard-bigid:bigid-ccf-connector
Oct 14, 2025
Merged

New BigID DSPM CCF connector#12929
rahul0216 merged 5 commits into
Azure:masterfrom
mhebrard-bigid:bigid-ccf-connector

Conversation

@mhebrard-bigid
Copy link
Copy Markdown
Contributor

Required items, please complete

Change(s):

  • New BigID DSPM CCF connector

Testing Completed:

  • Yes, via manual testing of the mainTemplate.json and the createUiDefinition

@mhebrard-bigid mhebrard-bigid requested review from a team as code owners October 7, 2025 09:36
@mhebrard-bigid
Copy link
Copy Markdown
Contributor Author

@microsoft-github-policy-service agree [company="bigid"]

@mhebrard-bigid
Copy link
Copy Markdown
Contributor Author

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

@mhebrard-bigid mhebrard-bigid marked this pull request as draft October 7, 2025 09:39
@mhebrard-bigid mhebrard-bigid changed the title NEw BigID DSPM CCF connector New BigID DSPM CCF connector Oct 7, 2025
@v-shukore v-shukore added the New Solution For new Solutions which are new to Microsoft Sentinel label Oct 8, 2025
@mhebrard-bigid mhebrard-bigid marked this pull request as ready for review October 9, 2025 16:32
@mhebrard-bigid
Copy link
Copy Markdown
Contributor Author

@v-shukore @v-maheshbh, please trigger the workflows. Thank you in advance

@mhebrard-bigid
Copy link
Copy Markdown
Contributor Author

I've been looking into the CI checks that were flagged, and I wanted to share a couple of observations.

Regarding the armttk flags:

  • For the resourceIds flag, it appears this might be related to the packagingv3 structure.
  • For the 'not empty properties' check, my understanding is that an empty string is the required value in this specific use case. Would you be open to re-evaluating this check for scenarios like this one?

Regarding the Solution Validation:

  • I noticed the validation is failing on the solution's domain. It seems there might be a small discrepancy between the domain list used in the CI pipeline (link to CI list) and the categories in the official Microsoft documentation (link to docs). It could be beneficial for us to sync these to ensure our validations are using the latest official guidance.

@v-maheshbh
Copy link
Copy Markdown
Contributor

Hi @mhebrard-bigid
Kindly review the following feedback:

offerId Format:
Update the offerId to follow the correct format:
azure-sentinel-solution-solutionName

Release Notes Version:
Update the version in the ReleaseNotes file from 1.0.0 to 3.0.0.

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

ARM-TTK Validation Failure:
The validation is failing due to an empty property value:
"ApiKeyIdentifier": ""
Please ensure all required fields are populated with valid data.

Solution Validation – SolutionMetadata:
Confirm that the domains section within the SolutionMetadata file is correctly defined and complete.

Data Connector:
Kindly share details of the running data connector instance for validation and testing purposes.

Please address these items at your earliest convenience. Let me know if you have any questions or need further clarification.

Thanks!

- added missing logo
- Small corrections on description fields
- Modified version in ReleaseNotes
- Aligned domains in solution metadata based on CI expectations
- Modified offerId to match expected format
- Modified basePath in solution_bigid.json
@mhebrard-bigid
Copy link
Copy Markdown
Contributor Author

@v-maheshbh , thank you for your feedback.

Please note that "ApiKeyIdentifier": "" needs to be empty, as otherwise a non-value means token (see documentation)

Please find attached the screenshots of the validation testing environment with this latest version, all other points were addressed. Please proceed with the review.

Screenshot 2025-10-10 at 15 46 01 Screenshot 2025-10-10 at 15 50 43 Screenshot 2025-10-10 at 15 51 18

@v-maheshbh
Copy link
Copy Markdown
Contributor

Hi @mhebrard-bigid Logo validation failed due to incorrect format. The logo must be in SVG format. Please change the file format and ensure that the SVG includes an id property containing a 16-character unique GUID and then repackage the solution to reflect these changes.

Thanks!

@rahul0216 rahul0216 merged commit c5220e0 into Azure:master Oct 14, 2025
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

New Solution For new Solutions which are new to Microsoft Sentinel

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants