Technical summary
How does Enhanced Rate Limiting 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 → Hardening / Configurations. 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 |
|---|---|---|---|
hardening.outbound_public_rate_limit |
10 | The shipped value of 10 is the current baseline threshold or capacity. It is intentionally finite so the control can provide useful protection or bounded resource use without starting at an extreme. | For abuse/rate thresholds, a lower number is generally more aggressive and can stop attacks sooner but may affect legitimate bursts; a higher number is more tolerant but allows more activity before intervention. Change incrementally and validate against logs. |
hardening.outbound_public_rate_limit_max |
Maximum: 300 | 300 is the current code-enforced maximum/capacity boundary for this control, not a normal operating default. | Do not treat this cap as a target. Operate below it unless the legitimate site requirement needs more capacity; reaching the cap means the current implementation will clamp, truncate, stop adding rows, or reject additional input depending on the control. |
hardening.outbound_public_rate_limit_min |
Minimum: 1 | 1 is the current code-enforced minimum boundary, not a recommended default. Values below it are clamped or rejected by the current save path. | Do not tune below this boundary. Adjust the corresponding primary setting at or above this minimum and validate legitimate traffic/workload. |
hardening.registration_rate_limit_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. |
hardening.wp_cron_rate_limit |
10 | The shipped value of 10 is the current baseline threshold or capacity. It is intentionally finite so the control can provide useful protection or bounded resource use without starting at an extreme. | For abuse/rate thresholds, a lower number is generally more aggressive and can stop attacks sooner but may affect legitimate bursts; a higher number is more tolerant but allows more activity before intervention. Change incrementally and validate against logs. |
hardening.wp_cron_rate_limit_max |
Maximum: 120 | 120 is the current code-enforced maximum/capacity boundary for this control, not a normal operating default. | Do not treat this cap as a target. Operate below it unless the legitimate site requirement needs more capacity; reaching the cap means the current implementation will clamp, truncate, stop adding rows, or reject additional input depending on the control. |
hardening.wp_cron_rate_limit_min |
Minimum: 1 | 1 is the current code-enforced minimum boundary, not a recommended default. Values below it are clamped or rejected by the current save path. | Do not tune below this boundary. Adjust the corresponding primary setting at or above this minimum and validate legitimate traffic/workload. |
login_guard.password_reset_rate_limit_enabled |
1 | 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
Apply hardening incrementally and verify WordPress core plus active plugin/theme workflows after each consequential change. A security control that silently breaks administrator recovery or a business-critical flow should be narrowed, not blindly strengthened.
Technical keywords
Aegisify Shield Security, 7.4.5, abuse, ddos, enhanced, limit, limiting, rate, threshold, hardening, outbound_public_rate_limit, outbound_public_rate_limit_max, outbound_public_rate_limit_min, registration_rate_limit_enabled, wp_cron_rate_limit, wp_cron_rate_limit_max
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.