{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T20:21:57.226Z",
  "record_id": "VXI-EXT-PROCUREMENT-VAULT-STATIC-LEASE-01-v1",
  "record_kind": "external_reference",
  "title": "Vault leases: Static KV values are not dynamic credentials",
  "system": "HashiCorp Vault",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Vault lease policy prove that a copied static password expires?",
  "near_questions": [
    "Does storing a password in Vault make it expire?",
    "Do static KV secrets have dynamic-secret leases?",
    "Does a returned duration prove a revocable lease exists?",
    "Which identifier supports a Vault lease review?",
    "Can revoking a Vault token invalidate every copied static password?",
    "What evidence proves downstream credential rotation?",
    "How do dynamic secrets differ from stored values?",
    "Which engine is relevant to an expiry claim?",
    "Can product-level lease support establish this credential lifecycle?",
    "What should procurement request for static secret expiry?",
    "When should automatic revocation remain unproven?",
    "Can I save a Vault credential-lifecycle review?"
  ],
  "supported_claims": [
    {
      "claim": "Vault documents leases for dynamic secrets and service tokens, while the key/value backend does not issue secret leases even when a duration is returned. A static value stored in Vault therefore needs its own credential-lifecycle evidence. Storage in a lease-capable product is not evidence of automatic downstream expiry.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Vault documents leases for dynamic secrets and service tokens, while the key/value backend does not issue secret leases even when a duration is returned. A static value stored in Vault therefore needs its own credential-lifecycle evidence. Storage in a lease-capable product is not evidence of automatic downstream expiry.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-AUTH0-REFRESH-REUSE-01-v1",
    "VXI-EXT-PROCUREMENT-TERRAFORM-SENSITIVE-STATE-01-v1",
    "VXI-EXT-PROCUREMENT-PULUMI-SECRET-RUNTIME-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Vault leases and static KV exception",
    "source_url": "https://developer.hashicorp.com/vault/docs/concepts/lease",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-VAULT-STATIC-LEASE-01-v1",
    "candidate_record_sha256": "39852b4527c9e7d0e23c50290ecf4818cf284070fa87a102a3d6b0ec0b7723b6",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Vault documents leases for dynamic secrets and service tokens, while the key/value backend does not issue secret leases even when a duration is returned. A static value stored in Vault therefore needs its own credential-lifecycle evidence. Storage in a lease-capable product is not evidence of automatic downstream expiry.",
    "required_buyer_context": "Secrets engine, credential type, lease identifier and downstream credential lifecycle.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-14",
    "claim_to_check": "Every value stored in Vault automatically expires or is revoked through a lease.",
    "documented_statement": {
      "status": "documented",
      "statement": "Vault documents leases for dynamic secrets and service tokens, while the key/value backend does not issue secret leases even when a duration is returned. A static value stored in Vault therefore needs its own credential-lifecycle evidence. Storage in a lease-capable product is not evidence of automatic downstream expiry.",
      "source_ids": [
        "vault-lease"
      ]
    },
    "buyer_evidence_required": [
      "Secrets engine and whether the value is dynamic or static KV.",
      "Actual lease identifier and revocation mechanism where applicable.",
      "Downstream rotation or invalidation evidence for static credentials."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not promise expiry of a static credential solely from Vault storage."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "vault-lease",
        "url": "https://developer.hashicorp.com/vault/docs/concepts/lease",
        "final_url": "https://developer.hashicorp.com/vault/docs/concepts/lease",
        "title": "Vault leases and static KV exception",
        "checked_on": "2026-10-14",
        "sha256": "95c97c14df62551540a1f981fddf99a6e24b875eaf94a1092084914f8be241cd",
        "bytes": 259375
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Preserve the engine and lifecycle distinction behind a credential-expiry assessment.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Engine changes, credential type and downstream revocation process."
    }
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#vault-static-secret-lease-boundary",
  "machine_readable_record": "/varexis-index/records/vault-static-secret-lease-boundary.json"
}