Begin with consequences, not a product list

UK GDPR requires security appropriate to the risk. Confidentiality, integrity and availability all matter: preventing unauthorised disclosure is only one part of the task. A business can also harm people by losing essential records or allowing inaccurate information to drive decisions.

Our recommended assessment starts with a few realistic scenarios. What happens if an employee account is compromised, a device is lost, a supplier becomes unavailable or a shared folder is accidentally opened to outsiders? Identify the people affected and the likely consequences. That gives a more useful basis for prioritising controls than copying a generic list of security products.

Know who can access what

Give people access appropriate to their role, not to everything they might possibly need one day. Separate routine accounts from administrative access where practicable. Remove access promptly when people leave or responsibilities change, including access to shared mailboxes, external collaboration spaces and connected services.

For implementation, maintain a small list of critical systems and their owners. Each owner should know who can approve new access and who reviews it. Pay particular attention to dormant accounts and externally shared links: these can remain active after the original reason for sharing has disappeared. A regular permissions review should produce actual changes and evidence, not merely an email asking colleagues whether everything looks right.

Protect the accounts that control the others

Email and administrator accounts often act as gateways to other services. The NCSC recommends additional authentication protection for important accounts. Multi-factor or two-step verification reduces reliance on a password alone, although the available methods have different strengths and recovery considerations.

Do not stop at enabling the setting for one owner. Check privileged users, finance accounts and recovery routes. Make sure recovery information is controlled and accessible to authorised people if a device is lost. Our practical recommendation is to document how the business would recover a critical account during an absence without sharing a personal password around the office.

Distinguish synchronisation from a recovery plan

A synchronised folder can reproduce an accidental deletion or malicious change across devices. The NCSC’s backup guidance emphasises keeping recoverable copies of information needed to operate. The relevant question is not whether a cloud service says it has backups, but what you can restore, how far back and how quickly.

Test restoration using an appropriate sample and record the result. Include attachments, permissions and any records needed to interpret the recovered files. Consider protecting backups from the same credentials or incident that could affect the live system. Decide which services need the fastest recovery and keep essential instructions available somewhere other than the service you are trying to restore.

Use encryption with a clear purpose

Encryption can materially reduce the consequences of losing a device or intercepting information, but it does not solve every security problem. It may not protect data from someone who is already signed into an authorised account, and it cannot compensate for an unrestricted sharing link. The ICO treats it as an important measure to consider in context.

For a practical review, distinguish protection while information is stored from protection while it is transmitted. Check mobile devices, removable media, backups and transfers to advisers. Ask who controls the keys and how recovery works. An encryption claim on a supplier’s website should prompt specific questions about the service and configuration being used rather than end the assessment.

Keep the ordinary maintenance working

Security controls deteriorate when devices and software are left unsupported, updates are postponed indefinitely or staff cannot recognise suspicious requests. Assign ownership for updates, endpoint protection and the retirement of old equipment. Training should reflect the decisions staff actually make, such as checking a changed bank detail or sharing a customer file.

Our suggested exercise is to follow one document from creation to disposal. Look at local copies, email attachments, printouts, home working and supplier access. Technical safeguards need supporting procedures: a locked laptop does little for a paper file left in a public area. Make reporting mistakes straightforward so people raise concerns early rather than hide them.

Ask suppliers for usable assurance

A supplier may operate secure infrastructure while your configuration remains too permissive. Establish which controls belong to the provider and which remain yours. For important services, ask how access is logged, incidents are escalated and information is returned or deleted at exit.

Avoid treating a certification as proof that every aspect of your use is compliant. It can be useful evidence, but scope and currency matter. Record the questions that remain unanswered and the consequence of accepting them. Procurement and security should inform each other before a service becomes difficult to replace.

Build a routine that leaves evidence

A manageable review can cover critical accounts, overdue updates, failed backups, departed users and newly shared information. The frequency should reflect the risks and pace of change. Keep brief evidence of checks and corrections so that ownership survives a change of staff.

These are practical controls, not a promise that incidents can never happen. The aim is to reduce avoidable exposure and make recovery credible. Where technical risks exceed the business’s competence, obtain suitably skilled support rather than assuming a policy document can substitute for secure implementation.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.