Domain · Client requirements & tenders

Cyber commitments you can keep, and prove.

Security questionnaires, the cyber sections of tenders, contract clauses: we prepare accurate answers, backed by your evidence, and track the commitments made until they fall due.

Situations

You are in the right place if…

  • A key account sends you a security questionnaire of several hundred questions, due in two weeks.
  • A tender asks for a security assurance plan and you do not have one.
  • A financial client sends you a « DORA » amendment and you do not know what you are signing.
  • Your sales team answers « yes » to requirements nobody checks afterwards.
  • You answer the same questionnaire every year, starting from scratch.
Our conviction

Commercial trust rests on commitments you can demonstrate.

A questionnaire filled in a hurry creates two risks: losing the deal with an over-cautious answer, or committing to a measure you do not apply. The second comes to light at the client’s audit, or after an incident.

So we answer from what exists and can be proven. Each answer points to evidence; each new commitment enters a tracked plan, with an owner and a due date.

Our approach

From the client’s question to the commitment kept.

The same base of answers serves all your clients; it grows with each questionnaire.

  1. 01Qualify the requestWhich framework the client applies, which requirements are eliminatory, which can be negotiated.

    You getA grid of requirements, ranked by stake

  2. 02Answer on evidenceEach answer rests on an existing policy, configuration, report or certificate.

    You getSubstantiated answers, with their attachments

  3. 03Negotiate the clausesNotification deadlines, audit rights, location, reversibility: what you can accept, and on what terms.

    You getA reasoned position, clause by clause

  4. 04Keep the commitmentsAccepted gaps become dated actions; evidence is kept up to date for the next review.

    You getA register of commitments and evidence

What the texts say

Why your clients ask.

Your clients do not ask out of curiosity: their own texts require them to oversee their providers, and they pass the requirements on to you.

  • DORADORA art. 30(2) · DORA art. 30(2), point (c) · DORA art. 30(2), point (f)

    Financial entities must include in their ICT services contracts, among other things, provisions on data protection and on the provider’s assistance when an incident related to the service occurs.123

  • NIS 2 · ReCyFNIS 2 art. 21(2), point (d) · NIS 2 art. 21(3) · ReCyF v2.5, objectif 3

    The directive asks Member States to ensure that entities take into account the quality of products and the cybersecurity practices of their suppliers; the ReCyF (working version) sets them the objective of ensuring, notably by contract, that the IT services they receive comply with their own obligations.456

  • GDPRRGPD art. 28(3), point (c) · RGPD art. 28(3), point (h)

    The processing contract stipulates that the processor takes the security measures of Article 32 and makes available the information needed to demonstrate compliance, including during audits.78

  • CNIL guideGuide CNIL sécurité, fiche 14, F14-PE-02 · Guide CNIL sécurité, fiche 14, F14-PE-03

    The CNIL recommends that controllers set their processors’ security obligations by contract and provide the means to verify that they are effective.910

Our engagement

The same topic, at three levels of engagement.

You choose the level; the scope and deliverables are set by contract.

Level 01

Monitor

We keep your base of answers up to date and flag outdated evidence and commitments falling due.

Deliverables
  • Library of standard answers, linked to their evidence
  • Register of commitments made, client by client
  • Alerts on evidence and certificates to renew
Level 03

Drive

We run the follow-up of commitments with your teams, without making the changes in your systems.

Deliverables
  • Management of the actions arising from commitments
  • Preparation of client audits
  • Evidence file ready to share
Accelerators

What we bring from day one.

Mappings between frameworks

One measure answers questions phrased after ISO 27001, DORA, NIS 2 or the CNIL guide: we describe it once.

Pre-filling assistant

An AI assistant drafts answers from your documents; an expert reviews and approves each answer before it is sent.

Assurance plan and annex templates

Security assurance plan, security annex, notification clauses: templates to adapt, already tested against clients’ requirements.

Frequently asked questions

Before we start.

Do you sign the answers on our behalf?

No. We prepare the answers and the evidence; you approve and send them. The commitment remains yours, and we only have you promise what you apply or have planned.

Can a financial client impose DORA clauses on us?

The regulation requires the financial entity to include certain provisions in its ICT services contracts; it therefore passes them on to you. We help you tell what the text requires from what the client adds, which can be negotiated.1

We are a processor under the GDPR: can a client audit us?

The processing contract must provide that you contribute to audits conducted by the controller or by an auditor it mandates. Better to agree the terms in advance: notice, scope, frequency, confidentiality.8

What about a requirement we do not meet?

Write it down. A « no, planned for such a date » answer with a plan is often better received than a fragile « yes ». We size the gap and propose the wording and the date.

Send us the next questionnaire.

Describe the request and its deadline. We come back to you with a first reading of the requirements and a proposed scope.

Sources

The excerpts quoted.

Exact text, in its original language, from the frameworks extracted from the official text.

Show the 10 excerpts quoted
  1. 1DORA art. 30(2)32022R2554-a30-p2
    The contractual arrangements on the use of ICT services shall include at least the following elements:
    Normative force
    directly applicable EU law (regulation, level 1)
    Source
    Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector
    Version
    CELEX 32022R2554 — ELI reg/2022/2554
    Official text
  2. 2DORA art. 30(2), point (c)32022R2554-a30-p2-3
    provisions on availability, authenticity, integrity and confidentiality in relation to the protection of data, including personal data;
    Normative force
    directly applicable EU law (regulation, level 1)
    Source
    Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector
    Version
    CELEX 32022R2554 — ELI reg/2022/2554
    Official text
  3. 3DORA art. 30(2), point (f)32022R2554-a30-p2-6
    the obligation of the ICT third-party service provider to provide assistance to the financial entity at no additional cost, or at a cost that is determined ex-ante , when an ICT incident that is related to the ICT service provided to the financial entity occurs;
    Normative force
    directly applicable EU law (regulation, level 1)
    Source
    Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector
    Version
    CELEX 32022R2554 — ELI reg/2022/2554
    Official text
  4. 4NIS 2 art. 21(2), point (d)32022L2555-a21-p2-4
    supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers;
    Normative force
    EU law to be transposed (directive): not directly applicable, requires national transposition
    Source
    Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive)
    Version
    CELEX 32022L2555 — ELI dir/2022/2555
    Official text
  5. 5NIS 2 art. 21(3)32022L2555-a21-p3
    Member States shall ensure that, when considering which measures referred to in paragraph 2, point (d), of this Article are appropriate, entities take into account the vulnerabilities specific to each direct supplier and service provider and the overall quality of products and cybersecurity practices of their suppliers and service providers, including their secure development procedures. Member States shall also ensure that, when considering which measures referred to in that point are appropriate, entities are required to take into account the results of the coordinated security risk assessments of critical supply chains carried out in accordance with Article 22(1).
    Normative force
    EU law to be transposed (directive): not directly applicable, requires national transposition
    Source
    Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive)
    Version
    CELEX 32022L2555 — ELI dir/2022/2555
    Official text
  6. 6ReCyF v2.5, objectif 3recyf:obj-3
    Les entités [importantes ou essentielles] réalisent et maintiennent à jour une liste des prestataires et fournisseurs informatiques intervenant dans la réalisation de leurs activités ou dans la fourniture de leurs services et avec lesquels il existe une relation de droit ou de fait ainsi que le périmètre et la nature de la prestation ou du service fourni. Les entités [importantes ou essentielles] mettent en place des processus visant à s’assurer, notamment par la voie contractuelle de la conformité des prestations informatiques dont elles bénéficient aux obligations auxquelles l’entité est assujettie notamment en matière de gestion des risques qui menacent la sécurité de leurs réseaux et systèmes d’information et de notification des incidents importants.
    Normative force
    obligation (decree, resilience bill)
    Source
    ReCyF — Référentiel Cyber France (NIS 2, transposition nationale)
    Version
    2.5 du 17/03/2026 (version de travail)
    Status
    Working version: not binding until the transposition is enacted
    Official text
  7. 7RGPD art. 28(3), point (c)32016R0679-a28-p3-3
    takes all measures required pursuant to Article 32;
    Normative force
    directly applicable EU law (regulation, level 1)
    Source
    Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)
    Version
    CELEX 32016R0679 — ELI reg/2016/679
    Official text
  8. 8RGPD art. 28(3), point (h)32016R0679-a28-p3-8
    makes available to the controller all information necessary to demonstrate compliance with the obligations laid down in this Article and allow for and contribute to audits, including inspections, conducted by the controller or another auditor mandated by the controller. With regard to point (h) of the first subparagraph, the processor shall immediately inform the controller if, in its opinion, an instruction infringes this Regulation or other Union or Member State data protection provisions.
    Normative force
    directly applicable EU law (regulation, level 1)
    Source
    Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)
    Version
    CELEX 32016R0679 — ELI reg/2016/679
    Official text
  9. 9Guide CNIL sécurité, fiche 14, F14-PE-02F14-PE-02
    Prévoir un contrat avec les sous-traitants, qui définit notamment l’objet, la durée, la finalité du traitement ainsi que les obligations des parties, notamment en termes de sécurité. S’assurer qu’il contient en particulier des dispositions fixant : la répartition des responsabilités et des obligations en matière de confidentialité des données personnelles confiées ; des contraintes minimales en matière d’authentification des utilisateurs ; les conditions de restitution et de destruction des données en fin du contrat ; les règles de gestion et de notification des incidents. Celles-ci devraient comprendre une information du responsable de traitement en cas de découverte de faille de sécurité ou d’incident de sécurité et cela dans les plus brefs délais lorsqu’il s’agit d’une violation de données personnelles ; l’assistance que doit fournir le sous-traitant pour garantir le respect des obligations de sécurité ; la revue régulière des mesures de sécurité et, le cas échéant, les conditions de leur révision.
    Normative force
    recommendation (soft law)
    Source
    Guide pratique RGPD — Sécurité des données personnelles
    Version
    2024 (mise à jour 2026)
    Official text
  10. 10Guide CNIL sécurité, fiche 14, F14-PE-03F14-PE-03
    Prévoir les moyens permettant de vérifier l’effectivité des garanties offertes par le sous-traitant en matière de protection des données (ex. : audits de sécurité, visite des installations). Ces garanties incluent notamment : le chiffrement des données selon leur sensibilité ou, à défaut, l’existence de procédures garantissant que la société de prestation n’a pas accès aux données qui lui sont confiées si cela n’est pas nécessaire à l’exécution de son contrat ; le chiffrement des transmissions de données (ex. : connexion de type HTTPS, mise en place de VPN) ; des garanties en matière de protection du réseau, de traçabilité, de gestion des habilitations, d’authentification, de pratiques d’administration, d’audits, etc.
    Normative force
    recommendation (soft law)
    Source
    Guide pratique RGPD — Sécurité des données personnelles
    Version
    2024 (mise à jour 2026)
    Official text