Skip to content
Talk to us

Managed WordPress hosting and what the GDPR actually requires

Jack O'Connor· 19 min read· ·Updated

Managed WordPress hosting and what the GDPR actually requires, HostLogic

Most organisations buying managed WordPress hosting assume that paying for a managed service transfers the security burden to their provider. It does not. Under Article 32 of the GDPR (Regulation (EU) 2016/679), the data controller remains legally responsible for implementing appropriate technical and organisational security measures, regardless of who administers the underlying infrastructure.

For financial entities, charities, and Irish public bodies, the distinction has practical consequences. Choosing a managed WordPress host on price or feature list alone leaves Article 32 obligations unaddressed, and the Data Protection Commission has demonstrated a consistent willingness to hold controllers accountable when that gap becomes a breach.

This post examines what Article 32 actually requires, how European regulators have applied it across 90 documented decisions, and why standard managed hosting arrangements routinely fall short of the standard. It then sets out what a compliant managed WordPress hosting arrangement must include: documented security controls, a robust data processing agreement, incident response procedures, and monthly evidence the controller can retain and produce. If your organisation operates under regulatory scrutiny, the line between where managed hosting ends and legal accountability begins is worth establishing before an auditor draws it for you.

Article 32 puts the responsibility on the controller

Article 32 of the GDPR places the obligation to implement appropriate technical and organisational measures on the data controller. That obligation does not transfer when the controller procures infrastructure or services from a third party. The hosting vendor’s role, however sophisticated, does not absorb the controller’s responsibility.

The controller-processor distinction makes this concrete. When a managed WordPress hosting provider handles personal data on the controller’s behalf, it acts as a processor. The controller can delegate execution; it cannot delegate accountability. If a measure fails or goes undocumented, the controller answers to the Data Protection Commission, not the vendor.

That distinction carries a specific operational consequence: the controller must verify the processor’s measures. Using a processor leaves the controller responsible for ensuring those measures are appropriate and functioning, and verification is part of the obligation rather than good practice layered on top of it.

The GDPR goes further. Recital 83 and Article 32(1) require organisations to assess risk and implement measures that ensure a level of security appropriate to that risk, including the ability to restore the availability and access to personal data in a timely manner following a physical or technical incident, and a process for regularly testing, assessing and evaluating the effectiveness of those measures. A passive hosting arrangement that runs without producing tested, documented evidence does not satisfy that standard. The controls may be real; without evidence of testing, they are unverifiable and therefore insufficient.

For financial entities, charities, and Irish public bodies, the practical weight of this falls on a specific person: typically a compliance officer, operations director or board secretary who will face the DPC, a funder or a board if the arrangement fails. The marketing manager who selected the hosting package and the developer who configured the server both sit outside that line of accountability. It also runs wider than the server, because every analytics script and tracking integration on the site processes personal data and carries its own consent obligation under SI 336/2011 (the ePrivacy Regulations).

The question for any regulated organisation is whether the arrangement produces the evidence the controller needs to demonstrate compliance. Provider competence is a separate question, and most standard managed hosting arrangements answer only that one.

What Article 32 actually requires: beyond the server checklist

Understanding what the controller is accountable for means reading the text of Article 32 rather than the portion of it hosting providers choose to address.

Article 32 asks for technical and organisational measures, chosen after an assessment of risk. A hosting arrangement that delivers only server-level infrastructure covers part of the technical side and leaves the risk assessment and the organisational measures entirely with the controller, unaddressed and unevidenced.

Article 32(1)(b) of the GDPR specifies that measures must ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services, and Article 32(1)(c) requires the ability to restore the availability and access to personal data in a timely manner following a physical or technical incident. Availability is a statutory requirement in its own right, and backup infrastructure with no tested restoration procedure satisfies none of it.

Article 32(1)(d) requires a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures. As stated, that testing obligation applies equally whether controls are deployed in-house or by a managed processor.

Organisational measures are where most hosting arrangements leave the largest gap. Documented security policies, staff awareness procedures, and incident response plans fall within this category. No hosting provider deploys these on the controller’s behalf. If the controller has not produced them independently, they are absent entirely, regardless of how well the server is managed.

Risk proportionality compounds this for regulated sectors. Article 32 requires measures appropriate to the nature, scope, context, and purposes of processing, taking into account the risks of varying likelihood and severity for the rights and freedoms of natural persons. A financial entity or Irish public body processing sensitive personal data at scale faces a materially higher risk profile than a generic commercial website. Higher risk demands correspondingly more rigorous controls and, critically, more rigorous documentation.

How regulators have enforced Article 32: lessons from 90 decisions

Knowing what Article 32 requires is one thing; understanding how regulators have actually applied it in enforcement decisions is another. The EDPB’s One Stop Shop Case Digest on security of processing and data breach notification provides the clearest available answer. Published in January 2024 and covering 90 final decisions taken between January 2019 and June 2023 under Articles 32, 33 and 34, it is the most comprehensive analysis of how supervisory authorities across EU member states have identified and penalised non-compliance with Article 32.

The digest categorises violations across three breach types: malicious external attacks, insufficient company practices and systems, and human error. Two of those three categories describe organisational failures. Controllers who framed their defence around technical infrastructure, while leaving procedural and governance gaps unaddressed, consistently fared worse in enforcement outcomes.

For malicious external attacks, the EDPB identified nine sub-categories, including ransomware and credential compromise. The critical enforcement finding is what actually drew the penalty: preventive measures that were absent, untested or undocumented at the time of the incident. A successful attack, on its own, was never treated as proof of non-compliance. The absence of documented preventive controls was.

The preventive-versus-remedial distinction runs throughout the digest as the central enforcement axis. Controllers who had preventive controls in place but failed to detect an incident quickly received lighter findings than those who lacked preventive controls entirely. Article 32 is prospective, and the first thing it asks is what was in place before the breach.

The enforcement pattern also confirms that Article 32 is a continuous evidencing obligation that outlives any one configuration. Organisations unable to produce documentation of tested security measures at the point of breach were systematically found in violation, whatever may have been in place informally. If it was not documented, it did not count.

For Irish and EU regulated organisations, this body of decisions is directly instructive. The Data Protection Commission works within the same EDPB framework as the supervisory authorities whose decisions are recorded in the digest. The preventive-versus-remedial lens, the documentation standard, and the organisational-failure categories identified there all translate directly into how the DPC approaches breach investigations.

Why standard managed WordPress hosting fails the Article 32 standard

Most standard managed WordPress hosting providers deliver server administration. What they provide includes automated software updates, uptime monitoring, daily backups and firewall configuration, and these are operational tasks, competently executed. Governance is a separate layer, and it is the layer that produces the documented evidence Article 32 requires.

A feature list is not a compliance record. Knowing that automatic updates are enabled tells a controller nothing about whether a specific update was applied before a known vulnerability was actively exploited, or whether the application was tested for regressions after the update ran. The DPC, like any supervisory authority working within the EDPB framework, asks what was evidenced and when.

Backup infrastructure is a further example of the same problem. It satisfies the availability and resilience limb of Article 32 only if restoration has been tested and a recovery time objective is documented. Most managed WordPress hosting providers run backups reliably. Very few routinely test restoration or provide the controller with written confirmation that recovery within a defined timeframe is achievable. The capability exists; the evidence does not.

Incident response is the most consequential absence. Standard hosting arrangements typically include breach notification after the fact, with no documented response procedure written before one occurs. Without a written procedure specifying what the provider does, in what sequence, and within what timelines, a controller cannot approach the DPC’s 72-hour notification window under Article 33 with any confidence. The controller is accountable for that deadline regardless of what the provider was or was not doing.

Managed WordPress hosting and maintenance services marketed on uptime and page speed are optimised for a different outcome. A compliance officer evaluating a hosting arrangement is concerned with whether it produces retained evidence they can put in front of a regulator, a funder or a board. Server response times sit some way below that on the list.

The gap here is structural. Standard hosting is priced and positioned on features because that is what the general market buys, and accountability and documentation sit outside the product. For most clients that is a reasonable trade. For regulated organisations it means the compliance documentation burden sits entirely with the controller, and the gap usually surfaces at the point of an incident or an audit, when there is no time left to close it.

The principle underneath all of this is simple enough to state: execution without evidence does not constitute a compliant arrangement.

Sector risk profiles: financial entities, charities, and Irish public bodies

The structural gap identified in the previous section applies with particular force to three categories of organisation, each of which carries obligations that amplify what Article 32 alone requires.

Financial entities

Central Bank of Ireland-regulated firms, and financial entities within scope of DORA (Regulation (EU) 2022/2554), operate under a dual obligation. The GDPR Article 32 governs the security of personal data. DORA, which applies from 17 January 2025 under Article 64 of the regulation, imposes ICT risk management, incident classification and reporting, and digital operational resilience testing requirements on in-scope entities. Where a financial entity’s website processes client data or supports regulated activity, both instruments are engaged. That means documented continuity measures, tested recovery procedures, and evidence of both. Organisations should take their own legal advice on whether their operations fall within DORA’s scope. A standard hosting arrangement delivers none of this governance infrastructure. It provides infrastructure, and the record that satisfies the DPC and any applicable DORA obligations has to come from somewhere else.

Charities

Charitable status carries no exemption from the GDPR. A charity registered with the Charities Regulator and processing donor payment records, beneficiary case data, or volunteer personal information is a data controller with full Article 32 obligations. The DPC can enforce against charities as it would any other controller, and public loss of donor confidence compounds regulatory risk significantly. For a charity dependent on public trust and on retaining its charitable status, that reputational exposure can outlast regulatory proceedings by years.

Irish public bodies

Semi-state bodies, local authorities, and educational institutions face DPC enforcement without the commercial insulation available to private-sector controllers. Irish public bodies also face transparency and accountability obligations, including under the Freedom of Information Act 2014, that can compound breach consequences. A public body in breach of Article 32 has limited control over disclosure, and those obligations mean the full circumstances of an incident, and the remedial steps taken, may become matters of public record. For bodies operating under statutory mandates, that level of exposure makes a well-evidenced hosting arrangement a matter of organisational governance, not merely operational preference.

The hosting vendor’s singular position

Across all three sectors, the hosting vendor appears as one processor among many in a data map or DPIA. It is, however, uniquely consequential: it is the only processor whose technical controls govern the security of every web interaction involving personal data. That concentration of risk is the reason a security posture that stands up to vendor due diligence cannot be inferred from a feature list. For regulated organisations, a governed arrangement with monthly evidence output is the only service model that maps to the actual obligation.

What a compliant managed WordPress hosting arrangement must include

Given that risk profile, the minimum a compliant managed WordPress hosting arrangement must deliver is a documented governance structure with the following components.

A Data Processing Agreement that is specific to the hosting engagement. Under Article 28 of the GDPR, a DPA must identify the personal data processed through the website, the security measures applied, the processor’s obligations upon a breach, and every sub-processor in the chain. A generic privacy policy clause does not satisfy this. If a provider cannot supply a specific, signed DPA before contract execution, the arrangement is non-compliant before it begins. The scope of what a DPA must contain, and what regulated organisations should demand of that instrument specifically, is addressed separately below.

Written security controls documentation. The controller needs a structured record of the specific controls in place, the standards or guidance frameworks they align to, and the date each was last reviewed or tested. A page listing security as a feature gives a compliance officer nothing they can retain or produce. A dated controls register does.

A defined and tested incident response procedure. The procedure must specify how quickly the provider notifies the controller on detection, what evidence the provider will supply, including logs, scope of compromise, and affected data categories, and the escalation path from the provider’s technical team to the controller’s compliance function. Without this, the controller cannot reliably meet the DPC’s 72-hour notification window under Article 33, regardless of how quickly the provider acts.

Monthly evidence output the controller can retain. This means update logs showing dates of application for WordPress core, plugins, and themes; vulnerability scan results with remediation records; backup restoration test confirmations; and uptime and access logs. A compliance officer should be able to answer a regulator’s questions from that month’s file without contacting the provider.

Proactive vulnerability management for the WordPress environment specifically. WordPress core, plugin, and theme vulnerabilities are the primary attack surface for website-hosted personal data. Known vulnerabilities are often exploited soon after disclosure. The provider must evidence that patching runs ahead of exploitation.

Documented engagements for GDPR monitoring, cookie consent governance, and accessibility conformance. Where these are live obligations for the controller, each has to be a structured engagement that produces records the controller can retain, rather than a background configuration the provider manages informally. Accessibility obligations under SI 358/2020 (transposing Directive (EU) 2016/2102) apply to public sector bodies and are enforced separately from data protection obligations; they are mentioned here because they share the same evidence-production logic.

The data processing agreement: what regulated organisations must demand

The DPA is the legal instrument that makes a compliant hosting arrangement enforceable.

Article 28 of the GDPR requires a written contract between controller and processor. For a hosting provider, that means a DPA specific to the hosting engagement. A generic data protection clause buried in standard terms of service does not satisfy the requirement; the contract must reflect the actual processing relationship.

The scope of that contract matters. For a WordPress site, the DPA must identify what personal data flows through the hosting environment: contact form submissions, user authentication credentials, analytics data, and any third-party integrations that route personal data through the server. A DPA that names website data without specifying categories is too vague to be relied upon in an enforcement context.

Sub-processor disclosure is part of the contract. Most managed WordPress hosting runs on third-party cloud infrastructure. That infrastructure provider is a sub-processor, and the DPA must name it. The controller must also have a documented mechanism to object to sub-processor changes or seek assurance about sub-processor practices. A hosting provider who cannot confirm which cloud platform their infrastructure runs on, or who omits that platform from the DPA, leaves a material gap in the controller’s accountability chain.

The assistance obligation needs a mechanism behind it. A DPA that states the processor will assist the controller in meeting its Article 32 obligations is standard language. What matters is whether the arrangement actually delivers that assistance in a form the controller can use. A commitment with no mechanism attached, however clearly worded, does nothing at the point the controller needs it.

For regulated organisations, the DPA negotiation is a due diligence exercise and deserves the time one gives it. The controls recorded in the DPA are the controls the controller can point to when a regulator asks what was in place. If those controls are vague, absent, or unverifiable, the controller carries that exposure alone. What belongs in the DPA, beyond the hosting-specific security provisions described here, including standard processor obligations, sub-processor chains, and data subject rights assistance, is a subject that merits its own treatment rather than a repetition here.

Monthly evidence: what the controller must be able to produce

The assistance obligation is fulfilled through retained records. A compliant monthly evidence package contains the following.

Update log: every WordPress core, plugin, and theme update applied during the month, with the date of application. This allows a controller to establish whether a known vulnerability was patched before or after any incident.

Backup confirmation: evidence that scheduled backups completed, and at least periodic confirmation that a restoration test has been carried out. Backup infrastructure that has never been restored from is an assumption rather than a control.

Vulnerability summary: a record of any alerts raised during the month and the response taken, including the timeline from alert to resolution.

Access control records are the category most frequently absent from standard managed hosting arrangements, and they are directly material to Article 32’s confidentiality requirement. The controller should be able to produce a log showing who held administrative access to the website environment during any given period, and when that access was last reviewed or revoked. Stale credentials and unrevoked access are a recognised confidentiality risk.

Cookie consent and data transfer records constitute a separate evidencing obligation under SI 336/2011. Where the website uses third-party scripts or analytics that constitute processing under the GDPR, the controller needs documented confirmation that the consent mechanism is functioning correctly and that any restricted data transfers, for example to processors outside the EEA, are covered by an appropriate transfer mechanism under Chapter V of the GDPR.

The practical test is simple. A compliance officer should be able to open a month’s evidence file and answer five questions without contacting the hosting provider. Were updates applied? Was the site secure? Were backups tested? Was access controlled? Were consent records functioning? If any of those requires a phone call, the arrangement is falling short of what Article 32 demands.

How to evaluate a managed WordPress hosting provider against Article 32

Knowing what good evidence looks like is only half the task. The other half is assessing whether a prospective provider will actually deliver it. These questions will tell you what you need to know before signing anything.

Request the DPA immediately. Ask whether the provider can supply a Data Processing Agreement specific to the hosting engagement, and read what it actually commits them to. A generic privacy policy is not a substitute. The DPA is the contractual instrument through which Article 32 obligations become enforceable against the processor.

Establish what monthly evidence you receive. Ask what the controller actually receives each month, in what format, and whether it is sufficient to constitute a retained compliance record. A provider who describes evidence reporting only in vague terms does not deliver governed managed WordPress hosting.

Test incident response specifically. Ask what the documented procedure is, what notification timeline the controller receives, and what evidence the provider will supply to support a DPC notification within 72 hours under Article 33. The provider should be able to describe a written procedure rather than improvise one in response to the question.

Verify sub-processor transparency. The provider should name the infrastructure layer, confirm data residency within the EEA or an adequacy-covered jurisdiction under Article 45 of the GDPR, and explain the mechanism by which they notify the controller of sub-processor changes. A reference to secure cloud infrastructure without naming the platform is not an answer.

Assess sector familiarity directly. A provider without prior experience serving financial entities, charities, or Irish public bodies will not anticipate the evidence formats those sectors require. Generic GDPR attestations do not satisfy sector-specific regulatory expectations.

The GDPR requires a process for regularly testing, assessing and evaluating the effectiveness of measures, as stated in Article 32(1)(d). A provider’s answer on monthly evidence is a direct test of whether they can support that obligation in practice.

HostLogic is an Automattic for Agencies Pro Partner, and its care plans cover managed WordPress hosting and maintenance with a monthly report. Accessibility audit, remediation and continuous accessibility monitoring are priced and scoped separately, each producing its own documented evidence output.

Conclusion: defining ‘managed’ by what the regulator requires

The evaluation questions in the preceding section reduce to a single test: does the arrangement produce evidence, or does it merely perform tasks? That distinction is the whole of Article 32’s practical demand on controllers.

Security responsibility under the GDPR cannot be outsourced. It can only be evidenced. A controller who cannot produce documentation of tested measures at the time of an incident will be found in breach regardless of what their hosting provider was doing in the background. The decisions reviewed in the EDPB One Stop Shop Case Digest on security of processing and data breach notification, published by the EDPB in January 2024 and covering final decisions from January 2019 to June 2023, confirm a consistent standard: documentation is the substance of compliance rather than a by-product of it.

For Irish and EU regulated organisations, managed WordPress hosting must be defined by what the provider evidences. A provider who applies updates, monitors uptime, and manages backups is performing execution. A provider who delivers monthly retained records, a tested incident response procedure, a specific Data Processing Agreement, and documented security controls is performing governance. Only the latter arrangement addresses what Article 32 actually requires.

The evaluation standard follows directly. If the arrangement does not produce those four outputs, the controller has delegated execution and retained all the risk. A regulator, a board or an auditor will read that as an unmanaged arrangement carrying a managed price.

Organisations that have not reviewed their hosting arrangement against this standard should do so before the next contract renewal or audit cycle. A review that happens after an incident becomes part of the evidence of the gap.

The final point is the most important one to carry forward. A compliant managed WordPress hosting arrangement is the minimum standard Article 32 requires, from the moment personal data is processed through a website. For financial entities, charities, and Irish public bodies, that moment is every contact form submission, every log-in, every analytics event. The obligation is already present. The question is only whether the arrangement evidences it.

Share this article

See exactly how your WordPress site is performing

Get a free HostLogic site audit covering Core Web Vitals, security posture, infrastructure and a maintenance gap analysis. Written report within 3 working days. No obligation, no sales pitch.