{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:09:18.442Z",
  "record_id": "VXI-EXT-PROCUREMENT-ENTRA-FEDERATED-CREDENTIAL-EXACT-SUBJECT-BRANCH-01-v1",
  "record_kind": "external_reference",
  "title": "Entra federated credential subject matching",
  "system": "Microsoft Entra",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an Entra federated credential for one GitHub branch automatically trust every branch in that repository?",
  "near_questions": [
    "Can a branch-specific Entra trust accept another GitHub branch?",
    "How does a GitHub environment alter an Entra federated subject?",
    "Does standard Entra federation support wildcard branch subjects?",
    "What subject evidence is needed before accepting workload federation?"
  ],
  "supported_claims": [
    {
      "claim": "The standard federated-credential guide requires issuer and subject values to match the external token. Its GitHub configuration distinguishes environment, branch, pull request and tag subjects. The documented branch and tag setup does not support wildcard patterns. Repository identity alone does not describe the configured subject boundary.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A claim about all flexible federated-credential features",
    "The buyer credential and presented token claims are not observed.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "The standard federated-credential guide requires issuer and subject values to match the external token. Its GitHub configuration distinguishes environment, branch, pull request and tag subjects. The documented branch and tag setup does not support wildcard patterns. Repository identity alone does not describe the configured subject boundary.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Create a trust relationship between an app and an external identity provider - Microsoft Entra Workload ID | Microsoft Learn",
    "source_url": "https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation-create-trust",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-ENTRA-FEDERATED-CREDENTIAL-EXACT-SUBJECT-BRANCH-01-v1",
    "candidate_record_sha256": "5eed46a59a46512e299c86496e08b69fef4c211012c78d59b1b94eb1e917506b",
    "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 standard federated-credential guide requires issuer and subject values to match the external token. Its GitHub configuration distinguishes environment, branch, pull request and tag subjects. The documented branch and tag setup does not support wildcard patterns. Repository identity alone does not describe the configured subject boundary.",
    "required_buyer_context": "Federated credential issuer, subject and audience; GitHub workflow trigger, environment and token subject; Credential type and applicable provider documentation. 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": "Does an Entra federated credential for one GitHub branch automatically trust every branch in that repository?",
    "documented_statement": {
      "status": "documented",
      "statement": "The standard federated-credential guide requires issuer and subject values to match the external token. Its GitHub configuration distinguishes environment, branch, pull request and tag subjects. The documented branch and tag setup does not support wildcard patterns. Repository identity alone does not describe the configured subject boundary.",
      "source_ids": [
        "entra-federated"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Compare the actual token subject with the specific credential type and configured subject.",
      "source_ids": [
        "entra-federated"
      ]
    },
    "buyer_evidence_required": [
      "Federated credential issuer, subject and audience",
      "GitHub workflow trigger, environment and token subject",
      "Credential type and applicable provider documentation"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Reject repository-wide trust assumptions derived from one branch-specific credential."
    },
    "unknowns": "The buyer credential and presented token claims are not observed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer credential and presented token claims are not observed."
    },
    "evidence_sources": [
      {
        "source_id": "entra-federated",
        "url": "https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation-create-trust",
        "final_url": "https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation-create-trust",
        "status": 200,
        "captured_at_utc": "2026-10-24T16:47:20.500Z",
        "sha256": "28f2da8a954a4ca3e7f110c351eea07abef738525305e4ae26e95abe5d2a1ba6",
        "bytes": 96672,
        "title": "Create a trust relationship between an app and an external identity provider - Microsoft Entra Workload ID | Microsoft Learn",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Issuer and subject matching",
          "GitHub entity types and branch/tag restrictions"
        ],
        "version_context": "Rolling official documentation captured 2026-10-24; installed API/SDK version, account tier and buyer configuration require verification."
      }
    ],
    "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 a CI agent’s token-minting boundary aligned with the approved workflow.",
      "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 documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Keep a CI agent’s token-minting boundary aligned with the approved workflow.",
    "refusal_conditions": [
      "Reject repository-wide trust assumptions derived from one branch-specific credential."
    ]
  },
  "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": "Keep a CI agent’s token-minting boundary aligned with the approved workflow.",
    "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#entra-federated-credential-exact-subject-branch",
  "machine_readable_record": "/varexis-index/records/entra-federated-credential-exact-subject-branch.json"
}
