CIAC-17779: Align asset fetch parameters with supportedModules rules

[dtroushinsky]

Status

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

Related Issues

fixes: https://jira-dc.paloaltonetworks.com/browse/CIAC-17779

Description

Aligns the Fetch Assets configuration parameters (isFetchAssets, assetsFetchInterval) of the asset integrations with the required supportedModules / hidden rules. For each of these params, supportedModules must be a subset of [xsiam, exposure_management] and the params should be hidden on xsoar.

Must have

• Tests
• Documentation

[content-bot]

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

• @marketplace-ai-reviewer start review - Initiate a full AI code review
• @marketplace-ai-reviewer re-review - Incremental review for new commits

[dtroushinsky]

@marketplace-ai-reviewer start review

[marketplace-ai-reviewer]

🤖 Analysis started. Please wait for results...

[github-actions]

Tests	Skipped	Failures	Errors	Time
751	0 💤	0 ❌	0 🔥	20.951s ⏱️

[marketplace-ai-reviewer]

🤖 AI 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.

[marketplace-ai-reviewer]

Hi! Thanks for your contribution. I've reviewed the PR and noticed a few minor formatting issues to tidy up.

Mainly, there are some YAML indentation inconsistencies across several integration files (CrowdStrike, Rapid7, Tenable, and Qualys), specifically around the new parameter blocks, hidden keys, and supportedModules lists. There's also a quick suggestion to add the vendor name to the Rapid7 pack metadata keywords.

Thanks again, and let me know if you have any questions!

Additionally, please address the following file-level notes:

• Packs/Rapid7_Nexpose/pack_metadata.json: Consider adding the vendor name "Rapid7" to the keywords list in this file.

@DanielTal87, @Shellyber, @talzich, @JasBeilin, @dtroushinsky please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

[content-bot]

🔍 AI Triage Report Available

An automated triage report has been generated for this pipeline.

Status: failed
Report ID: 488e204f436bc8a8

📋 Triage Report
💡 Resolutions are available in the full report.

⚠️ AI-generated triage. Validate before acting.

[content-bot]

Validate summary
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

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