{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T17:54:06.066Z",
  "record_id": "VXI-EXT-PROCUREMENT-K8S-OFFLINE-BOUND-TOKEN-01-v1",
  "record_kind": "external_reference",
  "title": "Kubernetes: Offline JWT validation after object deletion",
  "system": "Kubernetes",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does offline validation of a Kubernetes service-account JWT detect that its bound Pod was deleted?",
  "near_questions": [
    "Will offline JWT validation notice a deleted Pod?",
    "Does a valid signature prove the bound workload still exists?",
    "Is the relying service using TokenReview?",
    "Can a deleted-object token remain valid until expiry?",
    "Which audience accepts the service-account JWT?",
    "Was the bound object UID checked?",
    "Does Pod deletion end external agent access?",
    "What is the remaining token lifetime?",
    "Is the external token check current or offline?",
    "What evidence links deletion to access refusal?",
    "Can Tool Admission validate live Kubernetes token revocation?",
    "How does this differ from projected-token expiry?"
  ],
  "supported_claims": [
    {
      "claim": "An external service validating a service-account JWT offline does not check that its embedded object claims remain current. A token bound to a deleted object can still pass that validation until expiry. Kubernetes directs clients needing current bound-claim validation to the TokenReview API.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Revocation of every external session or proof that a relying service currently denies the token",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "An external service validating a service-account JWT offline does not check that its embedded object claims remain current. A token bound to a deleted object can still pass that validation until expiry. Kubernetes directs clients needing current bound-claim validation to the TokenReview API.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Kubernetes: Managing Service Accounts",
    "source_url": "https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-K8S-OFFLINE-BOUND-TOKEN-01-v1",
    "candidate_record_sha256": "858651c1bfa67f3258d39a91b5b95bd664f27a1ec197beef09d8de0fcfa2a793",
    "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": "An external service validating a service-account JWT offline does not check that its embedded object claims remain current. A token bound to a deleted object can still pass that validation until expiry. Kubernetes directs clients needing current bound-claim validation to the TokenReview API.",
    "required_buyer_context": "Token audience, expiry and bound object identity, without disclosing the token. Relying-service validation method and TokenReview response where applicable. Deletion time and dated evidence of the relying service access decision. Buyer deployment not inspected.",
    "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-17",
    "claim_to_check": "Does offline validation of a Kubernetes service-account JWT detect that its bound Pod was deleted?",
    "documented_statement": {
      "status": "documented",
      "statement": "An external service validating a service-account JWT offline does not check that its embedded object claims remain current. A token bound to a deleted object can still pass that validation until expiry. Kubernetes directs clients needing current bound-claim validation to the TokenReview API.",
      "source_ids": [
        "k8s-offline"
      ]
    },
    "buyer_evidence_required": [
      "Token audience, expiry and bound object identity, without disclosing the token.",
      "Relying-service validation method and TokenReview response where applicable.",
      "Deletion time and dated evidence of the relying service access decision."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline immediate external-access cutoff claims supported only by object deletion and offline signature validation; require current validation and access evidence."
    },
    "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": "k8s-offline",
        "url": "https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/",
        "final_url": "https://kubernetes.io/docs/reference/access-authn-authz/service-accounts-admin/",
        "title": "Kubernetes: Managing Service Accounts",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T17:50:55.721Z",
        "version_context": "Rolling documentation; TokenReview versus offline JWT validation",
        "sha256": "552638f6bae6f70959623fcea4174a703bcd41840f212aec7386f808814dc55c",
        "bytes": 573669,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Schema for ServiceAccount private claims"
        ]
      }
    ],
    "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": "An agent offboarding plan must identify how each relying service validates workload tokens, rather than assume Pod deletion ends every external session.",
      "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": "Token audience, expiry and bound object identity, without disclosing the token. Relying-service validation method and TokenReview response where applicable. Deletion time and dated evidence of the relying service access decision."
    },
    "buyer_relevance": "An agent offboarding plan must identify how each relying service validates workload tokens, rather than assume Pod deletion ends every external session.",
    "refusal_conditions": [
      "Decline immediate external-access cutoff claims supported only by object deletion and offline signature validation; require current validation and access evidence."
    ]
  },
  "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#kubernetes-offline-jwt-bound-object-deletion",
  "machine_readable_record": "/varexis-index/records/kubernetes-offline-jwt-bound-object-deletion.json"
}
