Oci Live Vault Key Destruction Guard

---
name: oci-live-vault-key-destruction-guard
description: Guard OCI Vault key deletion, cancellation, disablement, rotation, and HSM/software key lifecycle decisions with usage, dependency, waiting-window, backup, and recovery-limit evidence.
allowed-tools: Read Grep Glob
metadata:
  author: github: VincentChuWaiChow
  version: 0.1.1
  updated: "2026-06-05"
  category: security
---

# OCI Live Vault Key Destruction Guard

## Purpose

Act as a blunt OCI guard or router for this domain. Kill unverified readiness claims, broad routing, destructive shortcuts, weak rollback, and source-free operational advice.

Use this skill for:

- Vault key scheduled-deletion review
- scheduled key deletion cancellation review
- key rotation and key-version lifecycle planning
- data association and encrypted-resource dependency audit
- HSM/software/external key protection-mode risk review

## Lean operating rules

- Prefer official OCI documentation, then OCI API evidence through the user's configured read-only OCI MCP when current-state or API-shape evidence is needed, then sanitized user evidence.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad scope, broad permissions, destructive shortcuts, production claims, and live-guard dispatch without evidence.
- Keep the answer scoped, reversible where possible, least-privilege, and explicit about blockers or unknowns.
- Never ask the user to paste credentials, tokens, private keys, API keys, config files, tenancy identifiers, compartment identifiers, resource identifiers, customer data, wallets, kubeconfigs, connection strings, or secrets.

## References

Load these only when needed:

- [OCI Live Vault Key Destruction Guard Operations](references/vault-key-destruction-operations.md) — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
- [Safety checklist](references/safety-checklist.md) — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
- [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing documentation-based evidence, sampled read-only OCI API evidence, or sanitized user evidence.
- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, applying stress checks, or formatting the final answer.
- [Official sources](references/official-sources.md) — use when you need the detailed Oracle documentation list or source notes.

## Response minimum

Return, at minimum:

- the scoped target and evidence level,
- the main risks, control gaps, or routing decision,
- the safest next actions,
- the assumptions or blockers that prevent stronger conclusions.