Stop sensitive credential logging in data connectors - #14923
Open
idoshabi07 wants to merge 4 commits into
Open
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ccff4d4a-3094-4de9-a5c0-d00c63d96a37
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ccff4d4a-3094-4de9-a5c0-d00c63d96a37
This was referenced Aug 16, 2026
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: ecd48319-0dd9-4307-a659-860950fe6e6e
v-atulyadav
added
Connector
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Removes sensitive credential logging from Cybersixgill and Cohesity data connectors, and bumps solution/package versions to reflect the security-related changes.
Changes:
- Removed Cybersixgill environment dump logging from the Python Azure Function.
- Removed Cohesity ARM bearer token logging from the incident consumer.
- Updated solution/package versions and release notes for both solutions.
Reviewed changes
Copilot reviewed 8 out of 11 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| Solutions/Cybersixgill-Actionable-Alerts/ReleaseNotes.md | Adds release note entry documenting removal of environment secret logging. |
| Solutions/Cybersixgill-Actionable-Alerts/Package/mainTemplate.json | Bumps solution/content versions and adjusts some template variables/values. |
| Solutions/Cybersixgill-Actionable-Alerts/Data/Solution_Cybersixgill_Actionable_Alerts.json | Bumps packaged solution version. |
| Solutions/Cybersixgill-Actionable-Alerts/Data Connectors/CybersixgillAlerts/init.py | Removes logging of full process environment. |
| Solutions/CohesitySecurity/ReleaseNotes.md | Adds release note entry documenting removal of ARM token logging. |
| Solutions/CohesitySecurity/Package/mainTemplate.json | Bumps solution/content versions. |
| Solutions/CohesitySecurity/Data/Solution_CohesitySecurity.json | Bumps packaged solution version. |
| Solutions/CohesitySecurity/Data Connectors/Helios2Sentinel/IncidentConsumer/IncidentConsumer.cs | Removes logging of bearer token. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
Contributor
Author
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes AI scan items 130027 and 130268 by removing the Cybersixgill process-environment dump and Cohesity ARM bearer-token logging.
The connector and solution package artifacts were regenerated using the repository packaging flow. This necessarily includes solution/package version bumps, release notes, generated ARM template version/description updates, and new package ZIPs. The Cybersixgill generated template retains centralized ARM variables for its repeated
x-channel-idandstepIdvalues.Validation covers Python syntax, generated JSON/package consistency, and ARM template toolkit checks for the affected solutions.