Skills azure-keyvault-keys-rust
📦

azure-keyvault-keys-rust

Content revision r2 Medium Risk ⚙️ External commands🌐 Network access

Build Azure Key Vault Key Workflows in Rust

Rust developers need reliable patterns for managing cryptographic keys in Azure Key Vault. This skill provides focused guidance for authentication, lifecycle operations, backup, restore, and RBAC.

Supports: Claude Codex Code(CC)
📊 69 Adequate

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-rust" from https://skillstore.io/skills/sickn33-azure-keyvault-keys-rust.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-keyvault-keys-rust/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

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

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-azure-keyvault-keys-rust.md Signed manifest GET /api/skills/sickn33-azure-keyvault-keys-rust/manifest Signed lockfile GET /api/skills/sickn33-azure-keyvault-keys-rust/lockfile

Test it

Using "azure-keyvault-keys-rust". Which key type should I use for application signing?

Expected outcome:

  • Use an EC key, such as P-256, when compatibility requirements allow it.
  • Choose an HSM-backed key when hardware protection is required.
  • Grant only the signing and verification permissions the application needs.

Using "azure-keyvault-keys-rust". Outline a safe production key deletion process.

Expected outcome:

  • Confirm the subscription, vault, key name, and intended key version.
  • Verify soft delete and purge protection before starting.
  • Check dependencies, create an approved backup, and record authorization.
  • Delete only after explicit approval and verify recovery readiness.

Security Audit

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

All 31 static findings are false positives caused by Markdown formatting, fixed Azure package installation, expected service endpoints, trusted reference links, and non-secret key terminology. The skill has no prompt injection or malicious intent, but its deletion and backup examples need stronger operational safeguards. These semantic risks are limited to legitimate Key Vault lifecycle guidance.

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

Confirmed security concerns (2)

Medium
SKILL.md:95-99
Destructive Key Deletion Without Safeguards
The deletion example invokes delete_key directly without confirmation, recovery guidance, or a production safety check. Generated implementations could remove an active key unexpectedly.
The example directly performs a destructive key lifecycle operation, and the surrounding section provides no guard or recovery instruction.
Medium
SKILL.md:114-119
Key Backup Material Handling Is Underspecified
The backup example retrieves backup.value but only says to store it safely. It omits encryption, access controls, retention limits, and logging exclusions.
The code clearly obtains key backup bytes, while the only handling requirement is a brief comment with no concrete controls.

Risk Factors

⚙️ External commands (24)
SKILL.md:15-17 SKILL.md:17-21 SKILL.md:21-23 SKILL.md:23-27 SKILL.md:27-37 SKILL.md:37-52 SKILL.md:52-59 SKILL.md:59-63 SKILL.md:63-76 SKILL.md:76-80 SKILL.md:80-93 SKILL.md:93-97 SKILL.md:97-99 SKILL.md:99-103 SKILL.md:103-112 SKILL.md:112-116 SKILL.md:116-119 SKILL.md:119-123 SKILL.md:123-131 SKILL.md:131-137 SKILL.md:137-143 SKILL.md:143-147 SKILL.md:147 SKILL.md:158-159
🌐 Network access (5)
SKILL.md:22 SKILL.md:33 SKILL.md:165 SKILL.md:166 SKILL.md:167
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-rust/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-rust/security.svg)](https://skillstore.io/skills/sickn33-azure-keyvault-keys-rust?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-azure-keyvault-keys-rust.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-rust security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-keyvault-keys-rust/audits/5

BibTeX citation

@techreport{sickn33-sickn33-azure-keyvault-keys-rust-2026, author = {sickn33}, title = {azure-keyvault-keys-rust security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-azure-keyvault-keys-rust/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-rust 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-rust/audits/5" identifiers: - type: other value: "skillstore:sickn33-azure-keyvault-keys-rust:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

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

What You Can Build

Add Key Management to a Rust Service

Create a KeyClient and implement common key lifecycle operations for an application.

Select Keys and Access Roles

Compare RSA, EC, and HSM options while identifying suitable Key Vault RBAC roles.

Plan Backup and Recovery

Design controlled key backup, restore, soft-delete, and rotation procedures for production.

Try These Prompts

Connect to a Vault 
Show me how to add the required Rust crates and initialize KeyClient for my Azure Key Vault. Use developer credentials and explain each placeholder.
Create and List Keys 
Create a Rust example that adds one RSA key and one P-256 EC key, then lists their names. Include error-handling guidance.
Design a Safe Lifecycle 
Plan Rust workflows for key creation, retrieval, rotation, backup, restore, and deletion. Add confirmation steps and recovery controls for destructive actions.
Review a Production Architecture 
Review my Rust Key Vault design for identity, RBAC, HSM selection, rotation, backup protection, logging, and failure handling. Identify risks and concrete improvements.

Best Practices

  • Use managed identity in production and grant the smallest suitable Key Vault role.
  • Enable soft delete, purge protection, rotation, and monitored recovery procedures.
  • Protect backup bytes with encryption, access controls, retention policies, and logging exclusions.

Avoid

  • Do not embed vault credentials, key material, or backup bytes in source code.
  • Do not delete keys without confirming scope, dependencies, approval, and recovery controls.
  • Do not grant broad administrative roles when an application only needs cryptographic operations.

Frequently Asked Questions

Does this skill create an Azure Key Vault?
No. It assumes a vault already exists and focuses on the Rust Keys SDK.
Which credentials are shown?
The examples show DeveloperToolsCredential for development and recommend ManagedIdentityCredential for production.
Can it create HSM-backed keys?
It identifies RSA-HSM and EC-HSM key types, but it does not provide a complete creation example.
Does it include encryption and signing code?
No. It lists supported operations but does not provide complete cryptographic operation implementations.
What permissions are required?
Required permissions depend on the operation. The skill names Crypto User and Crypto Officer roles as starting points.
How should key backups be stored?
Treat backup bytes as sensitive material with encryption, limited access, retention controls, and excluded logging.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-keyvault-keys-rust

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

5 downloads · 110 views

File structure

📄 SKILL.md