VAREXIS-INDEX ยท Free evidence

Enterprise agent and MCP supplier evidence

23 bounded source reviews for supplier admission, contractual evidence, operational change and exit. UK applicability and voluntary guidance remain explicit. No supplier approval, legal advice, runtime verification or new paid product.

Free exact HTTP and /mcp/catalogue retrieval. Original /mcp search and preview, paid saved retrieval and enhanced natural-language qualification are not extended. Documentary evidence and review inference do not establish supplier approval, legal compliance or runtime enforcement.

Complete exact-ID manifest · Full catalogue · Existing MCP coverage

AI-assisted bids need proportionate verification

Should a supplier be excluded merely because AI helped write its bid?

PPN 017 says supplier AI use in the commercial process is not prohibited. It describes optional disclosure questions and proportionate due diligence into tender accuracy, capacity and capability. Review implication: AI-use disclosure alone cannot establish delivery capability or automatic exclusion authority. Request evidence against specific tender uncertainties.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK central government departments, executive agencies and non-departmental public bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • Do not infer capability or an exclusion ground from AI disclosure alone.
  • A well-evidenced AI-assisted bid can remain eligible; disclosure is neither automatic disqualification nor proof of competence.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

Tender access does not establish permission to train

Does sharing confidential tender material with a bidder establish permission to use it for model training?

PPN 017 describes proportionate controls to prevent confidential authority information or other non-public information being used as AI training data by suppliers. Review implication: Access to tender material alone does not establish training permission or actual compliance with the agreed handling restriction.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK central government departments, executive agencies and non-departmental public bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • Do not claim that every AI input trains a model or that a supplier actually complied with a restriction.
  • An applicable express training permission and handling agreement could support that narrower authority; receipt of a document alone cannot.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

Cyber controls depend on the contract risk

Must every public-sector MCP supplier hold Cyber Essentials regardless of the contract?

PPN 014 requires relevant, proportionate cyber controls and rejects a blanket approach. Where relevant, suppliers without Cyber Essentials or Cyber Essentials Plus must demonstrate equivalent controls. G-Cloud inclusion does not remove the buyer call-off cyber-risk review. Review implication: Record the contract-specific risk decision and supporting evidence. A missing badge alone is not a universal exclusion rule, and framework presence is not complete award assurance.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK central government departments, executive agencies and non-departmental public bodies and NHS bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • Do not assert all public or private contracts require certification or treat an unsupported equivalence claim as evidence.
  • A relevant higher-risk contract may properly require certification or equivalent controls; proportionality does not mean controls are optional everywhere.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

Certificate evidence has a handoff and renewal boundary

Can award-time certification alone support a later transfer of data to a supplier?

PPN 014 requires certificate or equivalent evidence at the point data is passed to the supplier. Where Cyber Essentials certification is required, annual renewal applies for the contract duration. Review implication: An award-time certificate alone does not establish the state at a later handoff. Equivalent-control evidence has its own review basis; it is not necessarily a certificate with an annual expiry.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK central government departments, executive agencies and non-departmental public bodies and NHS bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • No VAREXIS certificate validation, automatic expiry determination or supplier approval is performed.
  • Current applicable evidence at handoff can satisfy the narrower timing question; absence of a new certificate is not proof equivalent controls ceased.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A Cyber Essentials badge is not service assurance

Does a supplier Cyber Essentials certificate assure the particular MCP service being purchased?

PPN 014 says Cyber Essentials does not assure specific supplied products or services. Risks exceeding the scheme parameters may require additional proportionate measures and specialist input. Review implication: A general supplier certificate cannot substitute for the service-specific scope and threat evidence required by this buyer.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK central government departments, executive agencies and non-departmental public bodies and NHS bodies. Other public-sector bodies may choose to adopt the approach. Relevant new procurements from 24 February 2025; earlier procurements/frameworks need the applicable transition route. Not a blanket private-enterprise duty.
  • Do not infer current certification validity, product security or penetration-test results from this source.
  • Specific service assurance may be separately available; the limitation concerns what the general Cyber Essentials certificate establishes.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A privacy notice is not the complete processor contract

What processing details must be bound before relying on a UK processor agreement?

UK Article 28(3) requires a binding contract or other domestic-law act specifying processing subject, duration, nature, purpose, data types, data-subject categories and controller obligations and rights. Paragraph 9 requires writing, including electronic form. Review implication: A generic privacy notice alone does not establish the buyer-specific processing terms, binding relationship or applicable scope.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • A document title or signed template does not establish enforceability, applicability or whole-regime compliance.
  • An incorporated written agreement may contain the required particulars; a generic notice is not necessarily the only binding document.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

General authorisation still needs change notice

Can an agent supplier add a subprocessor under general authorisation without a change-notice opportunity?

UK Article 28(2) requires prior specific or general written controller authorisation for another processor. Under general authorisation, intended additions or replacements must be notified to give the controller an opportunity to object. Review implication: A public subprocessor list alone does not establish the applicable buyer authorisation, delivery of notice or opportunity to object.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No universal notice period, automatic veto outcome or actual runtime processor use is inferred.
  • Specific prior written authorisation may cover a named subprocessor; the general-authorisation change-notice rule must not be applied as an invented universal notice interval.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

Outsourcing does not erase the first processor obligation

Does a supplier shift its Article 28 responsibilities to the buyer simply by using a subprocessor?

UK Article 28(4) requires the same data-protection obligations to bind the further processor through a contract or other legal act. The initial processor remains fully liable to the controller for performance of those obligations if the further processor fails. Review implication: A list of subcontractors does not establish the obligation chain. Case-specific liability, damages and transfer legality need separate competent assessment.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • Do not decide case-specific legal liability, damages or third-country transfer legality.
  • A properly bound downstream arrangement can provide the obligation chain; this record does not decide whether a particular loss attracts damages.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

The controller choice and storage exception must be explicit

Which controller exit choice and claimed domestic-law storage exception must be evidenced under UK Article 28(3)(g)?

UK Article 28(3)(g) sets out the controller choice of return or deletion at the end of processing services, together with deletion of existing copies unless domestic law requires storage. Review implication: Identify the controller exit choice and evidence supporting any asserted legal storage exception. This duty is separate from evidence that return or deletion actually occurred.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No verified deletion, legal exception determination or memory-custody enforcement is supplied.
  • A supported domestic-law storage requirement can affect the exit handling; this does not prove all copies must or may be retained indefinitely.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A certification summary does not settle audit access

Can a processor certificate alone establish the controller has the required Article 28 audit information and access?

UK Article 28(3)(h) requires necessary compliance information and contribution to audits including inspections by the controller or its mandated auditor. Paragraph 5 permits approved Article 40 codes or Article 42 certification as a means of demonstrating sufficient guarantees. Review implication: Even an approved scheme does not by itself establish the contractual information/audit arrangements or their exercise. An arbitrary certificate is not automatically an approved Article 42 mechanism.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No unlimited public audit entitlement, audit success, certificate approval or compliance conclusion is inferred.
  • An approved scoped scheme may contribute evidence of guarantees; it is neither worthless nor a replacement for all information and audit arrangements.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A processor label does not decide every processing role

If an agent supplier determines processing purposes and means outside its processor role, is the contract label conclusive?

UK Article 28(10) treats a processor that infringes the Regulation by determining purposes and means as a controller in respect of that processing. Review implication: A contract label is not conclusive for every activity. Escalate an independent reuse purpose for a processing-specific assessment; ordinary implementation choices alone do not settle controller status.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • Do not classify an organisation globally or infer that every implementation choice makes it a controller.
  • A processor may choose technical implementation details without this alone establishing an independent purpose or controller role.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

Supplier criticality depends on the intended use

Can supplier brand or spend alone determine the assurance tier for an enterprise MCP service?

NIST SP 1305 recommends supplier-criticality criteria based on business importance, data sensitivity and system access, followed by prioritised supplier records. Review implication: Brand or spend alone does not describe this intended-use consequence. The buyer must supply its criticality criteria; this record supplies no risk score or mandatory tier.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • Voluntary NIST CSF 2.0/SP 1305 guidance, final October 2024. No automatic UK/EU legal obligation or supplier certification.
  • No quantitative risk score, supplier certification or mandatory NIST threshold is supplied.
  • A small supplier may be critical for a sensitive workflow, while a large supplier may be low criticality for a limited use.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A supplier contact is not a responsibility allocation

Who owns supplier-security decisions across the buyer, agent operator and infrastructure provider?

NIST SP 1305 recommends named accountable roles, responsibility matrices, shared-responsibility obligations in policies and applicable agreements, and information-sharing protocols. Review implication: A support contact is not the complete allocation of supplier-security decisions. Include buyer, operator, MSP and underlying-provider roles where relevant; a matrix remains a declaration.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • Voluntary NIST CSF 2.0/SP 1305 guidance, final October 2024. No automatic UK/EU legal obligation or supplier certification.
  • A matrix is declared responsibility, not proof it was exercised or a grant of authority.
  • A named support contact can be one useful role within a complete matrix; its existence alone does not assign every decision.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

An uptime SLA is not the complete security performance agreement

Does a service uptime percentage alone define acceptable supplier security performance?

NIST SP 1305 recommends security requirements in service-level agreements to monitor acceptable supplier security performance throughout the relationship. Review implication: An uptime metric alone does not specify the relevant security requirements, reporting and verification method. Review unresolved findings and owners before renewal.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • Voluntary NIST CSF 2.0/SP 1305 guidance, final October 2024. No automatic UK/EU legal obligation or supplier certification.
  • No universal SLA threshold or actual supplier performance is established.
  • An existing SLA may include appropriate security measures beyond uptime; its label alone does not show their content or performance.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A patch process needs scope and timing evidence

Does a supplier vulnerability-process statement establish timely mitigation across its service dependencies?

NCSC Principle 5.1 recommends checking mitigation timescales and provider responsibility across service components and dependencies. It notes that the process standards it cites do not themselves specify acceptable mitigation timescales. Review implication: A process label does not establish timely mitigation of the relevant deployment. Review scoped commitments, prior performance and current mitigation evidence separately.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • 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 vulnerability scan, exploit test, current patch verification or mandatory deadline is provided.
  • A scoped provider commitment with dated mitigation evidence may support a narrower review; a process certificate alone is insufficient.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

Collected logs are not demonstrated protective monitoring

Who analyses provider-side events and owns escalation and response beyond making audit logs available?

NCSC Principle 5.2 separates generating and collecting events from analysing them and taking appropriate action. It cautions that collection without effective analysis does not establish prompt detection and response. Review implication: Identify who analyses provider-side events and owns escalation/action. Event export or retention alone does not establish operational detection.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • 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 attack-detection rate, complete log coverage or effective security control is verified.
  • A provider may collect, analyse and respond effectively; an export feature alone neither establishes nor disproves that.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A public status page is not a buyer incident-notification agreement

What notification evidence is needed for incidents affecting the buyer data or shared service?

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.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • 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.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A release note is not the complete change-control evidence

What supplier notice and buyer-impact evidence are needed before a service-use-affecting change?

NCSC Principle 5.4 recommends tracking assets and dependencies, assessing security impact, following changes to completion and giving appropriate notice before changes that affect use of the service. Review implication: Before continued reliance, identify the changed buyer dependency, relevant impact and notice. A release announcement alone does not establish that this buyer received appropriate advance notice.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • 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 runtime change enforcement, cryptographic attestation or universal notice interval is claimed.
  • A supplier may provide appropriate notice and scoped impact evidence; a public release note may be part of that evidence but is not automatically complete.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

Application tenancy does not describe the whole underlying separation boundary

Can a community SaaS label alone establish the isolation controls of an MCP service built on public infrastructure?

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.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • 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.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

Confidentiality needs a people-access boundary

What evidence covers persons authorised to process personal data for a UK processor?

UK Article 28(3)(b) requires the processor contract to ensure persons authorised to process personal data have committed to confidentiality or are subject to an appropriate statutory confidentiality obligation. Review implication: A service privacy page alone does not establish the commitment or statutory obligation for each relevant personnel category. This is not staff vetting or an effective-access test.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No staff vetting, actual compliance or access-control enforcement is verified.
  • An appropriate statutory confidentiality obligation may be relevant without a separate individual promise; its applicability must be evidenced.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A processor export button is not the entire assistance arrangement

What should the buyer establish about processor assistance with data-subject requests?

UK Article 28(3)(e) requires appropriate technical and organisational assistance, insofar as possible and taking account of processing nature, for the controller response to data-subject rights requests. Review implication: A generic export feature does not establish the applicable assistance process, scope or limitations. Identify the contractual and operational assistance evidence separately.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No legal deadline assessment, complete subject discovery or automatic rights fulfilment is provided.
  • A supplier process may provide suitable assistance within the processing context; a missing feature does not by itself decide the entire legal duty.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

A technical token is not the documented processing instruction

Does possession of an API credential establish the controller instruction for a personal-data transfer?

UK Article 28(3)(a) addresses documented controller instructions, including transfers, with a domestic-law exception and a duty to inform beforehand unless the stated public-interest prohibition applies. Review implication: An API credential establishes neither that documented instruction nor a lawful transfer basis. Consent, destination authority and actual execution remain separate unverified questions.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • UK GDPR processing by a processor on behalf of a controller; confirm entity, personal-data processing and current legal applicability. Revised Article 28 captured 13 November 2026; not an EU GDPR or whole-regime compliance determination.
  • No consent, destination authority, legal transfer basis or effective permission is verified.
  • A valid documented instruction may accompany a technical token; neither token possession nor this record establishes the other legal requirements.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice

An initial SBOM does not settle inventory maintenance

What should be agreed about continuing component information for a critical supplier product?

NIST SP 1305 recommends contractual requirements to maintain a current component inventory for critical products and disclose security features, functions and vulnerabilities through product life or the service term. Review implication: An initial SBOM does not establish a continuing inventory-maintenance or disclosure commitment. Retain dated contract, inventory and change evidence; completeness remains unverified.

Documentation reviewed 2026-11-13. Primary source.

Boundaries
  • Voluntary NIST CSF 2.0/SP 1305 guidance, final October 2024. No automatic UK/EU legal obligation or supplier certification.
  • No inventory completeness, present deployment match or authenticity is inferred.
  • A maintained inventory can exist and be useful; its contractual maintenance commitment does not itself establish every deployed component was captured.
  • No supplier approval, legal advice, certification, runtime verification or new paid capability.

Complete record JSON · Exact free preview JSON · Source review

Required source attribution and distribution notice