In July 2018, Nuagerie updated its servers to Imunify360 3.4.1. The release combined maintenance fixes with the production release of Proactive Defense, a feature intended to identify potentially malicious behavior during PHP script execution.
Protection during application execution
The feature’s behaviour depends on its configuration. Availability does not mean that the same blocking mode is applied to every account.
Proactive Defense added a different perspective to server protection: examining what a script does while it runs. This complements file inspection and request filtering. It does not remove the need to maintain the website itself, protect administrator accounts or review a suspicious event in context.
The release also refined the information presented to users. Changes covered Proactive Defense event details, incident grouping and interface controls. Clearer event information helps distinguish the affected application and action when investigating a report.
Maintenance of the protection service
Other corrections addressed agent startup after an upgrade, malware-result access and parts of the scanning and backup-status interfaces. These were maintenance improvements to the security software and its reporting, rather than a change to a website’s content or business functions.
This update formed part of the maintenance of the hosting environment. Website owners should continue to keep their application, themes and extensions maintained. When a legitimate function appears to trigger a protection rule, provide the affected page, approximate time and steps to reproduce it to support. That context is more useful than disabling protection broadly.
Keep legitimate website functions working
A useful protection review considers both the security event and the work a visitor was trying to complete. For a form, account sign-in or checkout, our team can help relate the reported behaviour to the application and identify whether a focused adjustment or application correction needs review.
For a site hosted with Nuagerie, send your question through the client area. Mention the action that failed, whether it affects every attempt and any recent plugin or application change. This gives us a clearer starting point for helping restore the intended workflow while keeping the protection decision specific to the issue.
