{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-11-13T21:26:59.827748+00:00",
  "record_id": "VXI-EXT-SUP78-NCSC-INCIDENT-NOTIFICATION-AGREEMENT-01-v1",
  "record_kind": "external_reference",
  "title": "A public status page is not a buyer incident-notification agreement",
  "system": "National Cyber Security Centre",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "What notification evidence is needed for incidents affecting the buyer data or shared service?",
  "near_questions": [
    "What establishes buyer-specific incident notification arrangements?",
    "Does a public status page establish the agreed incident recipient?",
    "Which notification method and timescale should be evidenced?",
    "Does NCSC incident guidance itself set a statutory reporting clock?"
  ],
  "supported_claims": [
    {
      "claim": "NCSC Principle 5.3 recommends defined reporting routes, pre-planned response and agreed notification methods and timescales for incidents affecting customer data. These arrangements are additional to customer monitoring responsibilities.",
      "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.",
    "Do not infer a statutory notification deadline, actual incident handling or breach-free operation.",
    "A current agreement may establish notification arrangements; this does not itself prove an incident notification was delivered.",
    "No supplier approval, legal advice, certification, runtime verification or new paid capability."
  ],
  "public_summary": "NCSC Principle 5.3 recommends defined reporting routes, pre-planned response and agreed notification methods and timescales for incidents affecting customer data. These arrangements are additional to customer monitoring responsibilities. Review implication: A public status page alone does not establish a buyer-specific notification trigger, recipient or agreed timing. Include relevant supplier participation without inferring a statutory deadline.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "NCSC Cloud Security Principle 5",
    "source_url": "https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-5-operational-security",
    "checked_on": "2026-11-13",
    "candidate_record_id": "VXI-EXT-SUP78-NCSC-INCIDENT-NOTIFICATION-AGREEMENT-01-v1",
    "candidate_record_sha256": "54571a0bd5bb230d248b00a0708d0e64542dc84bb40dcb8831c397e34b9d61aa",
    "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 5.3 recommends defined reporting routes, pre-planned response and agreed notification methods and timescales for incidents affecting customer data. These arrangements are additional to customer monitoring responsibilities. Review implication: A public status page alone does not establish a buyer-specific notification trigger, recipient or agreed timing. Include relevant supplier participation without inferring a statutory deadline.",
    "required_buyer_context": "Service/data scope and notification trigger; Agreed reporting method, recipient and timescale; Supplier contact route and response responsibilities",
    "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": "What notification evidence is needed for incidents affecting the buyer data or shared service?",
    "documented_statement": {
      "status": "documented",
      "statement": "NCSC Principle 5.3 recommends defined reporting routes, pre-planned response and agreed notification methods and timescales for incidents affecting customer data. These arrangements are additional to customer monitoring responsibilities.",
      "source_ids": [
        "ncsc-operations"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A public status page alone does not establish a buyer-specific notification trigger, recipient or agreed timing. Include relevant supplier participation without inferring a statutory deadline.",
      "source_ids": [
        "ncsc-operations"
      ]
    },
    "buyer_evidence_required": [
      "Service/data scope and notification trigger",
      "Agreed reporting method, recipient and timescale",
      "Supplier contact route and response responsibilities"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer a statutory notification deadline, actual incident handling or breach-free operation."
    },
    "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-operations",
        "url": "https://www.ncsc.gov.uk/collection/cloud/the-cloud-security-principles/principle-5-operational-security",
        "title": "NCSC Cloud Security Principle 5",
        "publisher": "National Cyber Security Centre",
        "publication_date": "2018-11-17",
        "reviewed_date": "2023-06-07",
        "version": "2.1",
        "captured_at": "2026-11-13T21:10:01.042849+00:00",
        "status": 200,
        "sha256": "57dc6320745d99d751949ade4e6e9d0849c13418064fe4b16979a357aa76757f",
        "text_sha256": "335c8e3adc78f836f568dcfb06747ac90bd5ef68b3d26f46c30e6ebaa79fc4f1",
        "bytes": 258025,
        "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-operations",
        "anchor": "5.3 Incident management",
        "end_anchor": "5.4 Configuration and change management",
        "start_character": 13225,
        "end_character": 16426,
        "offset_unit": "Unicode code points in separately hashed UTF-8 text",
        "passage_sha256": "df5ead4b405ebdf670b0b7a5c46308ae24b51a2e32a976bfabe95bb6d9504399",
        "full_source_sha256": "57dc6320745d99d751949ade4e6e9d0849c13418064fe4b16979a357aa76757f",
        "text_sha256": "335c8e3adc78f836f568dcfb06747ac90bd5ef68b3d26f46c30e6ebaa79fc4f1"
      }
    ],
    "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": "Agree an actionable recipient, trigger and reporting channel before incident-driven reliance or renewal.",
    "refusal_conditions": [
      "Do not infer a statutory notification deadline, actual incident handling or breach-free operation.",
      "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": "What notification evidence is needed for incidents affecting the buyer data or shared service?",
      "consequence": "Agree an actionable recipient, trigger and reporting channel before incident-driven reliance or renewal.",
      "workflow": "incident readiness",
      "confidence": "Source-qualified documentary decision only; independent buyer value and paid demand remain unestablished."
    },
    "novelty_review": {
      "candidate_id": "SUP-017",
      "disposition": "new_distinct",
      "nearest_record_id": "VXI-EXT-TOOL-TRUST-PAGERDUTY-01-v1",
      "nearest_record_url": "/varexis-index/records/pagerduty-hosted-mcp-incident-authority-trust.json",
      "nearest_record_sha256": "7ce85f75efc9907ad5c3d423556d363cfaf62ccbffe62c5322bbe39a66365eef",
      "material_distinction": "Buyer-specific incident trigger, recipient, method and agreed timing differ from incident-tool permissions and event delivery records.",
      "review_status": "Independent reviewer challenge completed; reviewer receipt is not customer evaluation or supplier attestation.",
      "counterexample": "A current agreement may establish notification arrangements; this does not itself prove an incident notification was delivered."
    },
    "optional_selection": {
      "guide_id": null,
      "guide_url": null,
      "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": "No existing guide evaluates this procurement, legal or generic supplier-assurance determination. Preserve null rather than imply unsupported coverage."
    },
    "exact_access": {
      "endpoint": "/mcp/catalogue",
      "tool": "get_publication_record",
      "arguments": {
        "record_id": "VXI-EXT-SUP78-NCSC-INCIDENT-NOTIFICATION-AGREEMENT-01-v1"
      },
      "record_url": "/varexis-index/records/ncsc-incident-notification-agreement.json",
      "original_mcp_search": false,
      "paid_saved_retrieval": false
    }
  },
  "niche": {
    "niche_id": "sup78-audit",
    "label": "Audit, Provenance & Evidence Accountability",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Agree an actionable recipient, trigger and reporting channel before incident-driven reliance or renewal.",
    "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-incident-notification-agreement",
  "machine_readable_record": "/varexis-index/records/ncsc-incident-notification-agreement.json"
}
