PrestaShop back-office access control and brute-force protection

To protect the PrestaShop back office, you allow only your team’s IP addresses and stop repeated login attempts. Sentinel Free restricts the back office, login page included, to a list of IPv4 and IPv6 addresses or CIDR ranges, and Sentinel Pro automatically bans the addresses behind repeated failed logins.

Free & ProIncluded in Free, extended with Pro

Updated November 9, 2026

Restrict administration to your team.

IP access control protects the back office, including the login page. Pro adds automatic bans for sources of repeated failed logins.

  • Free: IPv4, IPv6 and CIDR allowlists
  • Free: redirect unauthorized visitors to the storefront 404 page
  • Pro: configurable attempt threshold, time window and ban duration
  • Pro: ban management, trusted IPs shared with anti-DDoS and a blacklist

Brute-force protection targets the back office. Customers sharing a banned IP can still access the storefront.

The risk: a login page anyone can reach

Out of the box, the PrestaShop back-office login page answers any address on the internet. A bot can try passwords over and over: that is a brute-force attack. One employee account with a weak password is then enough to open up the store’s orders, customers and modules.

IP allowlist (Free)

Sentinel Free restricts the back office to a list of allowed addresses: IPv4 or IPv6 addresses, or CIDR ranges (a block of addresses, such as an office network), each with an optional comment.

  • The address is checked on every back-office request, login page included, before anything runs. Credentials sent from a refused address are never even looked at.
  • An unauthorized visitor is redirected to the store’s 404 page: no login form, no error message, nothing to show that a back office exists at that URL.
  • Every blocked access is written to the security logs, with the IP address, the requested URL and the browser.
  • The storefront is never affected: customers browse and order as usual.

Safeguards keep you from locking yourself out: Sentinel refuses to save an active list that does not include your current address, an empty list blocks no one, and the command line is never blocked. The same tab offers a free rule that deactivates employee accounts unused for a number of days you choose (90 by default), without ever deleting an account.

Brute-force protection (Pro)

Sentinel Pro counts failed back-office logins per IP address. Past a threshold within a given time window, the address is banned: by default, 5 failures within 15 minutes earn a one-hour ban. A banned address gets a 403 error on the whole back office, while the storefront stays open. Bans expire on their own.

The Sentinel > Brute-force Protection page lists active bans, lets you lift one in a click and shows the email addresses tried from each IP. A blacklist bans an address permanently. Trusted IPs, shared with anti-DDoS and the web application firewall, are never counted or banned.

Setting it up

  1. If the store sits behind Cloudflare, a CDN or a reverse proxy, declare it first in Sentinel > Configuration, on the General tab.
  2. On the Access control tab, add your addresses with Add my current IP, turn the whitelist on and save.
  3. With Pro, adjust the threshold, time window and ban duration on the Brute force tab, and add your fixed addresses to the trusted IPs.

What these protections do not replace

IP filtering assumes stable addresses: if yours changes, use a CIDR range or a VPN with a fixed address. Brute-force protection slows down password guessing, but it does not make a weak password safe. To protect the accounts themselves, turn on two-factor authentication, which is free as well. See Free or Pro for the editions: Pro costs €29.90 excl. tax per month per installation, with no commitment.

FAQ

Questions about
this feature.

All questions
What happens if my IP address changes?

If your new address is not on the list, the back office sends you to the store’s 404 page. If your internet provider does not guarantee a fixed IP, use a CIDR range rather than a single address. The command line is never blocked, and the documentation explains how to turn the list off from the database, which your host can do for you.

Can my customers be blocked?

No. The allowlist only applies to the back office, and a brute-force ban only blocks the back office: a customer who shares a banned address can still browse and order.

My store is behind Cloudflare. Does it work?

Yes, as long as you declare the proxy on the General tab of Sentinel’s settings, which takes one click for Cloudflare. Without it, every visitor arrives with the proxy’s address, and allowing your own address would let everyone in.

What are the default brute-force settings?

The protection is on by default: 5 failed logins within 15 minutes lead to a one-hour ban. All three values can be changed, and addresses listed as trusted IPs are never banned.

Start by securing your access

Install Sentinel.
2FA is already included.

Download for free

No subscription for the Free edition · PrestaShop 1.7.7 – 9.2

How to install