Data protection

Security addendum: what EU enterprise buyers ask for, and what to agree

An enterprise deal in Europe usually brings a security schedule, a questionnaire, a DPA annex of technical and organisational measures, or all three. Most of it is reasonable. Some of it commits you to controls you do not have and cannot build by signing.

Security addendum § 2 Security program

2.1 Vendor shall comply with Customer’s Information Security Policy, as amended by Customer from time to timeits written information security program, which is aligned to SOC 2 Type II and made available to Customer under Section 6 (Audit).

Guide example § 2
In short
  • Commit to the controls you operate, shown by a current third-party report, and not to the controls the buyer's template describes.
  • Keep security commitments (what you do) apart from liability for security failures (what you pay). They are separate negotiations.
  • A questionnaire answer is a representation: a “yes” to a control you lack is a breach on day one.
  • In EU deals the same promises appear in three documents. Keep the security schedule, the DPA annex and the questionnaire answers consistent.

What arrives with the contract

Three documents tend to arrive together. A security addendum or schedule sets out the controls you commit to maintain. A security questionnaire is a spreadsheet of a few dozen to several hundred questions about your practices. And buyers increasingly ask for your third-party assurance report: a SOC 2 Type II, an ISO 27001 certificate or a penetration test summary.

The three interact. Questionnaire answers often become representations under the contract, and the addendum commits you to maintain what the report describes. A careless answer in one can create liability under another.

Standard asks you should expect to give

  • Maintain a written information security programme appropriate to the data processed.
  • Encryption in transit and at rest, using current industry standards.
  • Access control based on least privilege, with multi-factor authentication for administrative access.
  • Vulnerability management and regular penetration testing.
  • Incident response process and breach notification within a defined window.
  • Business continuity and backup arrangements.
  • Personnel screening and security training.
  • Annual third-party assessment, with the report made available on request under NDA.

If you cannot give these, the contract is not the problem.

Asks that deserve pushback

  • Compliance with the customer’s internal policies, incorporated by reference and changeable at will. You cannot commit to a document you have not seen and cannot control. Replace with a commitment to your own documented programme and a named standard.
  • Technical controls in the buyer’s template that do not fit your architecture. “Dedicated hardware” or “customer-specific encryption keys” may be impossible in a multi-tenant product. Say so, and offer what you actually do.
  • Unlimited on-site audit rights. Meet them with the third-party report, and keep on-site audits for cause.
  • Notice of every security incident instead of every incident that affects the customer’s data. Limit the scope.
  • A guarantee of no breach. Nobody can give one. Offer a commitment to maintain the controls instead; the consequences of a breach belong in the liability clause.
  • Certifications you do not hold, due by a date you cannot meet. Do not promise ISO certification in ninety days if the audit is not scheduled.

The TOMs annex in an EU deal

With a European customer the security commitments often sit in the annex of technical and organisational measures (TOMs) to the DPA. It is the one part a client can check against reality, and the part vendors are most tempted to inflate. Write it in the present tense for what you operate today, and give a dated commitment for anything in flight. Keep it consistent with the security addendum and with your questionnaire answers: three documents that disagree about incident notice timing is the most common finding in a vendor audit. See the DPA guide for processors.

Answering the questionnaire

Treat every answer as a statement you would defend after a breach. The options are yes, no, and partial-with-explanation — and “partial with explanation” is the honest answer far more often than sales would like. A “no” with a compensating control described is almost always acceptable to a serious buyer. A “yes” that turns out to be false is a misrepresentation, and the contract’s liability cap may not protect you from it.

Build one master questionnaire with reviewed answers and draw from it. Answering each buyer’s questionnaire from scratch produces inconsistency, and what you told two customers is exactly what gets compared when something goes wrong.

Keep the two negotiations apart

What you do (the security commitments) and what you pay if it fails (liability, indemnity, breach costs) are different negotiations, often with different people on the buyer’s side. Security teams want controls; legal teams want recourse. Conceding an uncapped data breach indemnity because the security schedule was hard-fought is a common and expensive mistake. Hold the liability discussion until the security terms are settled, and settle it as part of the overall cap.

When to involve counsel

A security addendum is where legal and technical diligence meet. The right reviewer is a lawyer who speaks to your engineering lead before accepting a control, and does not mark up the schedule alone. A promise that engineering never saw is a promise you will break.

General information, not legal advice. This page describes how EU and cross-border commercial contracts commonly work; it is not advice on your situation, and no engagement arises until a service agreement with Icon.Partners is signed. For advice on a specific contract, speak to a lawyer qualified in the relevant jurisdiction.

Next step

Have a contract like this on your desk?

Send it over. We will mark it up and walk you through it in twenty minutes — no cost, and you will know whether the desk is worth it.

Book a contract call