Skills azure-keyvault-keys-ts
📦

azure-keyvault-keys-ts

Content revision r2 High Risk ⚙️ External commands🌐 Network access🔑 Env variables

Build Azure Key Vault Key Workflows in TypeScript

Azure Key Vault key workflows can be complex and easy to configure incorrectly. This skill provides TypeScript examples for authentication, lifecycle management, cryptography, backup, and rotation.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "azure-keyvault-keys-ts" from https://skillstore.io/skills/sickn33-azure-keyvault-keys-ts.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-keyvault-keys-ts/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "azure-keyvault-keys-ts". Plan authentication and RSA key creation for an Azure-hosted Node.js service.

Expected outcome:

Recommended plan: use managed identity through DefaultAzureCredential, grant only required key permissions, create an expiring RSA key, and verify access without logging secrets.

Using "azure-keyvault-keys-ts". Design a rotation policy for a key that expires every 90 days.

Expected outcome:

Rotation policy: rotate 30 days before expiry, retain a recovery window, monitor failures, and validate dependent services before disabling older versions.

Security Audit

High Risk
v5 • 7/23/2026 Open versioned report

All 44 static findings are false positives caused by Markdown fences, a TypeScript template literal, normal Azure URLs, and non-secret configuration access. However, the examples expose sensitive values in logs and show irreversible purge operations without confirmation safeguards.

1
Files scanned
280
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (2)

High
Sensitive Values Printed to Logs
Examples print a retrieved secret and decrypted plaintext, which can expose sensitive data through logs, terminals, or captured agent output.
Both lines directly pass sensitive values to console.log without redaction.
Medium
Irreversible Purge Without Confirmation
Examples permanently purge deleted secrets and keys without requiring confirmation or warning that recovery becomes impossible.
The documented purge calls are explicit and no nearby safeguard or recovery warning is provided.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-azure-keyvault-keys-ts/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-azure-keyvault-keys-ts/security.svg)](https://skillstore.io/skills/sickn33-azure-keyvault-keys-ts?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-azure-keyvault-keys-ts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-keyvault-keys-ts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-azure-keyvault-keys-ts.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). azure-keyvault-keys-ts security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-keyvault-keys-ts/audits/5

BibTeX citation

@techreport{sickn33-sickn33-azure-keyvault-keys-ts-2026, author = {sickn33}, title = {azure-keyvault-keys-ts security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-azure-keyvault-keys-ts/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "azure-keyvault-keys-ts security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-azure-keyvault-keys-ts/audits/5" identifiers: - type: other value: "skillstore:sickn33-azure-keyvault-keys-ts:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Implement Application Encryption

Create TypeScript services that encrypt and decrypt application data through Azure-managed keys.

Automate Key Rotation

Define rotation policies, expiration periods, and validation steps for managed Azure keys.

Review Key Management Controls

Assess key operations, permissions, logging, backup, and destructive actions before production deployment.

Try These Prompts

Authenticate to a Vault
Show how to authenticate a Node.js TypeScript application to Azure Key Vault with DefaultAzureCredential. Include required packages, environment variables, and error handling.
Create a Managed Key
Create a TypeScript example that creates an RSA key named [KEY_NAME] in [VAULT_NAME]. Set expiration, allowed operations, and useful tags.
Design Key Rotation
Design a key rotation workflow for [KEY_NAME] with a 90-day lifetime and rotation 30 days before expiry. Explain permissions and validation steps.
Audit a Key Vault Integration
Review this TypeScript integration for least privilege, safe logging, retry handling, destructive-operation controls, and cryptographic algorithm choices. Return prioritized findings and tests.

Best Practices

  • Use DefaultAzureCredential with managed identity and least-privilege Azure roles.
  • Set expiration dates and rotation policies for every production key.
  • Keep plaintext, secret values, decrypted data, and key material out of logs.

Avoid

  • Do not purge keys or secrets without explicit confirmation and recovery checks.
  • Do not grant encrypt, decrypt, sign, or verify permissions unless the application requires them.
  • Do not hardcode credentials, secret values, vault-specific identifiers, or production expiration dates.

Frequently Asked Questions

Does this skill execute Azure operations?
No. It provides TypeScript guidance and examples that require your Azure credentials, vault, permissions, and runtime.
Which Azure packages are covered?
It primarily covers @azure/keyvault-keys and @azure/identity, with additional examples for @azure/keyvault-secrets.
Can I use these examples in a browser?
No. The source states that these SDK workflows target Node.js and do not support browser execution.
Which key operations are demonstrated?
The examples cover creation, retrieval, listing, rotation, deletion, purge, encryption, decryption, signing, verification, wrapping, backup, and restore.
What authentication method is recommended?
DefaultAzureCredential is recommended because it supports local development credentials and managed identity in Azure environments.
Are the examples production ready?
No. Replace placeholders, update expiration dates, remove sensitive logging, add retries, and protect destructive operations before production use.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

6 downloads · 116 views

File structure

📄 SKILL.md