Article 32 of the GDPR asks for “appropriate technical and organisational measures”. The wording is vague on purpose, because the right measures depend on the risk. For a small site or online shop it comes down to six controls that customers, auditors and insurers actually ask about.
Six controls that matter
- Encryption in transit. HTTPS on every public page and every admin panel, and TLS for mail (IMAP on 993, authenticated SMTP submission on 465 or 587).
- Access control. One account per person, multi-factor authentication on the hosting panel, the registrar and the mail admin, and removal of former staff on their last day.
- Updates. CMS core, plugins, themes and the PHP version. Outdated plugins are a common way into small sites.
- Backups you have restored. Keep copies off the server, run a restore test and know how long deleted personal data survives in old backups.
- Logs with a retention rule. Keep access logs long enough to investigate an incident and no longer. Pick a period and write it down.
- Breach readiness. Article 33 gives you 72 hours from becoming aware to notify the supervisory authority, unless the breach is unlikely to put people at risk. In Bulgaria that authority is the Commission for Personal Data Protection. Where the risk to individuals is high, Article 34 also requires telling them.
Evidence an auditor accepts
| Control | What you can show |
|---|---|
| Encryption | A valid certificate on every host name, mail TLS settings |
| Access | A list of admin accounts with MFA status and owner |
| Updates | A dated update log or an automatic update setting |
| Backups | The date and result of the last restore test |
| Logs | The retention period in your records |
| Breach | A one-page runbook: who decides, who calls, who writes |
Keep a record
Article 30 expects a record of processing activities for most organisations. Add the hosting location, the processors involved and the security measures above. One shared document is enough if it stays current.
What hosting does for you
A free certificate comes with web hosting, so encryption in transit is covered from day one. On a cloud server you also own the firewall, SSH access and patching of the operating system. Choosing the host is covered in why GDPR-compliant hosting matters.
Frequently asked questions
Is encryption at rest mandatory?
Article 32 names encryption as an example of a measure, not as a fixed rule. Decide by risk: laptops, backups and databases with sensitive data usually justify it.
Do small businesses need all six?
The depth scales with risk, but HTTPS, MFA, updates and tested backups are expected at every size.
How fast must a breach be reported?
Within 72 hours of becoming aware, where the breach is likely to put people at risk. Write down the decision either way.
Is a firewall enough?
No. A firewall limits exposure. Weak passwords, missing updates and untested backups remain open.




