Key Management
Category: Security
Node id: key-management
Standards: HIPAA, SOC2
Manages cryptographic key lifecycle including generation, rotation, retrieval, deletion, and export
What it does
- Six key lifecycle operations: generate, rotate, retrieve, delete, list, export
- AES-128, AES-256, RSA-2048, RSA-4096 key types
- Key rotation with version tracking and expiration
- Export in JSON, PEM, and DER formats
- Key status filtering and metadata management
Use cases
- Generate encryption keys for PHI data protection
- Rotate keys on a scheduled basis for compliance
- Export keys for cross-system integration
- Manage key lifecycle for HIPAA encryption requirements
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
key_id | text | No | Key identifier for operations that target an existing key |
authorized | any | No | Whether the requester is authorized for the operation |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Key operation result with operation, key_id, key_data/key_metadata (generate), keys/count (list), export_package (export), and message |
success | boolean | No | Whether the key operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | Yes | generate | generate, rotate, retrieve, delete, list, export | Key management operation to perform |
| Key Type | key_type | enum | No | aes-256 | aes-256, aes-128, rsa-2048, rsa-4096 | Type of cryptographic key |
| Key ID | key_id | string | No | Identifier for the key (auto-generated if empty) | ||
| Purpose | purpose | string | No | encryption | Intended use of the key |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Rotation Days | rotation_days | number | No | 90 | min 1; max 365 | Key rotation period in days |
| Immediate Delete | immediate | boolean | No | false | Delete key immediately instead of scheduling | |
| Status Filter | status | string | No | all | Filter keys by status (list operation) | |
| Export Format | format | enum | No | json | json, pem, der | Key export format |
| Key Version | version | number | No | 0 | Specific key version to retrieve |
Errors
| Code | Description |
|---|---|
KEY_NOT_FOUND | The specified key ID does not exist |
INVALID_OPERATION | The specified key management operation is not recognized |
KEY_GENERATION_FAILED | Failed to generate cryptographic key material |
UNAUTHORIZED | Requester is not authorized for this key operation |
Runtime notes
- result shape varies by operation — generate includes key_data, list includes keys array, rotate includes old/new versions
- Unauthorized requests return success=false with an error message in result, not a Go error
- key_data for AES keys is base64-encoded; RSA keys return a placeholder pending vault integration
- list operation supports status and purpose filters; defaults to returning all keys
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..