Vendor Register

Cybersecurity risk: the assessment template

Incident notification, vulnerability handling, secure development, advisories, provenance and privileged access. 8 questions; each names the clause it comes from or says "general practice, not a held regulation". The assessor rates the domain, inherent and residual, with a rationale; Vendor Register never sets a rating.

  1. cyb-01 How will you notify us of a compromise, a vulnerability or a relevant change affecting our service or data, and within what timeframe? vendor answers
    NIST SP 800-161 Rev 1 SR-8, Notification Agreements

    Establishes agreements requiring suppliers to notify the organization of compromise, vulnerability and relevant change.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance). Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The notification clause and the timeframe.
  2. cyb-02 Does the contract commit the vendor to assist us on an ICT incident affecting the service, at no cost or a cost fixed in advance? internal
    DORA Art. 30, Key contractual provisions

    Contracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protection provisions; access, recovery and return of data on insolvency, resolution, discontinuation or termination; service level descriptions; incident assistance at no cost or a cost fixed in advance; cooperation with competent and resolution authorities; termination rights and minimum notice periods; and participation in security awareness training. Contracts for services supporting critical or important functions add: full service levels with quantitative and qualitative targets, notice and reporting duties, provider contingency testing and security measures, participation in the entity's TLPT, unrestricted access, inspection and audit rights for the entity and the authority, and exit strategies with a mandatory transition period (Art. 30(3)). A microenterprise may agree with the provider that its access, inspection and audit rights are handed to an independent party that the provider appoints, from which it can request information and assurance at any time (Art. 30(3), final subparagraph). Standard contractual clauses from public authorities should be considered.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are a DORA financial entity. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The contract clause, by section number.
  3. cyb-03 Describe your secure development practice and how you handle vulnerabilities in the product we use (intake, triage, fix times by severity). vendor answers
    NIS2 Art. 21(3), Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

    Deciding what supply chain measures are appropriate is not left to general judgement. The entity has to take into account the vulnerabilities specific to each direct supplier and service provider, and the overall quality of those parties' products and cybersecurity practices including their secure development procedures. Separately, it must take into account the results of the Union level coordinated security risk assessments of critical supply chains carried out under Article 22(1). That second limb creates an external input the entity has to watch for and respond to: when a coordinated assessment lands on a technology the entity uses, the outcome has to reach the supplier risk decisions rather than stop at a policy team. Evidence of consideration is what is being asked for, including reasoned decisions not to change anything.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are a NIS2 essential or important entity. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The secure development policy and the vulnerability handling procedure.
  4. cyb-04 Has the outcome of any Union coordinated security risk assessment of a critical supply chain that covers this vendor's technology been taken into account? internal
    NIS2 Art. 21(3), Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

    Deciding what supply chain measures are appropriate is not left to general judgement. The entity has to take into account the vulnerabilities specific to each direct supplier and service provider, and the overall quality of those parties' products and cybersecurity practices including their secure development procedures. Separately, it must take into account the results of the Union level coordinated security risk assessments of critical supply chains carried out under Article 22(1). That second limb creates an external input the entity has to watch for and respond to: when a coordinated assessment lands on a technology the entity uses, the outcome has to reach the supplier risk decisions rather than stop at a policy team. Evidence of consideration is what is being asked for, including reasoned decisions not to change anything.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Named only: NIS2 Article 22, Union coordinated security risk assessments of critical supply chains (reached through Article 21(3))
    Applies when you are a NIS2 essential or important entity. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The record of the consideration, including a reasoned decision to change nothing.
  5. cyb-05 Do we receive and act on security advisories for the components and services this vendor supplies? internal
    NIST SP 800-161 Rev 1 SI-5, Security Alerts, Advisories, and Directives

    Receives and acts on advisories concerning acquired components and the suppliers behind them.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance). Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The advisory sources and the last advisory actioned.
  6. cyb-06 For hardware or software components: can you show provenance (origin and change history) and authenticity (anti-counterfeit measures) for what you deliver? vendor answers
    NIST SP 800-161 Rev 1 SR-4, Provenance

    Establishes and maintains provenance for systems, components and associated data so origin and change history are known.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    NIST SP 800-161 Rev 1 SR-11, Component Authenticity

    Establishes an anti-counterfeit policy and the means to detect and report counterfeit components.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance), and the vendor is hardware or components. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The provenance record and the anti-counterfeit policy.
  7. cyb-07 Is this a managed service or managed security service provider with privileged access into our estate, and is that access session-controlled and reviewed? internal
    NIS2 Art. 21(2)(d), Supply chain security, covering the relationship with each direct supplier and service provider

    The Directive scopes this deliberately at direct suppliers and service providers, which makes the first artefact an inventory of who those parties are and which of them touch the network and information systems behind the service. From there the entity has to manage the security-related aspects of each relationship: what the supplier may access, what security obligations bind it, what happens on incident, and what happens at exit. Contract terms are the enforcement mechanism, so contracts that predate NIS2 and carry no security clauses are a live gap rather than a legacy inconvenience. Managed service providers and managed security service providers deserve separate attention because they hold privileged access into the estate, which makes their compromise the entity's incident.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are a NIS2 essential or important entity, and the vendor is a managed or managed security service. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The privileged access list and the last access review.
  8. cyb-08 Do you require multi-factor authentication for all access to systems that hold our data, including your administrators' remote access? vendor answers
    general practice, not a held regulation
    Evidence that helps: The access control policy.

Use it as it is, reword a question (it then becomes your own and cites nothing), add your own, or save your own template, on Solo and Team. Pricing.