{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-11-13T21:26:59.827748+00:00",
  "record_id": "VXI-EXT-SUP78-NCSC-LAYERED-SEPARATION-RESPONSIBILITY-01-v1",
  "record_kind": "external_reference",
  "title": "Application tenancy does not describe the whole underlying separation boundary",
  "system": "National Cyber Security Centre",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can a community SaaS label alone establish the isolation controls of an MCP service built on public infrastructure?",
  "near_questions": [
    "Does a SaaS tenancy label describe underlying IaaS separation?",
    "Who implements security functions at each service layer?",
    "Can a layered service inherit assurance without scope evidence?",
    "Which stack evidence is needed for sensitive cloud-service use?"
  ],
  "supported_claims": [
    {
      "claim": "NCSC Principle 8 distinguishes application-level separation in a layered service from underlying public-IaaS hypervisor controls. It recommends identifying which party implements each security function and understanding the underlying stack for sensitive uses.",
      "reliance": "PRIMARY_DOCUMENTATION_REVIEW_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "NCSC cloud/supply-chain guidance, not a standalone statutory obligation. Apply only to the relevant supplier service and responsibility boundary; cited older standards are not asserted to be current.",
    "No tenant-isolation test, data-residency conclusion or inherited certification is supplied.",
    "Layered services can have appropriate separation; different controls at different layers do not by themselves establish an isolation failure.",
    "No supplier approval, legal advice, certification, runtime verification or new paid capability."
  ],
  "public_summary": "NCSC Principle 8 distinguishes application-level separation in a layered service from underlying public-IaaS hypervisor controls. It recommends identifying which party implements each security function and understanding the underlying stack for sensitive uses. Review implication: A community SaaS label alone does not establish the complete isolation boundary or transfer assurance from an underlying provider. No tenant-isolation testing occurred.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "NCSC Cloud Security Principle 8",
    "source_url": "https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-8-supply-chain-security",
    "checked_on": "2026-11-13",
    "candidate_record_id": "VXI-EXT-SUP78-NCSC-LAYERED-SEPARATION-RESPONSIBILITY-01-v1",
    "candidate_record_sha256": "45837ce2d853a075351ba589159ed753bd7a4fcdb7688013f2a5a33ee1bf39a1",
    "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": "NCSC Principle 8 distinguishes application-level separation in a layered service from underlying public-IaaS hypervisor controls. It recommends identifying which party implements each security function and understanding the underlying stack for sensitive uses. Review implication: A community SaaS label alone does not establish the complete isolation boundary or transfer assurance from an underlying provider. No tenant-isolation testing occurred.",
    "required_buyer_context": "Service stack and tenancy model; Separation control and responsible party by layer; Scope of assurance evidence for each relevant layer",
    "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",
    "applicability_status": "NCSC cloud/supply-chain guidance, not a standalone statutory obligation. Apply only to the relevant supplier service and responsibility boundary; cited older standards are not asserted to be current.",
    "checked_on": "2026-11-13",
    "claim_to_check": "Can a community SaaS label alone establish the isolation controls of an MCP service built on public infrastructure?",
    "documented_statement": {
      "status": "documented",
      "statement": "NCSC Principle 8 distinguishes application-level separation in a layered service from underlying public-IaaS hypervisor controls. It recommends identifying which party implements each security function and understanding the underlying stack for sensitive uses.",
      "source_ids": [
        "ncsc-supply"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A community SaaS label alone does not establish the complete isolation boundary or transfer assurance from an underlying provider. No tenant-isolation testing occurred.",
      "source_ids": [
        "ncsc-supply"
      ]
    },
    "buyer_evidence_required": [
      "Service stack and tenancy model",
      "Separation control and responsible party by layer",
      "Scope of assurance evidence for each relevant layer"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "No tenant-isolation test, data-residency conclusion or inherited certification is supplied."
    },
    "unknowns": "Documentation and buyer-supplied evidence requirements only. No supplier has been inspected; effectiveness, legal compliance and actual outcomes remain unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No enterprise, supplier or provider deployment has been tested. Applicability and implementation remain buyer-specific."
    },
    "evidence_sources": [
      {
        "source_id": "ncsc-supply",
        "url": "https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-8-supply-chain-security",
        "title": "NCSC Cloud Security Principle 8",
        "publisher": "National Cyber Security Centre",
        "publication_date": "2018-11-17",
        "reviewed_date": "2023-06-07",
        "version": "2.1",
        "captured_at": "2026-11-13T21:10:00.981609+00:00",
        "status": 200,
        "sha256": "7ea5c853e2d80a1c43dbf07b4eb50e095c721f3d002f2092ddcc5ae4c40a5a1a",
        "text_sha256": "8278516b4fe51966bb388229d392bddb54c10fe6a53061450355b8fd8ca0c74b",
        "bytes": 241041,
        "capture_status": "captured_primary_source",
        "hash_basis": "Original HTTP response bytes and separately hashed extracted text retained privately; hashes do not establish legal authority, factual truth or runtime behaviour.",
        "rights_disposition": "Concise original analysis with attribution; captures remain private. Crown material is attributed under OGL v3.0, subject to third-party exclusions and no endorsement. NIST source is a US government publication.",
        "licence_url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/"
      }
    ],
    "supporting_passages": [
      {
        "source_id": "ncsc-supply",
        "anchor": "These layered services may result",
        "end_anchor": "Additional considerations",
        "start_character": 5578,
        "end_character": 6591,
        "offset_unit": "Unicode code points in separately hashed UTF-8 text",
        "passage_sha256": "667d65af3e7c126f44fac6cf1b63ad1cdc9dfbb30895cf4732b418eaab9d6b80",
        "full_source_sha256": "7ea5c853e2d80a1c43dbf07b4eb50e095c721f3d002f2092ddcc5ae4c40a5a1a",
        "text_sha256": "8278516b4fe51966bb388229d392bddb54c10fe6a53061450355b8fd8ca0c74b"
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Free source evidence only. No supplier approval, legal advice, compliance certification, live verification or paid checker fit is established.",
    "paid_value": {
      "free": "Full documentary evidence, provenance and limitations.",
      "single_request": "Unavailable for this catalogue-only addition; existing eligible saving unchanged.",
      "evidence_receipt": "Unavailable for this catalogue-only addition.",
      "existing_licensed_products": "Unchanged; separately supported declaration inputs only, no supplier or regulatory determination.",
      "excluded": [
        "Legal compliance determination",
        "Supplier certification",
        "Runtime enforcement",
        "Verified deletion",
        "Expanded entitlement"
      ]
    },
    "revalidation": {
      "trigger": "Relevant primary source, legal effective date, contract or supplier service changes; no ongoing monitoring included.",
      "specific_watch": "Recheck the exact source version, applicable jurisdiction and effective date, supplier service/contract scope and missing evidence before reliance."
    },
    "buyer_relevance": "Identify missing layer-specific separation evidence before selecting a supplier for sensitive data.",
    "refusal_conditions": [
      "No tenant-isolation test, data-residency conclusion or inherited certification is supplied.",
      "Missing, stale, superseded, wrong-jurisdiction or conflicting evidence prevents reliance on the intended determination.",
      "Documentation and signed supplier declarations do not establish independent runtime enforcement or observed outcomes."
    ],
    "decision_context": {
      "operator": "Enterprise procurement, security or platform owner; involve the responsible privacy/legal specialist for legal scope",
      "scenario": "Can a community SaaS label alone establish the isolation controls of an MCP service built on public infrastructure?",
      "consequence": "Identify missing layer-specific separation evidence before selecting a supplier for sensitive data.",
      "workflow": "architecture admission",
      "confidence": "Source-qualified documentary decision only; independent buyer value and paid demand remain unestablished."
    },
    "novelty_review": {
      "candidate_id": "SUP-019",
      "disposition": "new_distinct",
      "nearest_record_id": "VXI-EXT-PROCUREMENT-POSTGRES-RLS-PRIVILEGES-01-v1",
      "nearest_record_url": "/varexis-index/records/postgres-rls-role-exception-evidence.json",
      "nearest_record_sha256": "a7bdd41c3de0d4489407b75c50639b40baa86e3070656b3604c6cc54d6223855",
      "material_distinction": "Layer-specific SaaS/IaaS separation responsibilities are distinct from Postgres RLS, Qdrant capacity and MCP sandbox exceptions.",
      "review_status": "Independent reviewer challenge completed; reviewer receipt is not customer evaluation or supplier attestation.",
      "counterexample": "Layered services can have appropriate separation; different controls at different layers do not by themselves establish an isolation failure."
    },
    "optional_selection": {
      "guide_id": "agent-authority-tool-trust",
      "guide_url": "/index-guides/agent-authority-tool-trust",
      "guide_manifest": "/varexis-index/decision-guides.json",
      "placement": "Contextual technical follow-on only; this supplier/legal decision is not assessed by the guide or checker. Existing guide records and trial paths remain unchanged.",
      "checker": null,
      "boundary": "Contextual follow-on for supported operation/identity declarations; not a tenancy isolation assessor."
    },
    "exact_access": {
      "endpoint": "/mcp/catalogue",
      "tool": "get_publication_record",
      "arguments": {
        "record_id": "VXI-EXT-SUP78-NCSC-LAYERED-SEPARATION-RESPONSIBILITY-01-v1"
      },
      "record_url": "/varexis-index/records/ncsc-layered-separation-responsibility.json",
      "original_mcp_search": false,
      "paid_saved_retrieval": false
    }
  },
  "niche": {
    "niche_id": "sup78-governance",
    "label": "Agent Governance & Policy Boundaries",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Identify missing layer-specific separation evidence before selecting a supplier for sensitive data.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "Complete free source evidence via exact HTTP and /mcp/catalogue. Paid saving and licensed checker fit are not available for this record; existing eligible offers are unchanged.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "public_discovery",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": false,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "PUBLIC_DISCOVERY_LIVE",
    "checkout_url": null
  },
  "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#ncsc-layered-separation-responsibility",
  "machine_readable_record": "/varexis-index/records/ncsc-layered-separation-responsibility.json"
}
