The foundation: engage.re
Security 30 July 2026 10 min read

Half of UK Small Businesses Had a Breach. Look at the Architecture.

Roughly half of UK small businesses report a breach or attack each year. Most responses treat this as a training problem or a firewall problem. A third factor sits underneath both: your data lives in six suppliers' systems, so you depend on six security practices, and every copy between them is another door. This article shows the arithmetic, and states which properties change it.

Connect with us about a secure estate · · Replies within 24 hours

~50%
of UK businesses report a breach or attack in a year
6
suppliers means six security practices you do not control
72 hrs
to report a notifiable breach to the ICO

What do the official figures say?

The Department for Science, Innovation and Technology publishes the Cyber Security Breaches Survey each year. It reports the share of UK organisations that identified a breach or attack, and the figure has stayed close to half for businesses across recent editions.

The survey also reports low uptake of basic controls among smaller organisations. Many hold no incident response plan, and many do not know which of their suppliers hold their data.

Two problems therefore run together. Attacks are common, and the ability to answer questions after one is uncommon.

Why does supplier sprawl raise your risk?

Count the systems that hold your customer data. A booking tool, an accounts package, a customer relationship system, a payroll provider, a marketing platform and a document store. Six suppliers is a normal position for a small organisation.

Three consequences follow, and each one is arithmetic rather than opinion.

  • Six security practices. Your exposure is the weakest of the six, and you control none of them.
  • Six sets of credentials. Each one is a route in, and each one has its own password rules.
  • Copies between them. Every integration moves data, and the copy at the other end has its own retention and its own access list.
The copies are the part nobody counts. A person can list six suppliers. Nobody can list every copy of a customer record across six systems, their backups, their reporting extracts and their integrations.

What happens in the first 72 hours?

UK data protection law requires you to report a notifiable personal data breach to the ICO within 72 hours. The ICO sets out the duties in its UK GDPR guidance.

The report needs four facts. Which data was affected. How many people. What you have done. What risk the people now face.

Fact needed Six suppliers One estate
Which records were read?Ask six suppliers, and wait.Query your own event log.
How many people?Add six answers, and hope for no overlap.Count once.
Who read them?Six log formats, if logs exist.One named actor per event.
Could the log be altered?Usually yes.No, the chain would break.

The fourth row decides what the other three are worth. A log an administrator can update records what somebody chose to leave in it.

Which properties change the position?

Five, and each one is a design decision made before your data exists.

  1. One estate instead of six. One security practice to assess, one set of credentials, and no copies between suppliers.
  2. One gate per domain boundary. One place decides every crossing, so you can state your access policy by reading one thing.
  3. Encryption per record. A breach of the store yields ciphertext, and destroying a key destroys access to that record everywhere.
  4. A signed event chain. Each entry carries a hash of the entry before it, so an alteration is detectable.
  5. Retention and legal hold as data. Each record states the rule that governs it, rather than a policy document stating it.

The National Cyber Security Centre's Cyber Essentials scheme covers the controls that sit above these properties, and the ICO's guidance on encryption treats it as a core security measure.

Where a controls framework stops

A framework asks whether you have a control, and it does not ask how many places must hold it.

Consider access control. A framework asks whether access is limited to what a role needs. Six suppliers means six answers, six audits and six chances of a wrong answer. Your certificate then describes six separate positions.

Frameworks are worth holding. They measure practice, and architecture decides how much practice is needed.

What ESRE Media offers

We build your system on engage.re, and the five properties above are properties of the platform.

  • One estate. Your records live in one place, so no integration copy sits in a supplier you did not assess.
  • One gate. One authorisation decision covers every domain crossing. One production estate we work on replaced 219 scattered checks with a single gate.
  • Per-record encryption, with your keys. Destroying a record's key destroys access to that record, including in backups.
  • Every access is a signed event. Each entry carries a hash of the entry before it, so your incident report states facts rather than recollections.
  • Retention and legal hold enforced. Each record carries its retention class, and a held record resists deletion.
  • One identity model. Your people, your applications and your agents all prove identity the same way.

Sense Future built engage.re, and it has run in production since December 2025.

Fewer systems, not fewer abilities

A common objection follows. One estate means one supplier, so you depend on us instead of six.

Three properties answer it, and each one is checkable before you sign.

  • You hold your keys. Our access to your data is not a matter of our policy.
  • You can host it yourself. A conformance package is published at version 2.0.0, so a third party can build a conforming implementation.
  • Your meaning travels. Your definitions are data, so an export carries the rules with the records.

We set out the seven pre-signature tests in vendor lock-in, what can you prove before you sign.

The same arithmetic at two sizes

A council runs forty systems from twenty suppliers. A breach in one supplier starts a three-week exercise to establish which residents were affected, and the 72-hour clock runs from the moment the council becomes aware.

A small business runs six systems. The exercise takes three days instead of three weeks, and it exceeds the same deadline. The arithmetic scales, and the deadline does not.

The care home software and retail software pages set out the sector detail. Our guides to the Data Security and Protection Toolkit and provable erasure cover the duties that follow an incident.

What we do not claim

  • Architecture does not prevent attacks. It decides what an attack reaches, and what you can prove afterwards.
  • One estate is not automatically safer. It is safer where the properties above hold, and each one is testable.
  • Training still matters. Most incidents start with a person, and no architecture removes that.

What to do next

  1. List every supplier that holds your customer data. Most organisations find more than they expected.
  2. Ask each one for a full access list for one record, and time the responses.
  3. Count the copies of one customer record across systems, backups and extracts.
  4. Ask whether anybody can alter your audit logs.
  5. Then measure your answers against the 72-hour deadline.

Common questions

How many UK small businesses have a cyber breach?

Roughly half of UK businesses identify a breach or attack in a year, on the Cyber Security Breaches Survey published by the Department for Science, Innovation and Technology. The same survey reports low uptake of basic controls among smaller organisations, and many hold no incident response plan.

Why does using several software suppliers raise risk?

Because your exposure is the weakest of their security practices, and you control none of them. Six suppliers means six sets of credentials, and every integration between them creates a copy with its own retention period and its own access list. The copies are the part nobody can count.

What do we have to report after a breach?

A notifiable personal data breach must reach the ICO within 72 hours. The report needs four facts: which data was affected, how many people, what you have done, and what risk those people now face. Answering across six suppliers usually takes longer than the deadline allows.

What makes an audit log trustworthy?

Anti-falsification. A log whose rows an administrator can update records what somebody chose to leave in it. A log that carries a hash of the previous entry in each new entry makes any alteration detectable, and that property is what gives an incident report weight.

Does Cyber Essentials cover this?

Partly. A controls framework asks whether you have a control, and not how many places must hold it. Six suppliers means six answers, six audits and six chances of a wrong answer. Frameworks measure practice, and architecture decides how much practice is needed.

What does ESRE Media build?

We build your system on engage.re. Your records live in one estate with one gate deciding every domain crossing, each record is encrypted separately under keys you hold, every access is an event in a signed chain, and each record carries its own retention class and legal hold.

Connect with us about a secure estate · · Replies within 24 hours

Sources and further reading