Access review
Each account that can change the site, the host, the domain or the payment dashboard is listed with its owner and the date it was last used. Accounts of people who left are removed, and the administrators get a second sign-in step. You receive: the account list, and a record of what was removed and what was added.
Hardening
Unused plugins and themes are deleted, abandoned ones are replaced, file permissions are tightened and the dashboard file editor is turned off. Changes are tested on a staging copy and released with your approval. You receive: the change list, with a reason beside each line.
Firewall rules
Rules at the firewall in front of the site limit login attempts, block requests aimed at admin and checkout paths from places your customers are not, and challenge automated traffic. The rule set sits in an account in your name. You receive: the rule list, and what each rule is meant to stop.
Payment-page scripts
Each script that loads on a page where customers pay is named, tied to an owner and a purpose, and approved or removed. We ask your payment provider and acquirer which questionnaire applies to you. You receive: the script list, and the questions to bring to your acquirer.
Scans and alerts
The site is scanned for changed files and known flawed versions, and Search Console is connected so Google’s security notices reach a named person. Who is told, and how often each scan runs, is set in the written scope. You receive: the scan settings, and the names of the people alerted.
Recovery plan
A copy of the site is held off the server, restored to a clean location and checked, and the order of steps for a suspected break-in is written out with phone numbers and decision rights. You receive: the recovery record, and the incident steps in one document you can print.