Remove logResponseContent attribute from Polling Config

[nitsan-tzur]

Required items, please complete

Change(s):

• Remove logResponseContent from CyberArkAudit_PollingConfig.json

Reason for Change(s):

• Security patch to prevent sensitive response data to be captured in telemetry

[Copilot]

Note

Copilot was unable to run its full agentic suite in this review.

Pull request overview

Removes logResponseContent from polling configuration to avoid capturing sensitive response payloads in telemetry.

Changes:

• Removed logResponseContent from the polling config used by the CyberArkAudit CCP data connector.
• Removed logResponseContent from the packaged ARM template equivalent.
• Added a release note entry documenting the security patch.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

File	Description
Solutions/CyberArkAudit/ReleaseNotes.md	Documents the security patch as version 3.2.1.
Solutions/CyberArkAudit/Package/mainTemplate.json	Removes logResponseContent from the packaged template polling/request config.
Solutions/CyberArkAudit/Data Connectors/CyberArkAudit_CCP/CyberArkAudit_PollingConfig.json	Removes logResponseContent from the connector’s polling configuration.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[v-maheshbh (v-maheshbh)]

Hi nitsan-tzur

Kindly review the Copilot comments and address them where applicable.
and attach a screenshot of the CCF connector in the Connected state for validation.

Thanks!