Technical summary
How does Attack Story Deep Dive Reports work in Aegisify WAF, and what should administrators verify? provides security telemetry and forensic context for inspected, logged, challenged, rate-limited, blocked, and operational events across WAF subsystems. This article is grounded in the supplied Aegisify WAF 1.20.13 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 WAF → Logs. Exact controls can be distributed across the related tab/page when the feature is composed of multiple engines.
Current 1.20.13 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 |
|---|---|---|---|
logs.attack_story_top_items |
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. | Treat this numeric value as the shipped baseline. Adjust one step at a time, document the reason, and verify the operational effect before making the setting more extreme. |
logs.attack_story_window_hours |
24 | The shipped value of 24 is the current timing baseline used to balance responsiveness, user impact, and processing overhead. | For the same event limit, a longer accumulation window or lockout/cooldown usually increases protection and user disruption; a shorter interval resets sooner. Tune together with the corresponding event threshold. |
app_monitoring.alert_history_limit |
50 | The shipped value of 50 is the current storage/forensics baseline, balancing historical visibility against database or filesystem growth. | Increase for longer forensic/compliance history at the cost of more storage; decrease to control growth, understanding that older evidence will be unavailable sooner. |
common_attacks.block_known_sensitive_paths |
ON / true | Enabled in the shipped baseline as the product’s current safe operating choice for this control. | 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. |
common_attacks.credential_block_seconds |
900 | The shipped value of 900 is the current timing baseline used to balance responsiveness, user impact, and processing overhead. | For the same event limit, a longer accumulation window or lockout/cooldown usually increases protection and user disruption; a shorter interval resets sooner. Tune together with the corresponding event threshold. |
common_attacks.credential_distinct_ip_limit |
8 | The shipped value of 8 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. |
common_attacks.credential_distinct_user_limit |
6 | The shipped value of 6 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. |
common_attacks.credential_distributed_source_min |
Minimum: 3 | 3 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. |
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
Use the feature’s logs and current request evidence as the tuning source. Compare normal traffic with the event that triggered the control, then change only the smallest setting required.
Technical keywords
Aegisify WAF, 1.20.13, attack, deep, dive, reports, story, logs, attack_story_top_items, attack_story_window_hours, app_monitoring, alert_history_limit, common_attacks, block_known_sensitive_paths, credential_block_seconds, credential_distinct_ip_limit
Source baseline
Verified package: Aegisify WAF 1.20.13. Primary source files: includes/class-aegiswaf-storage.php; includes/class-aegiswaf-ai-security.php; includes/class-aegiswaf-api-security.php; includes/class-aegiswaf-managed-rules.php; includes/ddos/class-aegiswaf-ddos-storage.php; includes/admin/pages/class-aegiswaf-page-waf-rules.php; includes/admin/pages/class-aegiswaf-page-logs.php; includes/admin/pages/class-aegiswaf-page-access.php. If a future plugin version changes these settings, support should re-read the installed version rather than carry these defaults forward automatically.