How do I check the security of my online store?
Six checks for access, updates, backups and integrations, followed by a practical decision on maintenance and security support.
AI-generated image- 1Quick answer
- 2Key takeaways
- 3What information do I need for an initial assessment?
- 4Which six areas should I check now?
- 5How does this differ between PrestaShop, Shopware and Shopify?
- 6What should I do with the findings?
- 7Do I need an assessment, maintenance, Security or Protect?
- 8What if I already suspect an attack?
- 9Sources & further reading
- 10Cite this article
- 11Authors & technical review
Quick answer
Start with an inventory of your systems and their owners. Then review access, updates, backups, checkout, integrations and alerts using documented evidence. A successful order alone does not prove security. Unclear or critical findings need a professional assessment; this checklist does not replace a security audit.
Your store accepts orders, payment methods work and your hosting provider reports no outage. Those are useful signs of normal operation. They do not establish whether access, extensions and backups have been properly reviewed.
At sjmedia, we therefore start with an inventory. Retailers first need to know which systems support their store, who maintains them and which checks are documented. Our recent blog article on AI-assisted attacks explains the news context. This guide focuses on reviewing your own operation.
Key takeaways
- Record your platform and version, hosting, installed modules or apps and connected services.
- With PrestaShop, we can examine the platform version, modules, access and integrations directly.
- Assign an owner to every finding and record the next action.
- At sjmedia, we first establish the scope of the review.
What information do I need for an initial assessment?
Record your platform and version, hosting, installed modules or apps and connected services. These may include Odoo or another ERP, payment providers and advertising accounts. Identify a technical contact for each system.
Add the latest update record, a list of authorised users and your backup documentation. Do not put passwords or API keys in this inventory. Record the responsible person and the agreed secure access process instead. Missing documentation is itself a finding.
Which six areas should I check now?
- Access: Request a list of active administrators, agency accounts and app permissions. Do former employees or providers still have access? Check where two-factor authentication is enabled and who manages recovery access.
- Updates: Establish the versions of your store, extensions and self-managed server components. Compare them with vendor information and security advisories. Each relevant outstanding update needs an owner, an urgency assessment and a planned implementation date.
- Backups: Ask for the latest successful backup, separately controlled access and the most recent restoration test. Having a backup does not prove that it can restart your store. Restore testing belongs in an isolated test environment.
- Checkout: Identify extensions and external scripts included on payment pages. Who reviews unexpected changes? Separate security checks from functional testing: a checkout that remains available may still have been tampered with.
- Integrations: Document connections to your ERP, marketplaces and other services. Together with your support provider, review required read and write permissions, ownership and the response to a compromised key. Successful data synchronisation alone is not proof of security.
- Alerts: Ask which events are monitored, where notifications go and who assesses them. Verify the notification path with an agreed test alert. Continuous technical monitoring does not automatically include a staffed round-the-clock response service.
- Define requirements
- Compare platforms
- Test workflows
- Plan the next step
How does this differ between PrestaShop, Shopware and Shopify?
With PrestaShop, we can examine the platform version, modules, access and integrations directly. That control is useful, but it requires an accurate inventory and clear responsibilities. Updating the core does not automatically make an old module safe. Our separate guide explains how to update PrestaShop safely.
For self-hosted Shopware, the review likewise covers the application, extensions and hosting. Built-in safeguards such as rate limits provide a foundation; effective configuration and ongoing maintenance still matter. Our Shopware 6 update guide covers the actual update process.
With Shopify, the provider operates the platform. Retailers still need to review user accounts, app access, themes and external integrations. Sign-in security can be checked in user and account settings; available requirements depend on permissions and the plan. Updating the underlying server is not the retailer's task here.
What should I do with the findings?
Assign an owner to every finding and record the next action. An applicable, exploitable vulnerability needs a different level of urgency from incomplete documentation. Critical indicators should receive a technical assessment rather than wait for the next routine maintenance appointment.
For example, a backup may run every night without any documented restoration. The next task is to restore a suitable backup in isolation and check the result. Additional monitoring alone does not answer that question. This is an illustrative example, not a customer case study.
Do I need an assessment, maintenance, Security or Protect?
At sjmedia, we first establish the scope of the review. Our technical check provides an overview of the version, modules and loading speed. For a documented security assessment, the PrestaShop Security Audit offers an agreed scope; remediation and certification are not included.
For ongoing support, we distinguish between Security, without routine platform and module maintenance, and Protect, which includes that maintenance. The PrestaShop packages also differ in security scope: a restoration test or an API security review is not automatically included in every tier. For Shopware and Shopify, we agree the work according to the platform and operating model.
Our maintenance and security page sets out current services and package boundaries. Setup, major version upgrades, security clean-up and emergency standby need separate consideration. The inventory should lead to a reasoned recommendation: a one-off improvement, ongoing support or a more detailed review first.
What if I already suspect an attack?
Unexpected administrator accounts, altered payment pages or suspicious redirects take you beyond routine prevention. Contact the responsible technical support team to contain and investigate the issue, and preserve available logs. Avoid deleting files indiscriminately or treating a suspicious system state as a new backup baseline. If office devices or ransomware are involved, bring in internal IT or specialist incident-response support. This checklist does not replace an investigation into an active incident.
Sources & further reading
Cite this article
Jochen Schmid (sjmedia GmbH, Kuppenheim): How do I check the security of my online store?. 21 Nov 2026. https://www.sjmedia-consulting.de/en/wissen/shopsysteme/sicherheit-onlineshop-pruefen
Author & technical review
Related to this topic.
Questions about this topic? Let’s talk about it.
I’ll listen to your situation and discuss which next steps suit your store.



