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.
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.
From the contract to the systems, and back.
- 01
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.
- 02
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.
- 03
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.
- 04
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.
- 05
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.
What we look at and what the rules ask for.
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.
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.
Where we've done it before.
Security remediation for a laboratory group.
External rating and penetration test findings closed one by one, then three inherited servers replaced by two, managed directly.
An inherited AWS environment, put back in order.
EC2 in Ireland and Milan, RDS MySQL, the old provider's access removed, servers managed through SSM with no SSH exposed, a stuck server recovered, costs reviewed line by line.
Email that leaves only from those entitled to send it.
Per-site SES policies with allowed IPs, a DMARC path from p=none to p=reject, SendGrid authentication and SPF under 10 lookups. One mistake stopped before going live.
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.