Skip to content

Secure GreyNoise API key handling - #14901

Open
idoshabi07 wants to merge 1 commit into
Azure:masterfrom
idoshabi07:ai-scan/greynoise-secret
Open

Secure GreyNoise API key handling#14901
idoshabi07 wants to merge 1 commit into
Azure:masterfrom
idoshabi07:ai-scan/greynoise-secret

Conversation

@idoshabi07

Copy link
Copy Markdown
Contributor

Summary

Uses secure-string parameters for the GreyNoise API key and masks the Logic App HTTP action inputs and outputs.

AI scan items

Validation

ARM template JSON parsing passed.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: ccff4d4a-3094-4de9-a5c0-d00c63d96a37
@idoshabi07
idoshabi07 requested review from a team as code owners August 13, 2026 12:11
@v-maheshbh v-maheshbh (v-maheshbh) added the Playbook Playbook specialty review needed label Aug 13, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Note

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

Updates the GreyNoise enrichment playbook ARM template to treat the GreyNoise API key as a secret and reduce the chance of it being logged in Logic App runs.

Changes:

  • Converted the ARM template GreyNoiseAPIKey parameter to securestring.
  • Converted the Logic App workflow parameter GreyNoiseKey to SecureString.
  • Added runtimeConfiguration.secureData to mask inputs/outputs for the GreyNoise HTTP actions.

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

Comment on lines 13 to 16
"GreyNoiseAPIKey": {
"defaultValue": "",
"type": "string"
"type": "securestring"
},
Comment on lines 109 to 112
"GreyNoiseKey": {
"defaultValue": "[parameters('GreyNoiseAPIKey')]",
"type": "String"
"type": "SecureString"
},
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Playbook Playbook specialty review needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants