{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-14T01:25:58.088Z",
  "record_id": "VXI-EXT-PROCUREMENT-GCP-KEY-LIFECYCLE-01-v1",
  "record_kind": "external_reference",
  "title": "Google Cloud keys: Expiry, rotation and workload continuity",
  "system": "Google Cloud service-account keys",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Do user-managed Google Cloud service-account keys expire automatically by default?",
  "near_questions": [
    "Do user-managed service-account keys expire by default?",
    "Does key expiry prove rotation has completed?",
    "Can an expiring key interrupt a production workload?",
    "What evidence shows an old key was removed?",
    "Which workloads still use the credential being replaced?",
    "Can procurement review key lifecycle without seeing secrets?",
    "Does a rotation policy prove it is followed?",
    "What should an agent ask about temporary key access?",
    "How do expiration and replacement differ?",
    "Which inventory facts belong in a saved credential review?",
    "Can I preserve the documented key-lifecycle boundary?",
    "When should service-account authentication be reassessed?"
  ],
  "supported_claims": [
    {
      "claim": "Google states that keys created through IAM have no expiry by default and remain valid until deleted. Expiry and rotation are separate lifecycle choices, and expiry can interrupt workloads. Request the actual key inventory and replacement process rather than assuming automatic expiration proves credential hygiene.",
      "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": "Google states that keys created through IAM have no expiry by default and remain valid until deleted. Expiry and rotation are separate lifecycle choices, and expiry can interrupt workloads. Request the actual key inventory and replacement process rather than assuming automatic expiration proves credential hygiene.",
  "related_record_ids": [
    "VXI-EXT-PROCUREMENT-GITHUB-PUSH-BYPASS-01-v1",
    "VXI-EXT-PROCUREMENT-GITLAB-MASKING-01-v1",
    "VXI-EXT-PROCUREMENT-SLACK-SCIM-DEACTIVATION-01-v1",
    "VXI-EXT-PROCUREMENT-AWS-LAST-ACCESS-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Google Cloud service account key lifecycle",
    "source_url": "https://cloud.google.com/iam/docs/best-practices-for-managing-service-account-keys",
    "checked_on": "2026-10-14",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GCP-KEY-LIFECYCLE-01-v1",
    "candidate_record_sha256": "d9e27e372b7ce79ef5a73399b1396a3002dfb2a567967af3b1fbedeb51b729f0",
    "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": "Google states that keys created through IAM have no expiry by default and remain valid until deleted. Expiry and rotation are separate lifecycle choices, and expiry can interrupt workloads. Request the actual key inventory and replacement process rather than assuming automatic expiration proves credential hygiene.",
    "required_buyer_context": "User-managed key inventory, expiry configuration, rotation process and dependent workload.",
    "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-14",
    "claim_to_check": "Service-account keys automatically expire and therefore need no lifecycle review.",
    "documented_statement": {
      "status": "documented",
      "statement": "Google states that keys created through IAM have no expiry by default and remain valid until deleted. Expiry and rotation are separate lifecycle choices, and expiry can interrupt workloads. Request the actual key inventory and replacement process rather than assuming automatic expiration proves credential hygiene.",
      "source_ids": [
        "gcp-keyexpiry"
      ]
    },
    "buyer_evidence_required": [
      "Key inventory, age and configured expiry without disclosing secret values",
      "Documented replacement and removal process",
      "Evidence that dependent workloads use the intended current credential"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer expiry or completed rotation from a policy statement alone."
    },
    "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": "gcp-keyexpiry",
        "url": "https://cloud.google.com/iam/docs/best-practices-for-managing-service-account-keys",
        "final_url": "https://docs.cloud.google.com/iam/docs/best-practices-for-managing-service-account-keys",
        "title": "Google Cloud service account key lifecycle",
        "checked_on": "2026-10-14",
        "sha256": "6f09596ea0379a04fd8ce9f43db9a1e63d702d13717716cf9d2b79c13f03c5c7",
        "bytes": 212542
      }
    ],
    "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 lifecycle evidence checklist for a supplier service identity.",
      "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": "Recheck key creation, rotation records and workload authentication changes."
    }
  },
  "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#google-cloud-service-key-expiry-evidence",
  "machine_readable_record": "/varexis-index/records/google-cloud-service-key-expiry-evidence.json"
}