{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T15:12:44.585Z",
  "record_id": "VXI-EXT-PROCUREMENT-KUBERNETES-RBAC-BIND-ESCALATE-DELEGATION-01-v1",
  "record_kind": "external_reference",
  "title": "Kubernetes: Role administration has explicit escalation exceptions",
  "system": "Kubernetes",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Do Kubernetes RBAC escalation checks prevent every role administrator from delegating stronger permissions?",
  "near_questions": [
    "Can an agent with bind attach a stronger Kubernetes role?",
    "What does the escalate verb permit in RBAC?",
    "Do create and update privileges tell the whole delegation story?",
    "Which permissions are checked before creating a RoleBinding?",
    "Can a role administrator delegate rights it does not otherwise hold?",
    "What should a buyer review before automating RBAC changes?"
  ],
  "supported_claims": [
    {
      "claim": "Kubernetes normally requires a role author to possess the permissions being added and a binding author to possess the permissions being delegated. The explicit escalate and bind verbs provide exceptions. Reviewing ordinary create or update privileges alone misses these distinct delegation authorities.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Effective authorisation in a buyer cluster or admission-policy enforcement",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for the existing Tool Admission and Audit Coverage executables"
  ],
  "public_summary": "Kubernetes normally requires a role author to possess the permissions being added and a binding author to possess the permissions being delegated. The explicit escalate and bind verbs provide exceptions. Reviewing ordinary create or update privileges alone misses these distinct delegation authorities.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Kubernetes RBAC authorization",
    "source_url": "https://kubernetes.io/docs/reference/access-authn-authz/rbac/",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-KUBERNETES-RBAC-BIND-ESCALATE-DELEGATION-01-v1",
    "candidate_record_sha256": "a0efcc2c7035d88072e7204384be2990fa8124a6bad8ea5a45913b997d2ad2f0",
    "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 normally requires a role author to possess the permissions being added and a binding author to possess the permissions being delegated. The explicit escalate and bind verbs provide exceptions. Reviewing ordinary create or update privileges alone misses these distinct delegation authorities.",
    "required_buyer_context": "The acting principal and effective RBAC grants. The target role permissions and binding scope. Any bind or escalate permissions and the requested change. 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-18",
    "claim_to_check": "Do Kubernetes RBAC escalation checks prevent every role administrator from delegating stronger permissions?",
    "documented_statement": {
      "status": "documented",
      "statement": "Kubernetes normally requires a role author to possess the permissions being added and a binding author to possess the permissions being delegated. The explicit escalate and bind verbs provide exceptions. Reviewing ordinary create or update privileges alone misses these distinct delegation authorities.",
      "source_ids": [
        "rbac"
      ]
    },
    "buyer_evidence_required": [
      "The acting principal and effective RBAC grants.",
      "The target role permissions and binding scope.",
      "Any bind or escalate permissions and the requested change."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not approve a bounded role-administration claim without checking explicit bind and escalate authority."
    },
    "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": "rbac",
        "url": "https://kubernetes.io/docs/reference/access-authn-authz/rbac/",
        "final_url": "https://kubernetes.io/docs/reference/access-authn-authz/rbac/",
        "title": "Kubernetes RBAC authorization",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T15:02:00.337Z",
        "version_context": "Rolling official documentation captured on 2026-10-18; feature and deployment limits apply",
        "sha256": "31644b77dadbe0a821a46f7e2840da29bb1b80ddca024523d5e63f027943e2e8",
        "bytes": 626823,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Do Kubernetes RBAC escalation checks prevent every role administrator from delegating stronger permissions?"
        ]
      }
    ],
    "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": "A platform owner must inspect special RBAC privileges before allowing an agent to administer roles or bindings.",
      "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": "The acting principal and effective RBAC grants. The target role permissions and binding scope. Any bind or escalate permissions and the requested change."
    },
    "buyer_relevance": "A platform owner must inspect special RBAC privileges before allowing an agent to administer roles or bindings.",
    "refusal_conditions": [
      "Do not approve a bounded role-administration claim without checking explicit bind and escalate authority."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "A platform owner must inspect special RBAC privileges before allowing an agent to administer roles or bindings.",
    "comparison_role": "supplementary_discovery"
  },
  "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-rbac-bind-escalate-delegation",
  "machine_readable_record": "/varexis-index/records/kubernetes-rbac-bind-escalate-delegation.json"
}
