Azure Key Vaults 1.0.1
- 01 Nov 2022
- 1 Minute to read
- DarkLight
- PDF
Azure Key Vaults 1.0.1
- Updated on 01 Nov 2022
- 1 Minute to read
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
tags: Python | Azure | Keys | Secret | Password | Vault
Description
Integration with Azure Key Vault enables securely storing and tightly controlling access to passwords. This integration is carried out in order to meet the requirement of one of the packs to store passwords on Azure Key Vault.
Azure Key Vault is a cloud service for securely storing and accessing secrets such as API keys, passwords, and certificates.
CyberProof has provided actions to get the secret values and store it to Redis, and set a secret value from Redis. In this integration, the Key Vault service supports the vaults type of containers.
CyberProof has provisioned a configuration option to CDC users to set an expiry date of a secret in a key vault. This needs to be configured from the data store key. The default expiry date of a secret in the key vault is set to 3650 days (i.e., 10yrs).
| Integration Type: | UCA Infrastructure |
| Information read: | Secrets such as passwords |
| API Supported: | |
| Input: | |
| Output: |
Configuration
DataStore
| Name | Type | Description | Example | Required | Secret |
|---|---|---|---|---|---|
| api_azure_key_vaults | object | The key name of the configuration | '{"vault_url":"kusto_cluster_url","tenant_id":"tenant_id","client_id":"client_id","client_secret":"client_secret"}' | True | True |
Pack UI
| Option | Type | Description | Required | Secret |
|---|---|---|---|---|
| instance_name | string | The key name of the configuration in DataStore. | True | False |
Customer Configuration
CDC Command Lines
No CDC command lines
Workflows
No workflows
Rules
No rules
Sensors
No sensors
Triggers
No triggers
Known Issues
No known issues
Was this article helpful?