WordPress security and hosting · For IT and security teams
SSO, patching on a clock,
backups and a named owner.
A marketing site becomes IT's problem when nobody owns it after launch. We build the site to your access and security requirements, HostLogic runs it under a written service level, and you get the documents your questionnaire asks for before the contract is signed.
What IT asks for
Eight controls, set up before launch.
Real-time and daily backups, stored off-site and independently of the hosting platform, with a 30-day minimum retention. A documented continuity plan with a four-business-hour recovery target, tested at least annually.
Managed WordPress on WP Cloud, built by Automattic, in Amsterdam. Each site runs in its own isolated container. Encrypted failover replicas are held under the platform's data processing agreement and EU standard contractual clauses.
Security headers and a content security policy set for the site, with a script allowlist so nothing loads that was not agreed. File editing in the admin is disabled.
Uptime and security monitoring 24/7. Critical issues found by monitoring are escalated at any hour. A critical issue has a one-business-hour response target and a four-hour resolution target, under a service level countersigned at onboarding.
Every update, restore and configuration change is logged against the site. You receive a monthly report of what was done and what needs a decision.
Where your firewall allowlists addresses, our engineers connect from one fixed address we control, so your allowlist holds one entry rather than a list of home IPs.
For the questionnaire
The documents, before the contract.
Most vendor questionnaires ask the same questions. These are the answers we provide, with the documents attached, so the security review does not hold up the project.
How it runs
Before launch, at launch, every week after.
Send the security section of your requirements as it is. We read it before the first call and come back with what we can meet, what needs a decision and what we would do differently.
Identity, headers, integrations and access are set up on staging and reviewed by your team against a checklist before anything goes live.
Your team signs off the pre-launch review. The accounts, the allowlist and the integration keys are recorded in the handover document.
Weekly staged updates, monitoring, backups and the monthly report, under the service level. One named owner for the site, with the escalation path in writing.
Straight answers
What security reviewers ask.
Yes. We connect WordPress to Okta or another SAML provider so editors sign in with their work accounts. Where SSO is not in scope, two-factor authentication is enforced for every user.
Production, the database and the backups are in Amsterdam, on WP Cloud. Encrypted failover replicas of the platform are held under its data processing agreement and the EU standard contractual clauses. We state this in every questionnaire rather than leave it to be found.
HostLogic reviews and stages updates weekly. WordPress core security releases are applied by the platform within hours of release. Where your policy sets a deadline for critical patches, we write it into the contract.
Monitoring raises the alert. A critical issue, such as an outage, a security breach or payments failing, has a one-hour response target at any time of day and a four-business-hour resolution target. Support hours are Monday to Friday, 9 to 6 Irish time; critical alerts from monitoring are escalated at any hour.
HostLogic itself holds no third-party certification. The data centres are SOC 2 Type 2 and ISO/IEC 27001 certified, and we provide the platform's reports with the questionnaire.
Yes. The site is a standard WordPress install with no lock-in to our hosting. If your policy requires it, we build to your environment and hand over the documentation at launch.
Access is role-based and per person. The handover document lists every account and integration key. When someone leaves, access is removed and the change is logged.
Yes, from one fixed address we control. Your allowlist holds that one entry. We never ask you to allowlist individual home connections.