Guide / 22 November 2026
Online shop security checklist, area by area
A secure online shop means an up-to-date platform and plugins, admin accounts with two-step sign-in, as little outside code on the payment page as possible, backups you have restored at least once, and customer data kept only as long as needed. The list below helps you check each area in turn.
Start with what automated attackers try first: old versions of the platform and plugins, weak admin passwords and files left on the server. Then look at the payment page and outside scripts, backups and customer data. Tick each point below and note anything you are not sure about: that is usually where the problem is.
1. Platform, theme and plugins
Whether the shop runs on WooCommerce, PrestaShop, OpenCart, Magento or a platform of its own, many compromises start with a published weakness that was never patched.
- The platform is on a version that still receives security updates.
- The theme and every plugin are up to date and come from official sources, not "free" copies of paid plugins.
- Disabled plugins and ones you no longer use are deleted, not just switched off.
- Someone follows the security announcements for the plugins you use and knows who applies the updates.
- Updates are tested on a copy of the shop first, if you have one.
2. Admin accounts
- Every person has their own account; nobody shares a common "admin" login.
- All accounts with admin rights use two-step sign-in (2FA).
- Accounts belonging to former staff, the agency that built the site and suppliers you no longer work with are deleted.
- Each account has only the rights it needs: someone processing orders does not need to install plugins.
- The sign-in page limits repeated attempts.
- Just as important: the hosting account, the server control panel, the domain registrar account and the administrator's email also use 2FA.
3. The payment page and outside scripts
The payment page is the target of skimming attacks: someone inserts a script that copies the card details the customer types in. The script can get there through a compromised plugin or through an outside service the shop loads code from.
- The basket and checkout pages load as few outside scripts as possible. Analytics, chat widgets and advertising usually have no business there.
- For every script that remains, you know who supplies it and why it is needed.
- A Content-Security-Policy limits where the page may load code from.
- Card payments are handled by a payment provider, through its own page or form. That way the shop never receives or stores full card details, which greatly reduces what you have to protect yourself.
- Check from time to time that the payment page looks and behaves as it did yesterday; an unexpected change is worth looking into.
4. Backups and restore
- Files and the database are backed up automatically, as often as your daily order volume calls for.
- At least one copy is kept somewhere other than the shop server, where an attacker who reaches the server cannot delete it.
- You have restored the shop from a backup at least once and know how long it takes.
- Backups are protected: they contain every customer's data.
5. Exported files and old backups left on the server
An easy problem to overlook is a file that should never be public: an order export, an archive of the site, a database copy made "just for the move". Automated scanners try file names like these every day.
- The site's public folder holds no .zip, .sql, .bak or .tar.gz files and no CSV exports.
- Export and backup plugins do not save their files in a folder reachable from the internet.
- Configuration files and code version folders (for example .git) cannot be opened from a browser.
- Test sites and old copies of the shop on subdomains are switched off or password protected.
6. Customer data and GDPR
Article 32 of Regulation (EU) 2016/679 (GDPR) requires appropriate technical and organisational measures to keep personal data secure, including encryption, the ability to restore access to data and regular testing of those measures. Article 33 requires a personal data breach to be reported to the supervisory authority within 72 hours of becoming aware of it. In Romania that authority is ANSPDCP; elsewhere in the EU it is your national data protection authority.
- Keep only the data you need, and delete old accounts and orders in line with your retention policy.
- Know where customer data lives: in the shop, in exports, in the invoicing app, in the CRM, in the newsletter platform.
- Write down, briefly, who decides and who reports to the authority if an incident happens, so no time is lost when it does.
This is a technical summary, not legal advice.
7. The shop's email
Customers receive order confirmations, invoices and password resets from the shop. If the domain has no correctly configured SPF, DKIM and DMARC, anyone can send messages that appear to come from the shop. The steps are explained in the SPF, DKIM and DMARC guide. Remember to add to SPF the service the shop uses for its automatic emails.
8. Hosting and HTTPS
- The whole shop loads over HTTPS, and http:// addresses redirect to https:// automatically.
- The certificate renews automatically, and someone gets a warning if renewal fails.
- Only the ports that are needed are open on the server; the database and admin panels cannot be reached directly from the internet.
- The version of PHP, or whichever language the shop uses, still receives security updates.
- You know what the hosting company looks after and what remains your responsibility.
9. Monitoring
- You get an alert when a new admin account appears or when the shop's files change.
- Server and shop logs are kept long enough to work out what happened.
- Someone keeps track of when the domain and certificate expire.
- Now and then you check what the internet can see about the shop: subdomains, open ports, public files.
When an audit is worth it
An outside-in audit makes sense when you have launched the shop or moved it to a new server, after a big change of platform or plugins, when you are not sure what the agency that built it left behind, or simply when it has never been checked. The website and shop security audit looks in particular at admin and account pages, payment and delivery plugins, outside scripts on the payment page and export files left on the server. You receive evidence and an ordered fix plan, and one retest within 30 days is included.
For a first signal, the free check shows in seconds the state of HTTPS, security headers and the domain's SPF, DMARC and DKIM records.
Last updated: 22 November 2026.