Skills azure-security-keyvault-keys-dotnet
๐Ÿ“ฆ

azure-security-keyvault-keys-dotnet

Content revision r2 Safe โš™๏ธ External commands๐ŸŒ Network access

Build Secure Azure Key Vault Key Workflows

Implementing secure cloud key operations in .NET requires correct SDK, identity, algorithm, and lifecycle choices. This skill provides focused Azure Key Vault patterns and references.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

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-security-keyvault-keys-dotnet" from https://skillstore.io/skills/sickn33-azure-security-keyvault-keys-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-security-keyvault-keys-dotnet/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.

Test it

Using "azure-security-keyvault-keys-dotnet". Explain the recommended authentication approach for a .NET service running in Azure.

Expected outcome:

A recommendation to use DefaultAzureCredential with managed identity, required RBAC roles, placeholder configuration, and local development considerations.

Using "azure-security-keyvault-keys-dotnet". Plan automatic rotation for an RSA key that expires every 90 days.

Expected outcome:

A lifecycle outline covering expiration, rotation 30 days before expiry, version handling, permission requirements, and recovery testing.

Using "azure-security-keyvault-keys-dotnet". Compare encryption, signing, and key wrapping for my application.

Expected outcome:

A concise comparison of each operation, suitable key types, supported algorithms, input expectations, and security boundaries.

Security Audit

Safe
v6 โ€ข 7/23/2026 Open versioned report

All 82 static findings are false positives caused by Markdown formatting, expected Azure endpoints, and benign SDK terminology. The file is documentation only and contains no executable scripts, prompt injection, credential exfiltration, or malware behavior.

1
Files scanned
416
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
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-security-keyvault-keys-dotnet/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

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

BibTeX citation

@techreport{sickn33-sickn33-azure-security-keyvault-keys-dotnet-2026, author = {sickn33}, title = {azure-security-keyvault-keys-dotnet security audit report (audit version 6)}, institution = {Skillstore}, year = {2026}, number = {6}, url = {https://skillstore.io/skills/sickn33-azure-security-keyvault-keys-dotnet/audits/6}, 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-security-keyvault-keys-dotnet security audit report (audit version 6)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-azure-security-keyvault-keys-dotnet/audits/6" identifiers: - type: other value: "skillstore:sickn33-azure-security-keyvault-keys-dotnet:audit:6" 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

Start a Key Vault Integration

Configure packages, credentials, vault URIs, and a KeyClient for a new .NET service.

Design a Key Lifecycle

Plan key creation, rotation, expiration, backup, recovery, and least-privilege operations.

Review Cryptographic Operations

Compare supported encryption, wrapping, signing, verification, and key-resolution patterns before implementation.

Try These Prompts

Create a KeyClient
Show how to install Azure Key Vault Keys and Azure Identity, then create a KeyClient with DefaultAzureCredential and placeholder vault settings.
Plan a Key Lifecycle
Design a .NET lifecycle for creating, retrieving, updating, rotating, deleting, and recovering an RSA key with least-privilege RBAC.
Implement Cryptographic Operations
Create a .NET workflow for RSA-OAEP-256 encryption and RS256 signing, including verification, error handling, and safe logging without plaintext or key exposure.
Review a Production Design
Review my Key Vault design for Managed HSM, rotation, version pinning, backup, recovery, caching, RBAC, and destructive-operation safeguards.

Best Practices

  • Prefer managed identity through DefaultAzureCredential and grant only the required Key Vault RBAC role.
  • Use HSM-backed keys, expiration dates, restricted operations, automatic rotation, and pinned versions where the risk requires them.
  • Review destructive operations, protect backups, handle Azure errors explicitly, and test recovery before production use.

Avoid

  • Do not embed tenant credentials, client secrets, plaintext, or key material in source code or logs.
  • Do not enable unnecessary key operations or grant broad management roles to application identities.
  • Do not purge keys, restore backups, or change rotation policies without approval and recovery planning.

Frequently Asked Questions

Which authentication method is recommended?
DefaultAzureCredential is preferred because it supports managed identity and local developer credentials without embedding secrets.
Does this skill provision Azure resources?
No. It provides guidance and examples; users must run, review, and test generated code in their Azure environment.
Does it cover Managed HSM?
Yes. The guidance covers hardware-protected key options and Azure Key Vault Managed HSM concepts.
Which cryptographic operations are included?
It covers encryption, decryption, key wrapping, unwrapping, signing, verification, and key resolution.
Are deletion and purge operations safe by default?
No. They require appropriate RBAC, explicit approval, recovery planning, and environment-specific safeguards.
Which SDK version does the source describe?
The source documents version 4.7.0. Verify current package APIs and security guidance before production adoption.

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

8 downloads ยท 136 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all