Month: November 2025
The UK’s data-protection landscape is evolving fast, and SMEs are now directly exposed to enforcement action once largely associated with public bodies or large multinationals. As the BDO enforcement trends analysis reviewing ICO enforcement trends 2025, highlights, the ICO is increasingly focused on fundamental compliance failures rather than technical edge cases, meaning SMEs face the same expectations as larger organisations.
To help UK SMEs stay ahead, this guide breaks down the three most prominent ICO enforcement themes in 2025 and explains how each relates directly to the core duties under UK GDPR.
ICO Enforcement Trend 1: DSAR Delays & Right-of-Access Failures
The ICO continues to treat DSAR delays as one of the most serious indicators of poor governance. This theme appears repeatedly in enforcement notices and aligns closely with the BDO analysis.
A recent example is the enforcement notice issued to South Wales Police, requiring the organisation to clear a backlog of more than 350 overdue SARs by mid-2026.
Although policing bodies sit in a unique context, the principle is identical for SMEs:
a delayed, incomplete, or mismanaged DSAR is a governance failure, not an administrative error.
Why SMEs are vulnerable
- DSAR processes are often informal or undocumented
- Staff rely on untracked shared inboxes that hamper compliance
- Manual redaction takes longer than expected and slows response times
- Identity verification checks are inconsistent or incomplete
- No clear owner is assigned to coordinate DSAR responses
Consequently, SMEs often fail “by accident”, simply because processes were never clearly built.
What SMEs should do
- Implement a formal DSAR register
- Use standardised verification templates
- Assign responsibility for triage and drafting
- Create a redaction decision record
- Test your DSAR workflow every six months
See how Athlex Data Protection can help you with your UK GDPR compliance.
To strengthen your position, Athlex Data Protection includes DSAR review as part of its Free UK GDPR Compliance Audit.
ICO Enforcement Trend 2: System Errors & Data-Accuracy Failures
While many SMEs assume breaches are caused by sophisticated threat actors, the ICO’s recent fines show that basic security failings, particularly around access control and system configuration, remain the driving force behind most incidents. This is why BDO identifies weak security controls as a recurring enforcement theme.
A clear example of this is the £3.07 million fine issued to Advanced Computer Software Group (“Advanced”), a major processor used across the UK health and education sectors.
What happened
A ransomware attack exploited several preventable vulnerabilities, including:
- inadequate access controls,
- outdated software components,
- unpatched critical systems, and
- insufficient segregation of sensitive data.
Because Advanced was acting as a data processor, the incident demonstrated that processors are not insulated from ICO enforcement. Importantly, the ICO highlighted that robust Article 32 security measures apply equally to processors and controllers — a point many SMEs overlook when relying on third-party suppliers.
Why this matters for SMEs
Many SMEs rely on external IT providers, SaaS dashboards, or outsourced infrastructure. Consequently, they often inherit a false sense of security. Yet, as the Advanced case shows:
- unpatched systems,
- misconfigured access rights, and
- weak administrator controls can create breach pathways that affect both the processorand its clients.
Furthermore, the ICO’s commentary stresses that technical misconfiguration is increasingly treated as a governance failure, not an unavoidable risk. In other words, SMEs are expected to demonstrate continuous security management – not reactive fixes after an incident.
What SMEs should do now
To reduce exposure to similar enforcement action:
- Conduct regular patch-management reviews and document them.
- Enforce multi-factor authentication onevery administrative and remote-access account.
- Validate that third-party systems use secure configuration baselines.
- Request evidence: recent pen-test summaries, MFA logs, and architecture diagrams showing data segregation.
ICO Enforcement Trend 3: Supply-Chain & Vendor Risk Is Now the Biggest Exposure
BDO notes that third-party suppliers are involved in a significant proportion of enforcement cases. This is evident across recent ICO actions.
A major example is the £14 million fine issued to Capita following a cyber incident that exposed the data of over 6 million people.
The ICO criticised:
- slow isolation of the breach,
- insufficient monitoring,
- weak patching practices, and
- inadequate oversight of third-party systems.
Similarly, the Upper Tribunal’s Clearview ruling confirmed that even overseas vendors fall under UK GDPR if they monitor UK residents.
Why SMEs must pay attention
SMEs are more dependent than ever on external providers – IT contractors, payroll services, marketing platforms, CRMs, SaaS tools, cloud storage, etc. Consequently, the regulator expects SMEs to:
- verify supplier security
- assess processors before onboarding
- maintain a vendor register
- require evidence of compliance
- include audit rights and termination clauses
In other words, your compliance is only as strong as your weakest vendor.
What SMEs should do
- Inventory all suppliers with data access
- Request evidence: certifications, test summaries, logs
- Ensure processor contracts meet Article 28 requirements
- Assess vendors annually (high-risk: quarterly)
The Athlex Data Protection free audit highlights exactly where your vendor chain poses compliance risk.
ICO Enforcement Trend 4: Governance, Documentation & Accountability Are Under the Microscope
BDO’s report highlights that the ICO is increasingly examining how decisions are made, not just whether breaches occur. Good governance – leadership awareness, documented decisions, risk logs, and internal reporting structures — is now a major enforcement factor.
This aligns with the ICO’s call for views on new enforcement-procedural guidance, signalling more transparent and structured regulatory processes.
This means SMEs are expected to show:
- clear data-protection ownership
- leadership engagement
- meaningful internal reporting
- documented risk assessments and decisions
- evidence of proactive compliance
How SMEs Can Stay Ahead – Starting Today
To prepare for these enforcement trends, SMEs should immediately focus on:
✔ DSAR workflows
✔ Data-accuracy controls
✔ Vendor oversight
✔ Incident readiness
✔ Governance documentation
And the simplest way to begin?
Use Athlex Data Protection’s Free UK GDPR Compliance Audit tool.
To read more about the biggest UK GDPR risks for SMEs, see our blog: Inside Out: Why Insider Risk Is the Biggest UK GDPR Blind Spot for SMEs.
It covers DSARs, access controls, vendor risk, system accuracy, governance, and incident readiness – all mapped into a clear action plan.
Managing personal data responsibly is a legal requirement. Under the UK GDPR, anyone can request a copy of the personal data you hold about them and details of how you use it. This is called a data subject access request (DSAR). For SMEs, responding within the one-month deadline may feel challenging, but it is achievable. This guide explains your DSAR obligations, how to verify identity and gather data, and why prompt, compliant responses build trust.
REASON: The revised introduction introduces keywords like one-month deadline, DSAR obligations and verify identity. It provides clearer context and encourages readers by outlining benefits.
What Is a DSAR?
A DSAR is a request made by a person to obtain a copy of their personal data held by an organisation. It may also ask for details on how the data is processed, who it is shared with, the source of the data and how long it will be retained. Under the UK GDPR, organisations typically have one month to respond. In certain situations, you can extend this by two months, but you must inform the requester within the initial month and explain why. Failing to meet the deadline can lead to complaints and potential regulatory action, so timely responses are essential.
Who Can Make a DSAR?
Anyone can make a DSAR – customers, employees, suppliers or any individual whose data you process. The request doesn’t need to mention “DSAR” or cite the GDPR; it can be informal, verbal or written. Even a message on social media can count. Your responsibility is to recognise the request and handle it appropriately. Businesses should train staff to identify DSARs and direct them to the right person or team.
How to Respond to a DSAR
1. Verify Identity
Before disclosing personal data, verify the requester’s identity to prevent data breaches. If you’re not sure the person is who they say they are, ask for additional information such as a copy of an ID or details only the individual would know. Make sure your verification process is reasonable and proportionate; you shouldn’t request excessive or irrelevant documents.
2. Acknowledge Receipt
Send a prompt acknowledgement confirming you’ve received the request. Outline what you will do next, mention the one-month deadline and ask any clarifying questions if the request is vague. This sets expectations and demonstrates professionalism.
3. Gather Information
Identify all systems, databases and physical files where the requester’s personal data may be stored. This includes emails, customer relationship management (CRM) systems, cloud storage, paper records and any third-party processors you use. You must inform processors of the DSAR and ensure they supply relevant data.
4. Filter Data
Review the collected data and remove any information that is not personal data about the requester or that falls under exemptions. For example, data that identifies another individual may need to be redacted, or you may withhold information that’s legally privileged. Consult the UK GDPR and relevant guidance to determine what can be excluded.
5. Compile a Response
Prepare the data in an accessible format. Explain why you hold the data, the lawful basis for processing, how long you will retain it and who else it has been shared with. If the requester asked specific questions, address them. Provide the data securely—use encrypted email or secure download links – and clearly state how they can contact you for follow-up questions.
6. Keep Records
Document each DSAR you receive, including the date, actions taken, communications and final response. Good record-keeping helps demonstrate compliance if the Information Commissioner’s Office (ICO) investigates.
Why Efficient DSAR Handling Matters
Properly managing DSARs is not just about legal compliance; it’s a chance to build trust. Responding promptly and clearly shows that you respect individual rights. It also helps you maintain accurate records, which can improve overall data governance. Moreover, DSARs can highlight gaps in your data protection processes, prompting improvements. Finally, efficient DSAR handling minimises the risk of fines and reputational damage from mishandled requests.
Tips for Streamlining DSAR Processes
- Train Staff: Make sure employees understand what a DSAR is and whom to contact if they receive one.
- Develop a Standard Procedure: Create a step-by-step guide for handling requests, including templates for acknowledgements and responses.
- Use Data Mapping: Maintain an up-to-date record of where personal data is stored to save time when collecting information.
- Automate Where Possible: Consider using data discovery tools or DSAR management software to help identify and compile data.
- Plan for Complex Requests: Some requests may be broad or require input from multiple departments. Having a plan in place reduces delays.
Common Mistakes to Avoid
- Missing the Deadline: Start the process as soon as you receive a request. Even if you don’t have all the data yet, communicate progress and explain any delays.
- Overlooking Data Held by Third Parties: Remember that data processors are part of your supply chain. You remain responsible for data held on your behalf.
- Sharing More Data Than Necessary: Only provide data relating to the individual. Avoid disclosing information about other people or proprietary business information.
- Charging a Fee: DSARs are usually free. You can only charge a reasonable fee in certain circumstances, such as repeated requests or excessive volumes of data.
- Ignoring Informal Requests: A DSAR doesn’t have to mention the GDPR. Recognise any request for personal data as potentially valid and treat it accordingly.
How Athlex Can Help
Handling DSARs can be time-consuming and complex, especially for SMEs with limited resources. Athlex provides tailored support to ensure your DSAR responses are compliant and efficient. Our consultants can help you set up a procedure, train staff, and even manage requests on your behalf. From verifying identity to drafting clear responses, we offer the peace of mind that comes with expert guidance. Working with our outsourced Data Protection Officers (DPOs) means you can focus on your core business, knowing that data subject rights are respected.
Conclusion
A well-handled DSAR is a sign of a mature data protection practice. By following a clear process verifying identity, gathering and filtering data, and responding within the legal timeframe you can comply with your obligations and build trust with your customers and employees. Investing in good DSAR management now will pay dividends in the long run, reducing risk and strengthening your organisation’s data governance.
Read our blog http://athlex.co.uk/when-enforcement-isnt-enough-what-bristols-transparency-failures-teach-us-about-foi-dsars-and-accountability/ to find out what might happen if you get DSARs wrong.


