Treat a security alert as a report of one event. Check the event type, site and timestamp in the WordPress dashboard you already use. A blocked sign-in, a successful sign-in and a changed file each offer different evidence and call for a different response.
The July 2016 Sucuri notice
In July 2016, Systm Web told hosting customers that it had added Sucuri Scanner to their sites. The notice explained that the change could generate email alerts and pointed readers to the plugin’s alert settings. It also identified unexpected file changes and repeated sign-in attempts as useful things to notice. Those details are preserved substantially in the Plugins archive capture. Menu names can change. Consult the current plugin listing for its documented capabilities.
The November 23, 2018 package announcement
One entry titled “iThemes Security Pro now included!” said the former host was adding the plugin to its packages. The November 23 listing preserves that commercial announcement. Plugin installation, settings and any particular customer’s entitlement remain unverified.
The November 24, 2018 customer notice
A second entry with the same title appeared at a different address. The November 24 excerpt said the provision was intended for existing and new customers. Both addresses now point to their own entries here. The standalone article bodies were unavailable in the sources checked.
Trace the alert to a decision
- Look up the underlying event. Find the dashboard entry for the alert time and site. Check whether a sign-in was refused or a session was created. Record the event type before changing any settings.
- Compare legitimate changes with the alert. Match a reported file change with your update and deployment records. For example, a changed plugin file just after a scheduled update calls for a different check from a change during a period when nobody was deploying.
- Escalate unexpected successful access or unexplained changes. Preserve the record and contact the site owner or host through your normal channel. Where there is evidence that account access may have been exposed, review access and revoke any unexpected sessions under your incident procedure.
- Review noisy notifications after you understand them. Keep the event record and make sure important alerts reach someone who can act. Confirm that urgent notifications stay visible before reducing email volume.
Record the site, timestamp and next action with the relevant person. The WordPress administration security handbook covers ongoing maintenance. See how to hand over support access for help involving another person.
Other items in the historical Plugins category
The four entries visible in the July 2019 category capture were the November 24 iThemes notice, the November 23 iThemes notice, the WordPress 4.9.6 announcement and the July 2016 Sucuri notice.
