Store security checklist
This page is for store owners and managers who are responsible for their store's security but are not security specialists. It turns the project's hardening advice into a checklist for a store, says who usually does each item, and links to the detailed page. Hand it to your host or partner and ask them to confirm each line.
Note
These are basics, not legal advice. Card security, data protection and consumer law obligations depend on where you sell and on your contracts. Read the rules that apply to you and ask your lawyer, data protection officer or payment provider.
Contents
- Why a store is a target
- Accounts and sign-in
- Shop permissions
- Payments
- The site and the server
- Updates
- Backups
- Watching
- Customer data
- If something happens
Why a store is a target
A store holds customer names, addresses and order histories, and it can change prices and order statuses. Attackers look for weak administrator passwords, outdated software and payment steps they can bypass. The project's view of the threats is in Security hardening.
Accounts and sign-in
| Check | Who | Read |
|---|---|---|
| The installation's initial administrator password has been changed | Host or partner | Change the admin password |
| Each person has their own account; nobody shares one | Owner | Security hardening |
| Two-step sign-in is required for administrators and shop staff | Host or partner | Two-factor login, sevenx_authentication_2fa |
| Accounts of people who left are disabled the same day | Owner | Access reviews |
| The administration runs on its own host and is restricted | Host | Restricting the administration |
Shop permissions
The shop's functions are buy, administrate, setup, edit_status and setstatus (kernel/shop/module.php).
- To do: Visitors and customers have only
shop/buy. - To do: Order handlers have
shop/administrateandshop/setstatus, limited byFromStatusandToStatuswhere that fits (Orders and order statuses). - To do: Only the owner or accountant has
shop/setup(VAT, currencies, discounts). - To do: Editors who maintain products have content permissions only on the product folders.
- To do: Roles are reviewed twice a year (Access reviews).
Payments
- To do: A payment step is on checkout; the Store dashboard does not warn "no payment step" (Store dashboard and reports).
- To do: A redirect gateway is used where possible, so card data never reaches your server (Card payments and PCI basics).
- To do: With ezauthorize: card data storage reviewed by a developer before launch (same page).
- To do: Payment notifications are checked against amount and currency, as ezpaypal does (PayPal payments).
- To do: Provider test mode and sandbox addresses removed on launch day.
- To do: Secrets (gateway keys, the receipt secret) live in override files, never in shipped files or in version control (Environment settings and secrets).
The site and the server
From the project's hardening checklist (Security hardening):
- To do: HTTPS everywhere, with HSTS and secure cookies (TLS and HTTPS).
- To do:
ezformtokenactive, so forms carry a per-session token against cross-site request forgery. - To do: Content Security Policy enforced, first on the administration, then on the sites (Content Security Policy).
- To do: Debug output off and PHP errors not displayed.
- To do: The installation wizard cannot run on the installed site.
- To do: Code read-only for the web server's user.
- To do: The request shield running in front (Setup > Request shield; Request shield) and request rules decided (Request rules).
Updates
- To do: Someone follows Exponential's releases and applies security fixes. Exponential 6.0 is the maintained line, and fixes are published with the next 6.0.x release (SECURITY.md).
- To do: Extensions (including payment gateways) are updated with the system.
- To do: Updates are tested on a copy before the live store (Upgrades without surprises).
Backups
- To do: The database is backed up daily at least; orders live there.
- To do: Backups are kept off the server and protected, since they contain customer data.
- To do: A restore has been tested (Backups that restore, Backups and restores).
Watching
- To do: The audit trail is on (it is by default) and someone reads it. It records orders, payments (never card data),
VAT, currencies and discounts in its
commercecategory (Audit trail). - To do: Audit alerts reach a person, and the trail is forwarded off the machine (hardening checklist).
- To do: Logs are read weekly (Log viewer).
Customer data
- To do: Only staff who need it can open the customer list and orders.
- To do: Order records are kept as long as your bookkeeping requires, and no longer (Data retention and deletion).
- To do: Marketing mail only with consent (Opt-in and consent).
- To do: Your privacy notice describes what the store stores (GDPR basics).
If something happens
- Follow the host's runbook for a compromised site (Compromised site).
- Report a vulnerability in Exponential privately to the address in SECURITY.md, not in a public issue.
- Tell your payment provider at once if payment data may be involved.
- Write down what happened (Incident response for small teams).
Related pages
- Security hardening
- Security basics for businesses
- Store launch checklist
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.