{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "pub-2-tranche-52-v1",
  "route_id": "agentic_reviewed_spiffe_x509_multiple_uri_rejection",
  "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-X509-MULTIPLE-URI-REJECTION-01-v1",
  "question": "Can an X509-SVID with two URI SAN identities be accepted if its certificate chain verifies?",
  "answer": "The pinned X509-SVID specification requires exactly one URI subject alternative name and one SPIFFE ID. Validators must reject more than one URI SAN, even when ordinary certificate-path validation succeeds. Other SAN types may be present. The identity selection rule prevents a verifier from arbitrarily choosing which workload identity to authorize.",
  "records": [
    {
      "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-X509-MULTIPLE-URI-REJECTION-01-v1",
      "url": "/varexis-index/records/spiffe-x509-multiple-uri-rejection.json",
      "content_sha256": "175f0d11949594c9fe26ad381189c92067757fbbb8a5a45fbd2df30bacc574d6",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-24T21:56:24.175Z",
        "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-X509-MULTIPLE-URI-REJECTION-01-v1",
        "record_kind": "external_reference",
        "title": "SPIFFE identity ambiguity in certificates",
        "system": "SPIFFE",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Can an X509-SVID with two URI SAN identities be accepted if its certificate chain verifies?",
        "near_questions": [
          "Does a valid certificate chain resolve two SPIFFE identities?",
          "May I pick the first URI SAN from an X509-SVID?",
          "Why can a SPIFFE certificate pass PKI checks yet fail identity validation?",
          "How many URI SANs may an X509-SVID contain?"
        ],
        "supported_claims": [
          {
            "claim": "The pinned X509-SVID specification requires exactly one URI subject alternative name and one SPIFFE ID. Validators must reject more than one URI SAN, even when ordinary certificate-path validation succeeds. Other SAN types may be present. The identity selection rule prevents a verifier from arbitrarily choosing which workload identity to authorize.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "No buyer certificate or validator output has been inspected.",
          "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 requires exactly one URI subject alternative name and one SPIFFE ID. Validators must reject more than one URI SAN, even when ordinary certificate-path validation succeeds. Other SAN types may be present. The identity selection rule prevents a verifier from arbitrarily choosing which workload identity to authorize.",
        "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-X509-MULTIPLE-URI-REJECTION-01-v1",
          "candidate_record_sha256": "4056ed9949264925c0dfbed295e100dfb0d1f96eeaa676afcd87ee88fb7e48ca",
          "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 requires exactly one URI subject alternative name and one SPIFFE ID. Validators must reject more than one URI SAN, even when ordinary certificate-path validation succeeds. Other SAN types may be present. The identity selection rule prevents a verifier from arbitrarily choosing which workload identity to authorize.",
          "required_buyer_context": "Presented certificate and SAN types; SPIFFE-aware validation result; Expected workload identity and deployed validation-library version. 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 an X509-SVID with two URI SAN identities be accepted if its certificate chain verifies?",
          "documented_statement": {
            "status": "documented",
            "statement": "The pinned X509-SVID specification requires exactly one URI subject alternative name and one SPIFFE ID. Validators must reject more than one URI SAN, even when ordinary certificate-path validation succeeds. Other SAN types may be present. The identity selection rule prevents a verifier from arbitrarily choosing which workload identity to authorize.",
            "source_ids": [
              "spiffe-x509"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Reject ambiguous workload identity before mapping a certificate to tool authority. This is a source-based review decision, not an observed deployment result.",
            "source_ids": [
              "spiffe-x509"
            ]
          },
          "buyer_evidence_required": [
            "Presented certificate and SAN types",
            "SPIFFE-aware validation result",
            "Expected workload identity and deployed validation-library version"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Do not choose one URI identity from a certificate that violates the single-URI rule."
          },
          "unknowns": "No buyer certificate or validator output has been inspected.",
          "unknown_finding": {
            "status": "unknown",
            "statement": "No buyer certificate or validator output has been inspected."
          },
          "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": "Reject ambiguous workload identity before mapping a certificate to tool authority.",
            "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": "Reject ambiguous workload identity before mapping a certificate to tool authority.",
          "refusal_conditions": [
            "Do not choose one URI identity from a certificate that violates the single-URI rule."
          ]
        },
        "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": "Reject ambiguous workload identity before mapping a certificate to tool authority.",
          "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-x509-multiple-uri-rejection",
        "machine_readable_record": "/varexis-index/records/spiffe-x509-multiple-uri-rejection.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": "69acb6b8bbadc118e580f638bb8ce077680a27f49f7dec79f1f947b576df3099"
}
