WordPress maintenance & security

WordPress security: encryption, authentication, audits and the GDPR

WordPress maintenance & security

WordPress security: encryption, authentication, audits and the GDPR

Keeping WordPress up to date does not guarantee optimal protection when your website handles sensitive forms, accounts or members’ areas.

Farweb

–

4–7 minutes

Keeping WordPress up to date does not guarantee optimal protection. Fundamental practices such as updates, backups and strong passwords remain crucial, but they do not cover all risks.

As soon as a website handles forms, user accounts, members’ areas, online shops, HR information, etc., a more robust approach is required: securing data transmissions, tightening administrative access controls and demonstrating your control over data. This approach aligns with GDPR requirements: minimising data collection, ensuring traceability and controlling the data lifecycle.

Encryption: securing data in transit and certain stored data

Encryption is often reduced to simply ‘enabling HTTPS’. This view is incomplete.

HTTPS (TLS) encrypts communications between browsers and your platform. Without this protection, contact forms, login pages or extranet areas risk exposing information whilst it is being transmitted.

Recommended practical measures:
– Enforce HTTPS across the entire site (public interface and administration).
– Check that no resources load via HTTP (images, scripts) to avoid mixed content.
– Enable HSTS where your hosting provider and configuration allow (to prevent unintended fallsback to HTTP).

Useful tools:
– TLS/SSL certificates provided by the hosting provider (usually based on Let’s Encrypt).
– Configuration assistance extensions if necessary: Really Simple SSL / Really Simple Security (to be used as a temporary aid, not as a permanent solution).

Encryption of non-transmission data: emails and integrations

A great deal of personal data is transmitted via:
– Email notifications (forms, orders, registrations).
– APIs (CRM, marketing tools, HR platforms, etc.).

Recommended actions:
– Use SMTP with TLS for sending emails (rather than standard PHP sending).
– Document integrations: what information is sent to which data processors (GDPR requirement).

Useful plugin:
– WP Mail SMTP (to configure reliable sending via an SMTP/transactional provider).

Encryption of stored data: databases, backups, exports

WordPress already encrypts passwords (hashing). However, custom fields (stored sensitive form data) or backups may contain personal data in plain text.

Recommended practices:
– Encrypt backups (or drastically restrict access to files and storage).
– Avoid storing sensitive information in WordPress unless absolutely necessary (GDPR principle of data minimisation).
– Define a retention period and a data deletion process.

Multi-factor authentication (2FA/MFA): strengthening access to the dashboard

Multi-factor authentication adds an extra verification step during login (app code, physical key, etc.). In practice, even if a password is leaked, access remains blocked.

Who should enable 2FA as a priority?
– WordPress administrators.
– Editor accounts with access to data (forms, orders, members).
– Agency or service provider accounts (temporary or maintenance access).

Gradual roll-out (without disrupting the team)
– Start with a pilot group (2–3 accounts).
– Require 2FA for privileged roles: administrator, editor.
– Provide backup codes and an internal procedure in the event of a lost mobile phone.
– Reduce the number of administrators: a WordPress site generally runs very well with 1–2 admins and appropriately assigned roles.

Common plugins:
– Wordfence Login Security (2FA + login protection).
– Two Factor (lightweight plugin, multiple options).
– Solid Security (iThemes Security) (security suite including 2FA depending on the version).

Regular audits: moving from declarative security to verifiable security

An audit does not necessarily have to be a major undertaking. For WordPress, it is often a routine process: check, correct, track.

What a useful WordPress audit should examine
– Accounts and access: roles, inactive users, contractor access, password policy.
– Plugins and themes: unused plugins, versions, source, active maintenance.
– Logging: logins, critical changes, recurring errors.
– Backups and restoration: frequency, retention, restoration testing (all too often overlooked).
– GDPR compliance: cookies, forms, consent, retention periods, requests for access/deletion.

How often?
– Monthly: quick review (plugins, accounts, alerts).
– Quarterly: in-depth audit (logs, restore tests, compliance checks).
– After every major update: new form, members’ area, redesign, addition of an integration.

Useful tools and plugins:
– Wordfence / Sucuri / Solid Security: alerts, checks, hardening.
– WP Activity Log: action history (also useful in an agency context).
– UpdraftPlus / BlogVault: backups with scheduling options (as required).

GDPR: linking security and compliance without adding unnecessary complexity

The GDPR is not limited to a cookie banner. Above all, it requires a focus on control: collect less, inform better, maintain control.

Key obligations to remember
– Minimal data collection: only ask for what is necessary.
– Legal basis and consent: explicit consent where required (e.g. for marketing), clear information on how data will be used.
– Data subjects’ rights: access, rectification, erasure (right to be forgotten), portability where applicable.
– Retention periods: define and apply rules (automatic deletion of unnecessary logs, purging of form submissions).
– Data processors: hosting providers, email marketing tools, CRMs, etc. must be identified and regulated (Data Processing Agreement/contract).

What WordPress already offers (often underused)
– Privacy pages and tools (privacy policy).
– Tools for exporting and erasing personal data (Tools menu).

Plugins to automate part of the compliance process
– Complianz (cookie management, register, document generation based on configuration).
– CookieYes (focus on the cookie banner and consent).

Point to note: these plugins make compliance easier, but do not guarantee it. Compliance also depends on your forms, your content, your integrations and your internal organisation.

Key takeaway:
Encryption isn’t just about the padlock icon – also consider emails, APIs and backups.
– Multi-factor authentication is one of the most effective safeguards for admin access.
– Regular audits transform intuitive security into controlled security.
– The GDPR encourages collecting less data, retaining it for shorter periods and responding to user requests.
– Extensions help, but compliance remains a holistic approach: technical + content + processes.

Frequently Asked Questions

Is HTTPS enough to ensure GDPR compliance?
No. HTTPS improves the security of data transfers, but GDPR compliance also covers data minimisation, information, consent, retention and individuals’ rights.

Do I need to enable 2FA for all users?
Not necessarily. In practice, you should require it at the very least for administrators and accounts with access to sensitive data. For others, it can be optional depending on the context.

Does a GDPR extension automatically make my website compliant?
No. It makes it easier to manage cookies, text and certain settings, but it does not replace your data collection policies, your contracts with data processors or your internal processes.

What is the purpose of an audit log?
To track who has done what on the site: logging in, installing a plugin, changing settings, or modifying content. It is useful for monitoring, quality assurance and governance.

Conclusion

WordPress security and the GDPR reinforce each other: encryption, multi-factor authentication and audits make your site more robust, whilst facilitating compliance (traceability, data control, procedures).

 

Need some clarity? We can help you draw up a realistic checklist (security + GDPR), tailored to your site, your team and your constraints.

f.

  • Agency & ecosystem

    Farweb at WordCamp Netherlands 2026

    On 12 and 13 November, we’re off to The Hague in the Netherlands for WordCamp Netherlands 2026, held in the rather unusual setting of Madurodam

    Read article →

  • Hosting & eco-design

    Faille de sécurité PHP : votre site WordPress est-il concerné ?

    PHP security vulnerability: is your WordPress site affected?

    On 21 October 2026, two major security vulnerabilities were patched in PHP, the programming language used, amongst others, by WordPress. This announcement raised concerns amongst…

    Read article →

  • Agency & ecosystem

    Farweb becomes a member of FeWeb

    A new milestone for Farweb: our WordPress agency in Brussels is now a member of FeWeb, the Belgian federation of web professionals.

    Read article →