Alert Settings: edit/delete existing alerts

Feature Alert Settings: edit/delete existing alerts Description Manage existing alerts. How it works AegisWAF applies this capability inside the Logging & Evidence module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met. How to access / Enable or disable Access: AegisWAF → Logs / Attack Story Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable. Recommended setting Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.

Alert Settings: create alerts (title, keyword string, recipients)

Feature Alert Settings: create alerts (title, keyword string, recipients) Description Create keyword-based alerts. How it works AegisWAF applies this capability inside the Logging & Evidence module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met. How to access / Enable or disable Access: AegisWAF → Logs / Attack Story Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable. Recommended setting Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.

Rows-per-page setting

Feature Rows-per-page setting Description Control how many log rows appear per page. How it works AegisWAF applies this capability inside the Logging & Evidence module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met. How to access / Enable or disable Access: AegisWAF → Logs / Attack Story Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable. Recommended setting Use 50 rows per page for most sites; use 25 on slower hosting.

Date range filtering (From / To)

Feature Date range filtering (From / To) Description Filter logs by date window. How it works AegisWAF applies this capability inside the Logging & Evidence module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met. How to access / Enable or disable Access: AegisWAF → Logs / Attack Story Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable. Recommended setting Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.

Log viewer: search + filters (route contains, method, event type/category, action, IP)

Feature Log viewer: search + filters (route contains, method, event type/category, action, IP) Description Filter and search security events. How it works AegisWAF applies this capability inside the Logging & Evidence module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met. How to access / Enable or disable Access: AegisWAF → Logs / Attack Story Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable. Recommended setting Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.

Core event logging (engine / managed_rule / heuristic / api_shield / bot_control / ddos_shield / endpoint_policy)

Feature Core event logging (engine / managed_rule / heuristic / api_shield / bot_control / ddos_shield / endpoint_policy) Description Core logging stream across modules. How it works AegisWAF applies this capability inside the Logging & Evidence module. The engine evaluates configuration, applies matching (path/method/tokens/counters/providers), then records evidence into the event log and executes the configured enforcement action when conditions are met. How to access / Enable or disable Access: AegisWAF → Logs / Attack Story Enable/Disable: Use the module toggle/switch on this screen (or the relevant category toggle) to enable/disable. Recommended setting Start conservative (LOG or Challenge) for new deployments; tighten to Block once you confirm low false positives.

What problem does it solve?

Reduces common WordPress attack surface (headers, hardening, login protection) Adds observability (activity logging + login attempts + file integrity baselines) Adds incident-oriented tooling (malware workflows like incremental scan / incidents / profiles / scheduler tabs in UI) Provides safer DB admin utilities (notably DB prefix management with a “don’t forget the internal keys” phase)

How does Who is it designed for work in Aegisify Shield Security, and what should administrators verify?

body.single-avada_faq h1.entry-title, body.single-avada_faq .entry-title, .fusion-faq-shortcode .fusion-toggle-heading, .fusion-faq-shortcode .panel-title a, .fusion-accordian .panel-title, .fusion-accordian .panel-title a {font-size:14px!important;color:#2d2e3d!important;} .aegisify-faq-tech,.aegisify-faq-tech p,.aegisify-faq-tech li,.aegisify-faq-tech td,.aegisify-faq-tech th,.aegisify-faq-tech code {font-size:11.5px!important;color:#2d2e3d!important;line-height:1.65;} .aegisify-faq-tech h2 {font-size:14px!important;color:#2d2e3d!important;line-height:1.4;margin:20px 0 8px;} .aegisify-faq-tech h3 {font-size:12.5px!important;color:#2d2e3d!important;line-height:1.45;margin:16px 0 6px;} .aegisify-faq-tech table {width:100%;border-collapse:collapse;margin:10px 0 14px;} .aegisify-faq-tech th,.aegisify-faq-tech td {vertical-align:top;text-align:left;border:1px solid #dedfe3;padding:7px 8px;} .aegisify-faq-tech code {overflow-wrap:anywhere;word-break:break-word;} Technical summary How does Who is it designed for 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.enable_hardening off Disabled in the shipped baseline because enabling it can change live request handling, indexing behavior, automation, enforcement, or integration traffic and should be reviewed for the specific site first. OFF leaves the behavior inactive. Turn it ON only after checking prerequisites and expected traffic/content because this setting can introduce enforcement, automation, indexing, outbound integration, or additional processing depending on the feature. activity_log.retention_days 30 The shipped value of 30 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. malware.enabled yes 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. file_integrity.scan_mode light “light” 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. 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, designed, who, hardening, enable_hardening, activity_log, retention_days, malware, enabled, file_integrity, scan_mode 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.

Who is it designed for?

WordPress site owners/admins who want practical protection without enterprise infrastructure Agencies managing multiple WordPress sites Security-conscious operators on shared hosting (Hostinger/HostGator/Bluehost-style environments) Technical admins who want visibility (logs, scan results, enforcement actions) and control knobs

What is Aegis Shield Security?

A WordPress security plugin built to run efficiently on shared hosting, providing defensive controls, hardening, monitoring/logging, security header enforcement, malware/integrity tooling, login protection, and database tools from inside WP Admin.

Archives: FAQs | Aegisify - WordPress Tools, Security…

Categories: AegisWAF
Alert Settings: edit/delete existing alerts
read more
Categories: AegisWAF
Alert Settings: create alerts (title, keyword string, recipients)
read more
Categories: AegisWAF
Rows-per-page setting
read more
Categories: AegisWAF
Date range filtering (From / To)
read more
Categories: AegisWAF
Log viewer: search + filters (route contains, method, event type/category, action, IP)
read more
Categories: AegisWAF
Core event logging (engine / managed_rule / heuristic / api_shield / bot_control / ddos_shield / endpoint_policy)
read more
Categories: AegisShield
What problem does it solve?
read more
Categories: AegisShield
How does Who is it designed for work in Aegisify Shield Security, and what should administrators verify?
read more
Categories: AegisShield
Who is it designed for?
read more
Categories: AegisShield
What is Aegis Shield Security?
read more

What’s New At Aegisify