Technical summary
How does Email Alerts on Lockouts work in Aegisify Shield Security, and what should administrators verify? protects authentication and account-lifecycle flows through rate limits, unknown-username handling, registration defenses, administrator controls, lockouts, and recovery-aware enforcement. This article is grounded in the supplied Aegisify Shield Security 7.4.5 plugin package. It documents current behavior and defaults rather than relying on older FAQ wording.
Where administrators configure or verify it
Primary wp-admin path: wp-admin → Aegisify Shield → Login Guard. Exact controls can be distributed across the related tab/page when the feature is composed of multiple engines.
Current 7.4.5 defaults and related controls
The table below lists settings in the supplied current source that are directly related to this topic. The current default/bound/status shown is code-derived. Where the product does not define a named Medium preset, the shipped default is documented as the baseline operating point rather than inventing a value.
| Setting | Current default / bound / status | Why this default | How to tune safely |
|---|---|---|---|
file_integrity.email_alert_threshold |
none | “none” is the exact shipped value in the current version. It is preserved as the baseline because the plugin code defines it as the default rather than deriving it from the old FAQ text. | Keep the shipped value unless a documented site requirement calls for a different mode or identifier. Validate the change in the feature’s logs/status view and roll back if behavior becomes less reliable. |
file_monitor.email_recipients |
(blank / site-specific) | Blank or empty by default because this value depends on the site, organization, route, identity source, recipient, API credential, or exception policy. Configure it only with verified site-specific data. | Supply only validated site-specific values. Leaving it blank/empty means no custom value, exception, recipient, credential, route, or policy has been asserted by default. |
db_tools.growth_email |
(blank / site-specific) | Blank or empty by default because this value depends on the site, organization, route, identity source, recipient, API credential, or exception policy. Configure it only with verified site-specific data. | Supply only validated site-specific values. Leaving it blank/empty means no custom value, exception, recipient, credential, route, or policy has been asserted by default. |
db_tools.growth_email_addresses |
(blank / site-specific) | Blank or empty by default because this value depends on the site, organization, route, identity source, recipient, API credential, or exception policy. Configure it only with verified site-specific data. | Supply only validated site-specific values. Leaving it blank/empty means no custom value, exception, recipient, credential, route, or policy has been asserted by default. |
file_monitor.email_events |
[] | Blank or empty by default because this value depends on the site, organization, route, identity source, recipient, API credential, or exception policy. Configure it only with verified site-specific data. | Supply only validated site-specific values. Leaving it blank/empty means no custom value, exception, recipient, credential, route, or policy has been asserted by default. |
file_monitor.email_mode |
instant | “instant” is the exact shipped value in the current version. It is preserved as the baseline because the plugin code defines it as the default rather than deriving it from the old FAQ text. | Keep the shipped value unless a documented site requirement calls for a different mode or identifier. Validate the change in the feature’s logs/status view and roll back if behavior becomes less reliable. |
login_guard.administrator_owner_email |
(blank / site-specific) | Blank or empty by default because this value depends on the site, organization, route, identity source, recipient, API credential, or exception policy. Configure it only with verified site-specific data. | Supply only validated site-specific values. Leaving it blank/empty means no custom value, exception, recipient, credential, route, or policy has been asserted by default. |
hardening.account_forms_alerts_enabled |
on | Enabled in the shipped baseline because the control provides broadly useful visibility, validation, compatibility, or protection without requiring a site-specific value. | ON activates the behavior; OFF removes that specific behavior. Use OFF only when the control is intentionally unnecessary, another trusted layer owns the function, or a compatibility investigation proves the control is involved. Re-enable after testing when protection is still required. |
Adjustment strategy
Change one control at a time, save it through the product UI, reproduce the legitimate and malicious/test flow, and review the product log/status surface. For enforcement controls, use Monitor/Observe first when normal behavior is uncertain; move to Block only after the signal is reliable. For thresholds, do not jump directly from the default to an extreme unless an active incident requires emergency containment and a recovery path exists.
Operational guidance
For WooCommerce, membership, social-login, REST, AJAX, or custom-registration sites, test legitimate account creation and recovery flows before increasing enforcement. Protect the abuse path without blocking normal WordPress/plugin account workflows, and keep an administrator recovery path.
Technical keywords
Aegisify Shield Security, 7.4.5, alert, alerts, email, lockouts, notification, recipient, file_integrity, email_alert_threshold, file_monitor, email_recipients, db_tools, growth_email, growth_email_addresses, email_events
Source baseline
Verified package: Aegisify Shield Security 7.4.5. Primary source files: includes/configuration/class-as-configuration-schema.php; includes/modules/class-as-module-login-guard.php; includes/modules/login_guard/class-as-login-guard-user-protection.php; includes/admin_pages/hardening/class-as-page-hardening-tab-endpoint-protection.php; includes/modules/class-as-module-hardening.php; includes/admin_pages/class-as-page-db-tools.php. If a future plugin version changes these settings, support should re-read the installed version rather than carry these defaults forward automatically.