encryption and data protection

Making Personal Information Safer With Practical Encryption

Every business that collects customer details, employee records, or account information has a responsibility to protect it. Encryption and data protection belong together because encryption can make information unintelligible to someone who lacks the correct key. However, switching on a security setting does not automatically make an organisation compliant with UK data protection law. Decisions about who can access information, how it is transmitted, and how systems recover from failure matter just as much.

For UK organisations, a useful starting point is the Information Commissioner’s Office (ICO) guidance. It explains a risk-based approach rather than a universal rule requiring identical encryption for every file. This article shows how to apply that approach to devices, cloud services, transfers, keys, and incident response without treating encryption as a complete security programme.

What Encryption Does—and What It Cannot Do

Encryption transforms readable information, known as plaintext, into ciphertext using a cryptographic process and a key. An authorised person or system can decrypt it when needed. If someone steals an encrypted storage drive but cannot obtain its decryption key, reading its contents may be much harder. That is a valuable safeguard, especially for portable equipment.

The relationship between encryption and data protection becomes clearer when you distinguish confidentiality from availability and integrity. Confidentiality limits unwanted disclosure. Integrity concerns whether data has been altered without authorisation, while availability means people can access information when they legitimately need it. Encryption can support confidentiality and, in suitable implementations, integrity, but lost keys can also make information permanently inaccessible.

Encryption Is Not the Same as Anonymisation

Encrypted customer records generally remain personal data when an organisation can decrypt them or otherwise identify the people concerned. Converting a database into ciphertext is itself a form of processing. Organisations must still consider lawful processing, retention, access rights, and the other relevant requirements of data protection law. ICO

Encryption and data protection should therefore be discussed within a larger governance programme.

What the UK GDPR Actually Requires

Article 5(1)(f) of the UK GDPR establishes the integrity and confidentiality principle. Article 32 requires controllers and processors to use technical and organisational security measures appropriate to the risk, naming pseudonymisation and encryption as possible measures. The ICO makes an important distinction: the law does not explicitly require every piece of personal information to be encrypted in every situation.

Nevertheless, the ICO recommends encryption for personal information transmitted electronically, stored on computing devices, and kept on removable media. In practice, encryption and data protection decisions should reflect the nature of the information, the potential harm from its exposure, the context of processing, the technology available, and implementation costs. ICO

Assess Risk Before Selecting Controls

Begin by identifying the personal information held, where copies exist, who uses them, and what could happen if a system or device were compromised. Sensitive records, financial information, credentials, and large datasets may require particularly careful protection. Map transfers to cloud providers, contractors, remote workers, and backup services rather than examining only the main office network.

When encryption and data protection are considered during a data protection impact assessment, document the identified risks and why particular safeguards were chosen. A DPIA is mandatory for certain high-risk processing, not for every routine operation.

Remember That Guidance Can Change

The ICO finalised its revised encryption guidance in September 2025. As of November 2026, the ICO website says that this material is under review following the Data (Use and Access) Act 2025. Organisations should therefore check the latest official guidance and the applicable law when approving policies or responding to incidents, rather than assuming an older summary remains complete. ICO

Protect Information Stored on Devices

Laptops and smartphones can be lost during travel, stolen from vehicles, or misplaced at home. Full disk encryption can protect information on a device when it is powered off and access controls are working correctly. The ICO advises enabling storage encryption on laptops, smartphones, and tablets holding personal information, and considering it on other devices where suitable. ICO

In an encryption and data protection programme, an asset register should identify which devices are encrypted and which remain exceptions. Recovery procedures should be managed centrally rather than leaving each employee responsible for an undocumented recovery key.

Consider Removable Media and Backups

USB drives, portable hard disks, exported spreadsheets, and backup copies can create overlooked exposures. Require approved encrypted storage where those devices are necessary, and avoid uncontrolled copies of customer records. Review backup encryption, retention, and recovery arrangements with cloud and IT suppliers. Test whether information can actually be restored after a failure.

Effective encryption and data protection also requires attention to devices being repaired, donated, recycled, or disposed of. Encryption reduces some risks, but proper data sanitisation and asset disposal processes remain important.

Keep Data Secure While It Travels

Data in transit moves between devices, websites, applications, and service providers. HTTPS uses Transport Layer Security (TLS) to protect web connections against certain forms of interception. The ICO expects organisations to use HTTPS, while the security of underlying connections depends on correct configuration, supported protocols, and valid certificates. Information Commissioner’s Office+1

Encryption and data protection should extend to staff portals, online forms, APIs, email workflows, and connections between systems. Review the complete route information takes, including external processors and automated exports.

Email and File Sharing Need Their Own Rules

An email service may encrypt transport links without providing end-to-end confidentiality across every stage. Sensitive attachments may warrant an approved secure portal or additional file encryption, depending on risk. Staff also need procedures for checking recipients, handling confidential requests, and reporting messages sent to the wrong address.

Good encryption and data protection does not mean choosing a complicated system that employees routinely bypass. Select approved tools that are secure and practical, train staff to use them, and establish how recipients obtain information without sending decryption passwords through the same insecure channel.

Manage Keys, Permissions, and Recovery

A strong encryption algorithm is only useful if its keys are protected. Keys and recovery secrets should have controlled access, appropriate storage, and clear ownership. The ICO discusses measures such as hardware security modules, role-based access control, and separation of duties where the circumstances justify them. ICO

The most serious weakness in some encryption and data protection arrangements is not the mathematics but operational practice. A password written beside a laptop, a shared administrator account, or a cloud key accessible to too many employees can undermine the intended safeguards. Apply the principle of least privilege, require strong authentication, and review privileged access regularly.

Plan for Lost or Compromised Keys

Organisations need documented recovery procedures. Losing a key may make valuable personal information permanently inaccessible, while a compromised key can require rotation and re-encryption. Establish who can authorise recovery, how keys are backed up, and how access is revoked when staff leave or responsibilities change.

Test Recovery Before a Crisis

A sound encryption and data protection policy should include rehearsed restoration exercises. An encrypted backup that nobody can decrypt during an outage offers little operational resilience. Recovery testing also reveals dependence on particular individuals or systems before an emergency happens.

Build Layers of Security Around Encryption

Encryption works best alongside access controls, software updates, multifactor authentication, device management, staff training, and incident monitoring. Protecting a laptop’s drive will not necessarily stop someone who signs in using a stolen employee password or obtains access while the device is unlocked. Malware, misconfigured sharing permissions, and insider misuse remain possible.

The ICO explicitly recommends treating encryption and data protection as part of defence in depth. Organisations should test, assess, and review the effectiveness of their measures rather than assuming a one-time purchase creates permanent compliance. Risk assessments should be updated after major system changes, supplier changes, or new threats. ICO+1

Put Written Responsibilities Behind the Technology

A practical security policy identifies when encryption is required, which systems and tools are approved, who manages keys, and how exceptions are assessed. It should also explain secure collaboration, remote working, records disposal, and incident reporting.

For growing businesses, encryption and data protection controls should remain workable when new software or contractors are introduced. Add security review to procurement, onboarding, and software deployment. Obtain appropriate contractual assurances and understand which controls belong to the provider and which remain the organisation’s responsibility.

Does Encryption Change Breach Reporting Duties?

Effective encryption can reduce the likelihood that stolen information can be understood by an unauthorised person. That can influence the assessment of risk to individuals and whether they need to be notified. It does not automatically mean an incident can be ignored or that notification to the ICO is unnecessary.

Under UK GDPR, a personal data breach generally must be reported to the regulator without undue delay and, where feasible, within 72 hours of awareness if it is likely to pose a risk to people’s rights and freedoms. Higher-risk incidents may also require communication to affected people. Investigate whether keys were compromised, data was already accessible, or records were lost and unavailable before making a decision. Legislation.gov.uk+1

An encryption and data protection incident plan should require prompt containment, preservation of evidence, accurate recording, and documented risk assessment. Obtain specialist advice where the facts or legal obligations are uncertain.

How to Turn the ICO Guidance Into a Working Plan

Start with the authoritative source rather than a product advertisement. The UK Information Commissioner’s Office’s guidance on encryption and data protection explains the security principle, the risk-based approach, encryption limitations, and the continuing status of encrypted personal information. It also provides examples showing why inaccessible data and poor key management can create compliance problems.

To improve encryption and data protection in practice, begin with a short inventory of personal information and its locations. Check laptops, mobile devices, removable media, websites, cloud storage, backups, and external transfers. Identify gaps, prioritise the highest risks, and decide who will implement and verify the chosen controls. Record the reasons for any exceptions rather than relying on informal assumptions.

Review, Test, and Improve

After deployment, confirm that device encryption is active, secure connections are correctly configured, keys are recoverable by authorised personnel, and backup restoration works. Review access privileges and respond to vendor security notices. Repeat assessments when the information processed, systems used, or risks change.

A mature encryption and data protection approach is measured by dependable protection and documented decisions, not by the number of security features a supplier advertises. Clear accountability helps an organisation respond convincingly when staff, customers, or regulators ask how their information is protected.

Frequently Asked Questions

Does the UK GDPR require encryption of every file?

No. The law requires security measures appropriate to the processing risks and lists encryption as an example. The ICO nevertheless recommends it for electronic transfers, computing devices, and removable media holding personal information. The appropriate decision must be documented in context.

Is encrypted customer information still personal data?

Usually yes. If an organisation can decrypt the records or identify individuals, UK GDPR obligations still apply. Encryption does not automatically anonymise information or remove other legal duties.

Is HTTPS enough to secure a business website?

HTTPS is important for protecting information in transit, but it does not secure a poorly configured database, weak accounts, or sensitive information stored elsewhere. Websites also need secure applications, permissions, and regular maintenance.

What happens if a business loses its decryption key?

Information may become inaccessible, potentially creating an availability problem and, depending on circumstances, a personal data breach. Secure recovery arrangements and tested backups are essential parts of responsible key management.

Must a stolen encrypted laptop always be reported to the ICO?

Not automatically. Assess whether the encryption was effective, whether keys or credentials were exposed, and the risk to individuals. Reporting duties depend on the circumstances; organisations should document the assessment and follow current ICO breach guidance.

How often should security arrangements be reviewed?

There is no single schedule suitable for every organisation. Review controls in line with risk, after major changes, and when vulnerabilities emerge. Regular testing, access reviews, and recovery exercises help show that safeguards remain effective.

Conclusion

Encryption is a practical safeguard for personal information, but it is not a substitute for responsible governance. Effective encryption and data protection combines risk assessment, secure devices and transfers, reliable key management, and trained people. UK organisations should use the ICO’s guidance as a foundation while checking legal updates and addressing risks that encryption cannot solve. The strongest approach is one that can be explained, tested, and improved as business needs change.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top