WordPress website security

Not a service. Part of every website we build.

With us, website cybersecurity is built in, not an add-on: access, updates, a firewall with a scanner, and backups with restore testing.

Four layers · standard

Website cybersecurity is four layers, not one plugin.

A secure website is one where someone is responsible every day for access, updates, change detection and recovery after a failure — not just once, at launch. At Websky Studio, these four layers are part of every WordPress website and store we build or maintain. They don't appear on the invoice as a separate service, because without them a website isn't ready.

  1. 01

    Access control

    Named accounts, two-factor authentication or passkeys for every administrator, minimum privileges for contractors, and access revoked the day the work ends. This applies to the site dashboard, hosting, domain and ad accounts — because former contractors' accounts are now the most common way in. The basics are covered in how to secure WordPress.

  2. 02

    Updates and vulnerabilities

    Core, plugins, theme and PHP version on a fixed schedule; security releases automatically, bigger changes after testing on a staging copy. The July vulnerability in WordPress 7.0.2 showed that the response window is measured in hours — that's why we update safely, but without delay. We explain how a staging copy of your website works separately.

  3. 03

    Detection

    A web application firewall, a file scanner that compares against originals, alerts about new administrator accounts and file changes, checks on what Googlebot sees, and uptime monitoring. Hacks start quietly — with an account or a file, not fireworks — so the first signal has to reach a phone, not come from a customer.

  4. 04

    Restoration

    Backups following the 3-2-1 rule — one off the hosting server — and restore tests with timed results. A one-page incident plan: who calls whom, where the backups are, and when the 72-hour clock for reporting to UODO (the Polish data protection authority) starts. The only answer that works for failures, human error and ransomware alike is “we restore.”

Layer 03 in practice

What happens when something happens.

You judge security by the first hour of an incident. This is what it looks like on the sites we administer — whether the signal is a new account, a changed file or a report from outside.

Discussing the post-incident report with a client at a conference table, a compliance panel with a control list and timeline on the screen
24 h We go through the post-incident report with the owner within 24 hours: what happened, what we did, what we are changing.
  1. 0 minAlertA new account with elevated privileges, a change to core files, a login from a new country, or a drop in uptime — the alert goes to a dedicated inbox and phone.
  2. 15 minContainmentThe suspicious file goes to quarantine, the account is locked, sessions are invalidated, and we check whether the site serves Google's bots different content than it serves users.
  3. 1 hScopeLogs, accounts, cron jobs, database options, neighboring installations on the same hosting. Decision: surgical cleanup or restore from a backup taken before the infection.
  4. 24 hRecovery and reportThe site is clean, security keys are replaced, passwords are changed, and the owner gets a report. If personal data may have leaked — information about your obligations and the 72-hour clock.

For detection and cleanup we use WP Strażnik — our own WordPress plugin (scanner, firewall, quarantine, alerts), developed based on incidents from the sites we manage. It's one of the tools in this layer, not the whole layer.

No separate line on the invoice

What comes standard with every site — and what we don't promise.

Website security is not a package to pick from a price list. Below is exactly what every client gets when we build or maintain their site, and what we do not do — because an honest list has two columns.

Standard

  • Named accounts with 2FA or passkeys; at most two administrators
  • Updates on a cycle, security releases automatically, larger ones after a test on a copy
  • Firewall, file scanner, quarantine and change alerts — on every site and store
  • Off-host backups with a restore test; we know how long it takes
  • Uptime monitoring with an alert to your phone
  • Control over what Googlebot sees — cloaking detected before rankings drop
  • SPF, DKIM and DMARC for your domain — nobody will send mail „from you”
  • Forms with anti-spam protection and a GDPR-compliant privacy notice
  • Answers to security questionnaires from your clients — written down on a single page

What we do not do

  • Penetration testing of custom applications — we recommend teams that do only that
  • Formal compliance audits against the Polish NIS2 act, ISO 27001 or DORA — that is an auditor's job
  • 24/7 SOC monitoring with a shift team — we respond during working hours and within the on-call arrangement agreed in the contract
  • Legal advice — in case of a data breach or a dispute we point you to a law firm
  • A guarantee that a break-in will never happen — we guarantee it will be detected and that the site can be restored

Already have a site built somewhere else? We also implement the four layers on existing sites — as part of website maintenance, after a free audit that shows which of them are missing.

NIS2 · Polish cybersecurity act · supply chain

Your client has new obligations under the KSC Act? The answers are ready.

The amended Polish act on the national cybersecurity system has applied since 3 April 2026 and requires key and important entities to assess the security of their suppliers. A small company is rarely covered directly — but it does receive a questionnaire from a client who is. On the sites we build, those four questions have an answer from day one.

Whether your company is covered by the act and what to do before the October 3, 2026 registration deadline — read NIS2 and the KSC Act — is your company covered.

A store employee packing an order at a taping station, next to a laptop with the orders panel and a payment terminal
supplier A store or service provider working for a company covered by the act is a link in its supply chain — the questionnaire's questions apply to you too.
01

How do you protect client data?

Named access with 2FA, encrypted transmission, backups in two locations, no data exports circulating by e-mail.

02

How do you report incidents?

A reporting address, a response time and the first notice to the client within hours — because the client has 24 hours for an early warning to CSIRT.

03

How do you handle updates and vulnerabilities?

An update cycle, automatic security releases, monitoring of known vulnerabilities in the installed plugins and themes.

04

Who has access and how do you revoke it?

A list of accounts with roles, a quarterly review, access revoked on the last day of cooperation — including hosting and the registrar.

Questions and Answers

What site owners ask before they ask about the price.

Is website security included in the price?

Yes. Four layers — access, updates, detection, recovery — are part of every deployment and don't appear on the invoice as a separate line item. Maintaining them after launch (scheduled updates, tested backups, monitoring, alert response) falls under website administration, starting at PLN 250 per month.

How is this different from installing a security plugin?

A plugin is a tool of the third layer — it detects and blocks. It will not change a former contractor's passwords, will not update PHP and will not restore a store after a failure. A secure website is the four layers together; a plugin without the other three gives a sense of protection, not protection.

My site was built elsewhere. Can you secure it?

Yes. We start with a free audit that shows which layers are missing — most often 2FA, a backup restore test and change alerts. Then we roll them out as part of administration, without rebuilding the site.

What if the site has already been hacked?

We cut off access, isolate modified files and accounts, determine the scope, and either restore from a clean backup or clean up surgically; we replace keys and passwords, check what Googlebot sees, and hand over a report. If personal data may have leaked — we inform you about the 72-hour deadline for notifying UODO (the Polish data protection authority). We've described the step-by-step procedure in WordPress hacked — what now.

Does my small company fall under NIS2?

Most often not directly — the Polish act covers medium and large entities in 18 sectors. A small company meets it as a supplier to a client who is covered: through a security questionnaire and a contract annex. For our clients, the answers to the four typical questions from such questionnaires are written down from day one.

How do I check whether my website is secure?

Four questions: who has admin access and does everyone have 2FA; when was the last update and who tested it; who will get an alert about a new account or a file change; when did someone last restore a backup and how long did it take. If you don't know the answer to any of them, a free website audit will show it to you in numbers.

Studio in Poznań · clients from all over Poland

Website security starts with one question: who gets the alert at 2:14 a.m.?

If the answer is „I don't know”, let's book 30 minutes. We will show you what the four layers look like on your site — and what it takes to have them.