# Cyber risk in contracts: who does what, before it happens.

> When an incident happens, the first question is whose job it was: who was meant to run the backups, who was meant to update, who was meant to notice and raise the alarm. We read your IT contracts from the technical side, write down who does what, answer security questionnaires from customers and insurers with you, and close what is missing.

- Service: Technical review and security annexes
- For: IT contracts, questionnaires, cyber policies
- With: Your lawyer and your DPO
- URL: https://cloudfactory.it/en/services/cyber-risk-it-supplier-contracts/

## Each side thought the other was taking care of it.

Many IT contracts describe the service in one line, support or systems management, and don't say who runs the backups, who tests restoring them, who installs updates, how soon an incident must be reported and to whom. While everything works nobody notices. On the day of the incident customer and supplier find they had assumed different things. Meanwhile security questionnaires arrive from larger customers, along with the insurer's questions, and they have to be answered truthfully.

## We are suppliers too.

We receive the same requests you do: questionnaires, checks, security clauses. For the Italian site of an international group of laboratories we closed the findings from an external rating and a penetration test. We have taken over environments inherited from other suppliers, where the first thing to rebuild was who had access to what. We know what is reasonable to ask of a supplier and what a supplier can truly promise.

## From the contract to the systems, and back.

1. **Map suppliers and access.** Who manages what: hosting, email, business software, support, development. For each, which systems and data they reach and with which credentials.
2. **Read the contracts from the technical side.** We compare what is written with what really happens: backups, recovery times, updates, monitoring, subcontractors, incident notice, return of data when the relationship ends.
3. **Write down who does what.** A task matrix for every system: who does it, how often, who checks it was done. It becomes the technical annex your lawyer builds the clauses on.
4. **Answer the questionnaires.** We fill in security questionnaires from customers, banks and insurers with you: answers checked on the systems, with the evidence to attach and an honest list of what isn't there yet.
5. **Close the gaps.** Two-factor authentication, backups with a restore test, accounts in your name, supplier access that is personal and revocable. What you declared has to be true.

## A technical annex that matches reality.

Documents a lawyer can use and a technician can verify. Your lawyer writes the clauses: we give them the facts.

- Map of suppliers and access
- Task matrix
- Technical notes on contracts
- Security technical annex
- Completed questionnaires
- Evidence to attach
- List of gaps
- Remediation plan

## What we look at and what the rules ask for.

### What we look at in an IT contract

- **Scope**: which systems are included and which aren't. What isn't named usually belongs to nobody.
- **Backup and restore**: who runs them, where the copies are, how often a restore is tested, how long it takes to be running again.
- **Updates and vulnerabilities**: who installs them, how soon, what happens with systems that can't be updated.
- **Access**: personal accounts, two-factor authentication, what happens when someone leaves the supplier.
- **Incidents**: how soon the supplier tells you, whom, with what information, and who talks to the authorities.
- **Subcontractors**: who else has their hands on your systems, and where the data is.
- **Contract exit**: return of data, credentials and documentation, and whose name domains, cloud accounts and licences are in.

### What the rules ask for

- **GDPR, Article 28**: whoever processes personal data on your behalf needs a contract saying what they do, with which security measures and which subcontractors. **Article 33**: the supplier tells you about a breach without undue delay, and you have 72 hours to notify the authority ([text of the regulation](https://eur-lex.europa.eu/eli/reg/2016/679/oj)).
- **NIS2**: organisations under the directive must manage the security of their direct suppliers, including through contract requirements ([Agenda Digitale on the ACN FAQs](https://www.agendadigitale.eu/sicurezza/nis2-e-fornitori-cosa-prevedono-le-faq-acn-sui-contratti/), in Italian). If you supply one of them, the requests reach you by contract even if the directive doesn't apply to you.
- **Italian Civil Code, Article 1229**: an agreement that excludes or limits liability in advance for wilful misconduct or gross negligence is void. An exemption clause is no substitute for work done well and documented.
- **Cyber policies**: questionnaire answers are statements the insurer uses to assess the risk. If they turn out to be inaccurate, the payout can be reduced or refused (Italian Civil Code, Articles 1892 and 1893).

These are technical pointers, not legal advice: the clauses need your lawyer.

## When the request arrives.

- **Those who receive a security questionnaire**: A larger customer, often under NIS2, asks how you protect its data. True answers are needed, with evidence.
- **Those taking out or renewing a cyber policy**: The insurer asks about two-factor authentication, backups and updates. Better to check before signing.
- **Those changing IT supplier**: The right moment to write down who does what and to get access, data and documentation handed back.
- **Healthcare facilities and professional firms**: Several suppliers on the same systems, with data that must not leak. You need to know who answers for what.

## Before signing.

### Do you write the clauses?

No. We prepare the facts and the technical annex: who does what, how soon, how it is verified. Clauses, liability limits and penalties are your lawyer's work, and we are glad to work alongside them.

### Is a clause that shifts liability enough?

No. In Italy an agreement excluding liability in advance for wilful misconduct or gross negligence is void, and no clause gives you your data back. It works better to write each party's tasks precisely and be able to show they were carried out.

### We aren't under NIS2: does it concern us?

Often yes, by contract. Organisations under the directive must check their direct suppliers and pass requirements and questionnaires on to them. And if you process personal data on behalf of others, Article 28 of the GDPR applies anyway.

### Can you answer the questionnaire for us?

We fill it in together: we check on the systems and prepare answers and evidence, you sign. Where the true answer is no, we write that, with the plan to get there.

---

Cloudfactory S.r.l., Rome. Contact: hello@cloudfactory.it
