- [NEW] The Integrity Check shows your themes in their own section next to Core and Modules: your PrestaShop theme is verified there, and your custom themes are listed as not verified
- [NEW] Submit a custom theme from the Integrity Check so that its files are verified at the next checks, with the Pro plan
- [NEW] Set the time of the automatic Security Scanner and Integrity Check, or pause them, from the module configuration page, with the Pro plan
- [NEW] Choose the e-mail addresses that receive the Security Scanner and Integrity Check reports from the module configuration page, with the Pro plan
- Show and filter brute force and rate limit bans in Security Logs, and show every event on the dashboard under the same translated name as in Security Logs
- Fix several ways for a file name, a visited page address or a message from the Sentinel service to run code in your back office from the dashboard, the Security Scanner or the Integrity Check
- Fix an employee with only the View permission on the Integrity Check being able to read the files holding the shop's secrets, database dumps or backups left at the root of the shop
- Fix an employee with only the View permission on the Module Manager being able to change Sentinel's settings on PrestaShop 9
- Fix a detected attack that could get through when its log entry could not be recorded
- Fix the brute-force protection never banning when the security log could not be written
- Fix threat detection turning off on Pro shops when the Sentinel service was unreachable
- Fix the auto_prepend protection not activating on Apache when the module is installed or updated from the command line
- Fix large requests being able to fill the shop's disk through the security log
- Fix an employee being refused a back-office page by chance, and the visit logged as an attack
- Fix the Integrity Check showing a section as intact when one of its folders or themes could not be checked
- Fix unbanned addresses that could stay refused or be banned again too quickly; unbanning from the DDoS Protection or Brute-force Protection screen now only lifts that screen's ban
- Fix the Auto Prepend tab of Security Logs missing some requests, failing to open on busy days, or showing the wrong entry details
- Stop copying the Redis password from the DDoS Protection screen into a file on the server; an existing copy is removed the next time the settings are saved
- Minor fixes
Documentation
Consulter la documentation complète