1. Know where personal data lives
List your systems, SaaS tools and file stores that hold customer or staff data. You cannot protect what you have not found.
Home / Security monitoring / GDPR compliance for small business
GDPR does not give you a list of tools. Article 32 asks for appropriate technical and organisational measures to protect personal data, in proportion to the risk. For a small business that comes down to a short set of controls you can prove are working. This guide lists them and shows what evidence to keep.
GDPR Article 32 is the security article. It says that controllers and processors must put in place appropriate technical and organisational measures to secure personal data. "Appropriate" depends on the state of the art, the cost, and the risk to the people whose data you hold.
The article gives four examples of what that can include. You choose what fits your business and you must be able to show why.
Encrypt data on laptops, in backups and on the wire. Where you can, separate identifying details from the rest of a record.
Only the right people can read the data, nobody can change it unseen, and your systems keep running when something breaks.
You can get personal data back in good time after a technical or physical failure. That means backups you have actually restored.
You test whether your measures still work. A policy written once and never checked does not meet this.
List your systems, SaaS tools and file stores that hold customer or staff data. You cannot protect what you have not found.
Use unique accounts and multi-factor authentication. Remove leavers the same day. Give people only the access their job needs.
Use HTTPS everywhere. Turn on disk encryption for laptops and phones. Encrypt backups.
Keep servers, websites and plugins up to date. Most breaches use a known flaw that already had a fix.
Keep a copy that an attacker on your network cannot reach, and restore it once to prove it works.
Check regularly for open services, forgotten test sites, expired certificates and leaked staff passwords.
Know which vendors touch personal data and where it is stored. Transfers outside the EU need a legal basis, so ask your lawyer.
Say who decides, who calls whom, and how you reach the 72-hour notification window. Practise it once.
A regulator or a customer rarely asks whether you own a security policy. They ask you to show that the measures were in place and working on a given date.
That is why we talk about continuous compliance. A yearly checklist tells you how you looked once. Continuous monitoring produces a dated record: what was exposed, what was found, who looked at it, and when it was fixed. That record is the technical evidence behind your Article 32 answer.
Keep it simple. A running log of scans, triaged findings, patch dates, restore tests and your breach response plan covers most of what a small business needs to show.
Secrabbit provides the technical side: monitoring of your public footprint, vulnerability triage by a person, leak checks, and an evidence trail you can hand to an auditor. Our infrastructure is EU-hosted. Read more in our security monitoring and compliance overview.
We do not give legal advice, act as your data protection officer or promise that you are compliant. No tool can. GDPR compliance covers contracts, consent, rights requests and training as well as technology.
This page is general information, not legal advice. Questions about whether a rule applies to you belong with your lawyer or your national authority.
Yes, if you handle personal data of people in the EU, whatever your size. Some record-keeping duties differ for smaller organisations, so check the details with your lawyer or data protection authority.
They are the security controls that protect personal data, such as encryption, access control, patching, backups and monitoring. Article 32 asks for measures that are appropriate to the risk, not a fixed list of products.
Article 32 names encryption and pseudonymisation as examples of measures to use where appropriate. Whether you need them depends on the risk of your processing. Encryption in transit and for laptops and backups is a sensible starting point.
Article 33 says to notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach, unless it is unlikely to put people at risk. Have a breach response plan before you need it.