Skip to content

Add new content packs to XDR users#42522

Merged
jbabazadeh merged 8 commits intomasterfrom
ae-fix-CRTX-207166
Jan 8, 2026
Merged

Add new content packs to XDR users#42522
jbabazadeh merged 8 commits intomasterfrom
ae-fix-CRTX-207166

Conversation

@BEAdi
Copy link
Copy Markdown
Contributor

@BEAdi BEAdi commented Jan 4, 2026 •
edited
Loading

Contributing to Cortex XSOAR Content

Make sure to register your contribution by filling the contribution registration form

The Pull Request will be reviewed only after the contribution registration form is filled.

Status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

fixes: https://jira-dc.paloaltonetworks.com/browse/CRTX-207166

Description

Must have

  • Tests
  • Documentation

@BEAdi BEAdi self-assigned this Jan 4, 2026
@BEAdi BEAdi requested a review from DeanArbel as a code owner January 4, 2026 09:26
@BEAdi BEAdi added the ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines label Jan 4, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jan 4, 2026 •
edited
Loading

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/PrismaSaasSecurity/Integrations/SaasSecurityEventCollector
   SaasSecurityEventCollector.py931583%46–47, 51, 92–93, 98, 102–103, 186, 192–194, 241–243
TOTAL931583% 

Tests Skipped Failures Errors Time
88 0 💤 0 ❌ 0 🔥 2.661s ⏱️

BEAdi
BEAdi commented Jan 7, 2026
View reviewed changes
Comment thread ...s/PrismaSaasSecurity/ModelingRules/SaasSecurityEventCollector/SaasSecurityEventCollector.xif Outdated
Copy link
Copy Markdown
Contributor Author

@BEAdi BEAdi Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no related test data for this modeling rule, so the build failed to verify it. Per @eepstain, this is an old mapping that should be removed.

@BEAdi BEAdi added the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Jan 7, 2026
@content-bot content-bot removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Jan 7, 2026
@content-bot
Copy link
Copy Markdown
Contributor

content-bot commented Jan 7, 2026

🤖 Content AI Reviewer: Analysis started. Please wait for results...

content-bot

This comment was marked as outdated.

Sign in to view

@BEAdi BEAdi added the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Jan 8, 2026
@content-bot content-bot removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Jan 8, 2026
@content-bot
Copy link
Copy Markdown
Contributor

content-bot commented Jan 8, 2026

🤖 Content AI Reviewer: Analysis started. Please wait for results...

@content-bot
Copy link
Copy Markdown
Contributor

content-bot commented Jan 8, 2026

Validate summary
The following errors were reported as warnings: BC117.
BC117 validation requires PM review due to changes to supportedModules.
The following errors were thrown as a part of this pr: RN107.
The following errors cannot be ignored: RN107.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: RN107.

Verdict: PR can be force merged from validate perspective? ✅

@content-bot
Copy link
Copy Markdown
Contributor

content-bot commented Jan 8, 2026

🤖 Content-bot Review Disclaimer

This review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause.

content-bot
content-bot reviewed Jan 8, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@content-bot content-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello and thanks for the contribution! I have a few observations regarding the release notes and integration configuration.

It appears that the <~PLATFORM> placeholder was left in multiple release note files; please update these to specific tags or remove them if not needed. Also, please double-check the supportedModules field in the Event Collector YAML to ensure it is valid and supported.

Great work otherwise!

@DeanArbel please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

Comment thread Packs/Palo_Alto_Networks_Enterprise_DLP/ReleaseNotes/2_0_24.md
@@ -0,0 +1,6 @@
<~PLATFORM>
Copy link
Copy Markdown
Contributor

@content-bot content-bot Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears that <~PLATFORM> is a template placeholder. Please verify if this should be replaced with a specific platform tag (e.g., <~XSIAM>) or removed if the release note applies to all supported platforms.

@BEAdi
Copy link
Copy Markdown
Contributor Author

BEAdi commented Jan 8, 2026

Needs a force merge:

  • The pre-commit hook validate-deleted-files fails because a modeling rule was deleted per @eepstain request.
  • Validations fail on: RN107 - I added 1 RN entry for the whole pack with no split for content items. BC117 - the supported modules change is this PR's purpose.

@demisto demisto deleted a comment from content-bot Jan 8, 2026
@demisto demisto deleted a comment from content-bot Jan 8, 2026
@demisto demisto deleted a comment from content-bot Jan 8, 2026
@demisto demisto deleted a comment from content-bot Jan 8, 2026
jbabazadeh
jbabazadeh approved these changes Jan 8, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@jbabazadeh jbabazadeh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

Comment thread Packs/FreshworksFreshservice/Classifiers/classifier-FreshworksFreshservice_-_Classifier.json
@BEAdi BEAdi added the ForceMerge Forcing the merge of the PR despite the build status label Jan 8, 2026
@jbabazadeh jbabazadeh merged commit 585f233 into master Jan 8, 2026
43 of 49 checks passed
@jbabazadeh jbabazadeh deleted the ae-fix-CRTX-207166 branch January 8, 2026 15:19
@BarGali BarGali changed the title Add new content packs to XDR users !Add new content packs to XDR users Jan 8, 2026
@BarGali BarGali changed the title !Add new content packs to XDR users Add new content packs to XDR users Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@content-bot content-bot content-bot left review comments

@jbabazadeh jbabazadeh jbabazadeh approved these changes

@DeanArbel DeanArbel Awaiting requested review from DeanArbel DeanArbel is a code owner

Assignees

@BEAdi BEAdi

Labels

docs-approved ForceMerge Forcing the merge of the PR despite the build status ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines supported-modules-approved

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@BEAdi @content-bot @jbabazadeh