Skip to content

Issue of the newsletter Conformidade em Foco

Fornecedores tecnológicos: o contrato e o calendário das obrigações.

16 November 2026

Conformidade em Foco

Technology suppliers: the contract and the timetable of the duties

The heading is the original title, in Portuguese.

Translation of the Portuguese original. The citations follow the Portuguese wording.

Technology suppliers. The contract and the timetable.

A security clause can be technically demanding and still be poorly framed in law. That happens when GDPR duties, preparation for the cybersecurity regime and contractual choices of good practice are confused.

  1. First, identify the processing relationship

If the supplier processes personal data on behalf of the organisation, Article 28(1) of the GDPR requires the controller to use only processors that provide sufficient guarantees to implement appropriate technical and organisational measures.

Paragraph 3 requires a contract or other binding legal act that sets out, among other elements, the subject matter and duration of the processing, its nature and purpose, the types of data and the categories of data subjects. It must govern documented instructions, confidentiality, security, the use of other processors and assistance to the controller.

It is not enough to call the supplier a "processor". The qualification must match the function actually performed.

  1. Make the duty verifiable

Article 28(3)(h) of the GDPR requires the processor to make available the information needed to demonstrate compliance and to allow for and contribute to audits, including inspections.

As an implementation proposal, I recommend a sheet with three fields: the contractual duty, the evidence to be produced and the person responsible for checking it. The form of this sheet is an organisational choice, not a template imposed by the GDPR.

How often the check is made should be justified by the risk. I do not present an annual review of every supplier as a general legal time limit.

  1. Do not give the supplier the authority's 72 hours

Article 33(2) of the GDPR requires the processor to notify the controller without undue delay after becoming aware of a personal data breach.

That is different from the controller's duty towards the supervisory authority, in paragraph 1: without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons.

I recommend that the contract identify contacts, the minimum information and the escalation path. No contractual time limit authorises a delay that breaches the duty to communicate without undue delay.

  1. Read when the cybersecurity regime takes effect

Article 10(2) of Decree-Law 125/2025 provides that certain provisions of the annexed regime, including Article 27(1) and (2) and Article 28, take effect 24 months after publication of the regulations identified there.

Finding supply-chain security in Article 27, or the criteria for assessing suppliers in Article 28, is therefore not enough to conclude that those duties are already enforceable in November 2026.

Contractual preparation can and should be discussed now. It must, however, be presented as preparation, without anticipating the taking of effect of the rules and without dispensing with a check of the regulations and of each entity's position.

This deferral does not mean that every cybersecurity duty is suspended. The other rules that apply to the entity and to the service, including the GDPR, must be checked.

  1. A practical sheet to start with

I propose five working questions, not a public questionnaire:

  1. Does the supplier process data on behalf of the organisation?
  2. What access and dependencies does the service create?
  3. Which legal and contractual duties apply today?
  4. What evidence makes it possible to check that they are met?
  5. Which future duties justify preparing the contract now?

My position: a sound contract distinguishes the legal duty in force, the duty whose taking of effect is deferred, and the measure of good practice. Mixing them does not strengthen compliance.

  • RGPD
  • Cibersegurança
  • Compliance

Official sources

Last reviewed 8 November 2026.

Read on LinkedInSubscribe on LinkedIn