Site icon techcoffeehouse.com

Keeper Security Adds Zero-Knowledge Secrets to Azure Logic Apps

Hackers Report First Security Vulnerability To 77% Of Customers Within 24 Hours HackerOne Report Reveals
Advertisements

Keeper Security has launched a certified connector integrating its Secrets Manager with Microsoft Azure Logic Apps, giving enterprise teams a way to retrieve and manage credentials at runtime without hardcoding sensitive values into automated workflows.

The connector, now published on the Microsoft Power Platform marketplace, lets teams create, retrieve and rotate secrets directly within Azure Logic Apps and Power Automate flows. Microsoft Azure and Power Automate see wide adoption across the Asia Pacific region excluding China, with Southeast Asia in particular seeing strong SMB uptake of low-code cloud tools.

Closing a persistent workflow security gap

Hardcoded credentials in automation scripts remain one of the most persistent and exploitable vulnerabilities in enterprise environments, according to Keeper. The connector addresses this by giving teams a zero-knowledge, policy-enforced path to secrets management inside Microsoft Power Platform.

“Workflow automation is only as secure as the secrets powering it, and most organisations are still hardcoding those secrets which creates massive cyber risk. This connector eliminates that exposure by bringing Keeper’s zero-knowledge architecture directly into the Microsoft automation layer: secrets stay encrypted in the vault and are retrieved only at the moment they are needed, so there is nothing hardcoded to steal,” said Darren Guccione, CEO and Co-founder of Keeper Security.

The connector runs through a lightweight Python middleware service deployed as an Azure Function App, communicating with the Keeper Vault via the Keeper Secrets Manager SDK. Secrets stay encrypted under Keeper’s zero-knowledge architecture and are decrypted locally within the customer’s own Azure environment, never transmitted in plaintext through Keeper’s infrastructure.

“Secrets should be decrypted as close to the workload as possible and only when needed. The Azure Function middleware gives customers a deployment model where the Keeper SDK runs inside their own Azure environment, their own key management handles the configuration and plaintext credentials are never in motion across a network boundary they do not control,” said Craig Lurey, CTO and Co-founder of Keeper Security.

What the connector offers enterprise teams

The connector supports five operations — List Secrets, Get Secret, Create Secret, Update Secret and List Folders — covering use cases from API credential injection to GitHub secret synchronisation and vault compliance auditing. It is available now, with documentation and deployment instructions published on Keeper’s developer site.

Author

Exit mobile version