{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "pub-2-tranche-52-v1",
  "route_id": "agentic_reviewed_spiffe_signing_certificate_not_workload",
  "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-SIGNING-CERTIFICATE-NOT-WORKLOAD-01-v1",
  "question": "Can a SPIFFE CA signing certificate authenticate as the workload it issues credentials for?",
  "answer": "The pinned X509-SVID specification reserves caller authentication for leaf certificates and prohibits using signing certificates for authentication. A leaf must have cA false, lack keyCertSign and cRLSign, and carry a SPIFFE ID with a non-root path. Possessing valid signing material is not interchangeable with presenting a valid workload leaf.",
  "records": [
    {
      "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-SIGNING-CERTIFICATE-NOT-WORKLOAD-01-v1",
      "url": "/varexis-index/records/spiffe-signing-certificate-not-workload.json",
      "content_sha256": "3c761098f88c8e9b9d134c40642cd3d69d6d98753d5a22be8b82549787758ab3",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-24T21:56:24.175Z",
        "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-SIGNING-CERTIFICATE-NOT-WORKLOAD-01-v1",
        "record_kind": "external_reference",
        "title": "SPIFFE signing authority versus caller identity",
        "system": "SPIFFE",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Can a SPIFFE CA signing certificate authenticate as the workload it issues credentials for?",
        "near_questions": [
          "Can a SPIFFE signing certificate be used as a client identity?",
          "Does a trusted SVID issuer count as an authenticated workload?",
          "Which leaf constraints distinguish SPIFFE callers from issuers?",
          "Is a SPIFFE root identity enough for a workload login?"
        ],
        "supported_claims": [
          {
            "claim": "The pinned X509-SVID specification reserves caller authentication for leaf certificates and prohibits using signing certificates for authentication. A leaf must have cA false, lack keyCertSign and cRLSign, and carry a SPIFFE ID with a non-root path. Possessing valid signing material is not interchangeable with presenting a valid workload leaf.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Actual key custody and the caller are unobserved.",
          "Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.",
          "Buyer deployment testing, live runtime enforcement, certification or permission to act",
          "Expanded capabilities or licences for existing INDEX executables"
        ],
        "public_summary": "The pinned X509-SVID specification reserves caller authentication for leaf certificates and prohibits using signing certificates for authentication. A leaf must have cA false, lack keyCertSign and cRLSign, and carry a SPIFFE ID with a non-root path. Possessing valid signing material is not interchangeable with presenting a valid workload leaf.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "The X.509 SPIFFE Verifiable Identity Document",
          "source_url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/X509-SVID.md",
          "checked_on": "2026-10-24",
          "candidate_record_id": "VXI-EXT-PROCUREMENT-SPIFFE-SIGNING-CERTIFICATE-NOT-WORKLOAD-01-v1",
          "candidate_record_sha256": "32d49a1b5d8c3a8b156eb083a55794e71f2d7f30e7964554d409d318376ee7cc",
          "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": "The pinned X509-SVID specification reserves caller authentication for leaf certificates and prohibits using signing certificates for authentication. A leaf must have cA false, lack keyCertSign and cRLSign, and carry a SPIFFE ID with a non-root path. Possessing valid signing material is not interchangeable with presenting a valid workload leaf.",
          "required_buyer_context": "Leaf and chain certificate fields; Expected workload SPIFFE ID; Caller-to-business-principal mapping for the requested action. 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-24",
          "claim_to_check": "Can a SPIFFE CA signing certificate authenticate as the workload it issues credentials for?",
          "documented_statement": {
            "status": "documented",
            "statement": "The pinned X509-SVID specification reserves caller authentication for leaf certificates and prohibits using signing certificates for authentication. A leaf must have cA false, lack keyCertSign and cRLSign, and carry a SPIFFE ID with a non-root path. Possessing valid signing material is not interchangeable with presenting a valid workload leaf.",
            "source_ids": [
              "spiffe-x509"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Keep credential-issuing authority separate from the identity requesting a tool action. This is a source-based review decision, not an observed deployment result.",
            "source_ids": [
              "spiffe-x509"
            ]
          },
          "buyer_evidence_required": [
            "Leaf and chain certificate fields",
            "Expected workload SPIFFE ID",
            "Caller-to-business-principal mapping for the requested action"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Do not authorize a caller using a CA certificate in place of its workload leaf."
          },
          "unknowns": "Actual key custody and the caller are unobserved.",
          "unknown_finding": {
            "status": "unknown",
            "statement": "Actual key custody and the caller are unobserved."
          },
          "evidence_sources": [
            {
              "source_id": "spiffe-x509",
              "url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/X509-SVID.md",
              "final_url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/X509-SVID.md",
              "status": 200,
              "captured_at_utc": "2026-10-24T21:45:00.240Z",
              "sha256": "a7dc93995458b750ad6622b3520e91aba21ff9712fa9ec3d16cefce234c9176e",
              "bytes": 14412,
              "title": "The X.509 SPIFFE Verifiable Identity Document",
              "hash_basis": "Decoded HTTP response body bytes",
              "rights_review": "Original factual paraphrase and source metadata only; Apache-2.0 repository captures retained privately and not redistributed.",
              "checked_on": "2026-10-24",
              "capture_status": 200,
              "claim_review_completed": true,
              "reviewed_sections": [
                "2. SPIFFE ID",
                "5.2. Leaf Validation",
                "3.1. Leaf Certificates",
                "3.2. Signing Certificates"
              ],
              "version_context": "Pinned spiffe/spiffe revision 49a9cbbc018c39ec6643ad3301632f9f4549258b captured 2026-10-24. Documentation review, not evidence that a buyer implementation conforms."
            }
          ],
          "observed_deployment": false,
          "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
          "paid_value": {
            "decision_context": "Keep credential-issuing authority separate from the identity requesting a tool action.",
            "free": "Complete review, sources, practical questions 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": "Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome."
          },
          "buyer_relevance": "Keep credential-issuing authority separate from the identity requesting a tool action.",
          "refusal_conditions": [
            "Do not authorize a caller using a CA certificate in place of its workload leaf."
          ]
        },
        "niche": {
          "niche_id": "agent-authority-action-evidence",
          "label": "Agent Authority & Action Evidence",
          "classification_id": "identity",
          "classification_label": "Agent Identity, Credentials & Delegation",
          "topic_id": "identity",
          "buyer_intent": "Keep credential-issuing authority separate from the identity requesting a tool action.",
          "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#spiffe-signing-certificate-not-workload",
        "machine_readable_record": "/varexis-index/records/spiffe-signing-certificate-not-workload.json"
      }
    }
  ],
  "access": {
    "mode": "exact_http_only",
    "payment_required": false,
    "purchase_url": null,
    "mcp_preview_available": false,
    "paid_saved_retrieval_available": false,
    "natural_language_search_qualified": false
  },
  "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.",
  "content_sha256": "0d908b0f75059dd2bb32061303f8326ebb05a3284d4372f497a96ab8fe0a2703"
}
