Skills azure-security-keyvault-secrets-java
📦

azure-security-keyvault-secrets-java

Content revision r2 High Risk ⚙️ External commands🌐 Network access📁 Filesystem access

Manage Azure Key Vault Secrets with Java

Java applications need secure credential access without embedding secrets in source code. This skill provides Azure Key Vault SDK patterns for secret lifecycle management.

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-security-keyvault-secrets-java" from https://skillstore.io/skills/sickn33-azure-security-keyvault-secrets-java.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-security-keyvault-secrets-java/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-security-keyvault-secrets-java". Set up a Java client for my production vault.

Expected outcome:

  • A Maven dependency recommendation with version verification guidance.
  • A client configuration using DefaultAzureCredential and an external vault URL.
  • A checklist for identity permissions, local testing, and production deployment.

Using "azure-security-keyvault-secrets-java". Plan a safe database-password rotation.

Expected outcome:

  • Create and validate a new version before changing the active version.
  • Update consumers and verify successful reads without exposing the value.
  • Disable the prior version only after validation, with a documented rollback path.

Using "azure-security-keyvault-secrets-java". Review my Key Vault error handling.

Expected outcome:

The review distinguishes missing secrets, denied access, rate limits, and unexpected service errors. It recommends bounded retries and secret-safe diagnostic messages.

Security Audit

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

All 57 static findings are false positives caused by Markdown syntax, Azure endpoint examples, Java SDK package names, or placeholder text. Semantic review found unsafe secret logging, local backup persistence without protection guidance, and a rotation sequence that can disable the active version before replacement succeeds.

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

Confirmed security concerns (3)

High
Secret Values Written to Standard Output
Several examples print complete secret values or a secret prefix. Application logs can expose credentials to operators, log processors, and retained telemetry.
The examples directly concatenate values returned by getValue() into System.out output, including complete values and a five-character prefix.
Medium
Secret Backup Persisted Without Protection Guidance
The backup workflow writes a Key Vault secret backup blob to a local file without permissions, protected storage, retention, or cleanup guidance.
The example directly writes backup bytes to secret-backup.blob and later reads them, while providing no filesystem protection or cleanup controls.
Medium
Rotation Can Disable the Active Secret Before Replacement
The rotation workflow disables the current secret version before creating its replacement. A failed write can leave consumers without an enabled secret.
The sequence explicitly disables and updates the current version before setSecret creates the new version, with no rollback or validation path.
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-secrets-java/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-security-keyvault-secrets-java/security.svg)](https://skillstore.io/skills/sickn33-azure-security-keyvault-secrets-java?utm_source=security_passport_badge)

HTML badge

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

Embed card

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

BibTeX citation

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

Skillstore Score

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

What You Can Build

Integrate Application Secrets

Add Key Vault retrieval to a Java service while keeping credentials outside source code.

Standardize Secret Operations

Define consistent workflows for versioning, rotation, deletion, recovery, and backup across services.

Review Secret Handling

Assess Java Key Vault patterns for least privilege, safe logging, lifecycle controls, and failure recovery.

Try These Prompts

Create a Key Vault Client
Show how to add the Azure Key Vault Secrets SDK to a Java Maven project. Create a SecretClient with DefaultAzureCredential.
Load Application Secrets
Design a Java service that retrieves [secret names] from [vault URL] without logging values. Include error handling and clear configuration boundaries.
Manage a Secret Lifecycle
Create a Java workflow for setting metadata, listing versions, deleting, recovering, and purging [secret name]. Explain permissions and irreversible steps.
Design Resilient Rotation
Design a resilient rotation workflow for [secret name] with the Azure Key Vault Java SDK. Include validation, rollback, concurrency, auditing, and secret-safe logging.

Best Practices

  • Use managed identities or workload identities with least-privilege Key Vault permissions.
  • Log secret names and version identifiers only, never secret values or prefixes.
  • Create and validate replacement versions before disabling previous versions.

Avoid

  • Do not hardcode real passwords, API keys, connection strings, or vault credentials in source code.
  • Do not persist backup blobs without restricted permissions, retention controls, and secure deletion.
  • Do not purge deleted secrets until recovery requirements and approvals are confirmed.

Frequently Asked Questions

Does this skill access Azure Key Vault directly?
No. It provides Java SDK guidance and examples. Your application needs Azure connectivity, credentials, and Key Vault permissions.
Which authentication method does it demonstrate?
It demonstrates DefaultAzureCredential, which can use supported local and hosted Azure identity sources.
Does it cover synchronous and asynchronous clients?
Yes. It includes SecretClient and SecretAsyncClient creation and common operation patterns.
Can deleted secrets always be recovered?
Recovery depends on vault configuration and retention state. Purged secrets cannot be recovered through the shown workflow.
Are the examples production ready?
No. Validate imports, permissions, retries, logging, backup protection, and rotation ordering for your environment.
Which SDK version should I use?
The skill shows version 4.9.0. Check Azure release notes and your dependency policy before selecting a production version.

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 · 106 views

File structure

📄 SKILL.md

More from sickn33

View all
View all