{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T14:13:51.913Z",
  "record_id": "VXI-EXT-PROCUREMENT-GITGUARDIAN-REVOCATION-01-v1",
  "record_kind": "external_reference",
  "title": "GitGuardian: Revocation and incident state",
  "system": "GitGuardian",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a resolved GitGuardian incident prove the exposed credential was revoked?",
  "near_questions": [
    "Is this provider supported for integrated revocation?",
    "Was the secret valid before revocation?",
    "Who had Full Access to the incident?",
    "Did a revocation operation occur?",
    "Does the provider confirm revocation directly?",
    "Was a later validity check completed?",
    "When was the credential last checked?",
    "Which playbook resolved the incident?",
    "Could an ignore rule explain its state?",
    "Is the credential still used by a workload?",
    "Does the timeline support the claimed outcome?",
    "Can I save the remediation evidence boundary?"
  ],
  "supported_claims": [
    {
      "claim": "Integrated revocation requires a supported provider, a valid secret and Full Access to the incident. The documented auto-resolution path also depends on a playbook. Many provider APIs do not directly confirm revocation; GitGuardian uses later validity checks. Preserve the revocation and validity evidence separately from the incident label.",
      "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": "Integrated revocation requires a supported provider, a valid secret and Full Access to the incident. The documented auto-resolution path also depends on a playbook. Many provider APIs do not directly confirm revocation; GitGuardian uses later validity checks. Preserve the revocation and validity evidence separately from the incident label.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "GitGuardian: Remediate incidents",
    "source_url": "https://docs.gitguardian.com/internal-monitoring/remediate/remediate-incidents",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GITGUARDIAN-REVOCATION-01-v1",
    "candidate_record_sha256": "c6bf00578c2ea6b9c5b1d7f4316c917e041b59a0af58de267529dee2a9db42b7",
    "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": "Integrated revocation requires a supported provider, a valid secret and Full Access to the incident. The documented auto-resolution path also depends on a playbook. Many provider APIs do not directly confirm revocation; GitGuardian uses later validity checks. Preserve the revocation and validity evidence separately from the incident label.",
    "required_buyer_context": "Provider, incident timeline, revocation event, validity timestamps and playbook configuration. Effective configuration and dated operational evidence have not been 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-16",
    "claim_to_check": "A resolved incident is sufficient proof of credential revocation.",
    "documented_statement": {
      "status": "documented",
      "statement": "Integrated revocation requires a supported provider, a valid secret and Full Access to the incident. The documented auto-resolution path also depends on a playbook. Many provider APIs do not directly confirm revocation; GitGuardian uses later validity checks. Preserve the revocation and validity evidence separately from the incident label.",
      "source_ids": [
        "gitguardian"
      ]
    },
    "buyer_evidence_required": [
      "Provider support and revocation event.",
      "Subsequent validity result with time.",
      "Incident timeline and enabled resolution playbook."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require provider and validity evidence before asserting the credential is no longer usable."
    },
    "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": "gitguardian",
        "url": "https://docs.gitguardian.com/internal-monitoring/remediate/remediate-incidents",
        "final_url": "https://docs.gitguardian.com/internal-monitoring/remediate/remediate-incidents",
        "title": "GitGuardian: Remediate incidents",
        "checked_on": "2026-10-16",
        "sha256": "1dcb9909184d9eeaf343b507345a6277a4e7dfdb3029a4f9fe62b9b9afa852d4",
        "bytes": 69831
      }
    ],
    "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 distinction between workflow closure and credential invalidation.",
      "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": "Provider, incident timeline, revocation event, validity timestamps and playbook configuration."
    }
  },
  "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#gitguardian-revocation-validity-and-incident-state",
  "machine_readable_record": "/varexis-index/records/gitguardian-revocation-validity-and-incident-state.json"
}