azure-security-keyvault-keys-dotnet
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.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
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.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
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
SafeAll 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.
Risk Factors
⚙️ External commands (50)
🌐 Network access (8)
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.
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_reportMarkdown badge
[](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/6BibTeX 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: HighWhat 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
Show how to install Azure Key Vault Keys and Azure Identity, then create a KeyClient with DefaultAzureCredential and placeholder vault settings.
Design a .NET lifecycle for creating, retrieving, updating, rotating, deleting, and recovering an RSA key with least-privilege RBAC.
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 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.