{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T20:21:57.226Z",
  "record_id": "VXI-EXT-PROCUREMENT-KUBERNETES-SECRET-LIST-01-v1",
  "record_kind": "external_reference",
  "title": "Kubernetes: Secret listing is not metadata-only access",
  "system": "Kubernetes RBAC",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a Kubernetes inventory role reveal secrets without a get permission?",
  "near_questions": [
    "Can an inventory role list secret values?",
    "Does removing get prevent Kubernetes Secret disclosure?",
    "What does watch permission expose for Secrets?",
    "Can workload creation affect secret access?",
    "Which namespace roles should a procurement review inspect?",
    "Does read-only cluster access mean metadata-only?",
    "What evidence supports a secret-isolation claim?",
    "Can a service identity gain access through workloads?",
    "Which role bindings belong in an access review?",
    "Does one denied request prove no other access path?",
    "When should an agent refuse a metadata-only assurance?",
    "Can I save a Kubernetes secret-access review?"
  ],
  "supported_claims": [
    {
      "claim": "Kubernetes documents that list and watch access can reveal Secret contents. It also identifies workload-creation permissions as another route to namespace resources. A review confined to the get verb therefore cannot establish secret isolation; inspect the complete role and workload authority.",
      "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": "Kubernetes documents that list and watch access can reveal Secret contents. It also identifies workload-creation permissions as another route to namespace resources. A review confined to the get verb therefore cannot establish secret isolation; inspect the complete role and workload authority.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-IAM-BOUNDARY-GRANTS-01-v1",
    "VXI-EXT-PROCUREMENT-AZURE-LOCK-PLANE-01-v1",
    "VXI-EXT-PROCUREMENT-CIRCLECI-CONTEXT-RESTRICTION-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Kubernetes RBAC secret and workload permissions",
    "source_url": "https://kubernetes.io/docs/concepts/security/rbac-good-practices/",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-KUBERNETES-SECRET-LIST-01-v1",
    "candidate_record_sha256": "922000bdfbd099979eb0fdf388fd4d3968cdf21eee883138d0b356aaff890b84",
    "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": "Kubernetes documents that list and watch access can reveal Secret contents. It also identifies workload-creation permissions as another route to namespace resources. A review confined to the get verb therefore cannot establish secret isolation; inspect the complete role and workload authority.",
    "required_buyer_context": "Cluster role bindings, namespace, Secret verbs and workload-creation permissions.",
    "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": "The inventory role cannot retrieve secret values.",
    "documented_statement": {
      "status": "documented",
      "statement": "Kubernetes documents that list and watch access can reveal Secret contents. It also identifies workload-creation permissions as another route to namespace resources. A review confined to the get verb therefore cannot establish secret isolation; inspect the complete role and workload authority.",
      "source_ids": [
        "kube-secrets"
      ]
    },
    "buyer_evidence_required": [
      "Effective roles and bindings for the inventory identity.",
      "Secret list/watch permissions and namespace scope.",
      "Workload creation authority and applicable admission controls."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Keep secret isolation unproven until all relevant permissions are evidenced."
    },
    "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": "kube-secrets",
        "url": "https://kubernetes.io/docs/concepts/security/rbac-good-practices/",
        "final_url": "https://kubernetes.io/docs/concepts/security/rbac-good-practices/",
        "title": "Kubernetes RBAC secret and workload permissions",
        "checked_on": "2026-10-14",
        "sha256": "5b04a441c70f4f3287ac999a1c56fd85ed5104c088c36f0c4d6c886fca771f08",
        "bytes": 514526
      }
    ],
    "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": "Save the specific permission gaps that prevent approving an inventory role as metadata-only.",
      "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": "RBAC bindings, workload authority and admission policy changes."
    }
  },
  "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-secret-list-disclosure",
  "machine_readable_record": "/varexis-index/records/kubernetes-secret-list-disclosure.json"
}