{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T07:59:18.009Z",
  "record_id": "VXI-EXT-PROCUREMENT-GCP-PERIMETER-01-v1",
  "record_kind": "external_reference",
  "title": "VPC Service Controls: A perimeter is separate from IAM",
  "system": "Google Cloud",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Google Cloud service perimeter replace resource permissions?",
  "near_questions": [
    "Does VPC Service Controls replace IAM?",
    "Which services are restricted?",
    "Which resources are inside the perimeter?",
    "What ingress rule admits the client?",
    "Which egress operations are allowed?",
    "Are unsupported services covered identically?",
    "Does network origin alone establish identity authority?",
    "Which access level applies?",
    "What audit evidence records perimeter decisions?",
    "Can a permitted identity still be overprivileged?",
    "When should an agent leave isolation unproven?",
    "Can I save the perimeter-and-IAM review?"
  ],
  "supported_claims": [
    {
      "claim": "VPC Service Controls supplies context-based perimeter checks in addition to IAM. Ingress/egress rules and supported-service scope determine which paths it covers. A perimeter configuration does not establish least-privilege identities or coverage for every service operation.",
      "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": "VPC Service Controls supplies context-based perimeter checks in addition to IAM. Ingress/egress rules and supported-service scope determine which paths it covers. A perimeter configuration does not establish least-privilege identities or coverage for every service operation.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Google Cloud VPC Service Controls overview",
    "source_url": "https://docs.cloud.google.com/vpc-service-controls/docs/overview",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-GCP-PERIMETER-01-v1",
    "candidate_record_sha256": "92da73048b11178f8870057d26e4063f976904a4a3be5a45570f5110e093e8ac",
    "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": "VPC Service Controls supplies context-based perimeter checks in addition to IAM. Ingress/egress rules and supported-service scope determine which paths it covers. A perimeter configuration does not establish least-privilege identities or coverage for every service operation.",
    "required_buyer_context": "Perimeter resources, supported services, access rules and IAM. Effective buyer configuration and dated operational evidence are required.",
    "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 service perimeter replaces identity authorization for all services.",
    "documented_statement": {
      "status": "documented",
      "statement": "VPC Service Controls supplies context-based perimeter checks in addition to IAM. Ingress/egress rules and supported-service scope determine which paths it covers. A perimeter configuration does not establish least-privilege identities or coverage for every service operation.",
      "source_ids": [
        "gcp-perimeter"
      ]
    },
    "buyer_evidence_required": [
      "Restricted services and resource inventory.",
      "Ingress, egress and access-level rules.",
      "Effective IAM permissions."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Require both identity and perimeter evidence before approving data isolation."
    },
    "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-perimeter",
        "url": "https://docs.cloud.google.com/vpc-service-controls/docs/overview",
        "final_url": "https://docs.cloud.google.com/vpc-service-controls/docs/overview",
        "title": "Google Cloud VPC Service Controls overview",
        "checked_on": "2026-10-16",
        "sha256": "b04055d0a5971db975eef85e1cf0305a50ef64ec6f8dc3603a6b9d94cc9bdead",
        "bytes": 155684
      }
    ],
    "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": "Preserve two separate control layers in a cloud data-sharing decision.",
      "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": "Perimeter resources, supported services, access rules and IAM"
    }
  },
  "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#gcp-service-perimeter-iam-complement",
  "machine_readable_record": "/varexis-index/records/gcp-service-perimeter-iam-complement.json"
}