How does Extended Retention 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 Extended Retention 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 activity_log.flat_file_retention_days 7 The shipped value of 7 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. 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. activity_log.archive_enabled 0 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.archive_format csv “csv” 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. activity_log.archive_frequency monthly “monthly” 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_integrity.scan_history_limit 10 “10” 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, archive, cleanup, extended, history, retention, activity_log, flat_file_retention_days, retention_days, archive_enabled, archive_format, archive_frequency, file_integrity, scan_history_limit 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.

How does Advanced Filtering 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 Advanced Filtering 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, advanced, filtering, 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.

How does Export Logs (CSV / JSON) 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 Export Logs (CSV / JSON) 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 → Activity Log. 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_monitor.exclude_all_logs 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. file_monitor.exclude_wp_default_logs 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. activity_log.archive_enabled 0 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.archive_format csv “csv” 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. activity_log.archive_frequency monthly “monthly” 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. activity_log.flat_file_retention_days 7 The shipped value of 7 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. 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. 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. 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, audit, csv, event, events, export, json, log, logging, logs, file_monitor, exclude_all_logs, exclude_wp_default_logs, activity_log, archive_enabled 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.

How does Pro Module Indicators (CSP Builder, Attack Story, etc.) 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 Pro Module Indicators (CSP Builder, Attack Story, etc.) 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 → Security Headers. 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, attack, builder, csp, indicators, module, story, 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.

How does Deep Scan Summaries (Integrity, Quick Scan, Attack Story) 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 Deep Scan Summaries (Integrity, Quick Scan, Attack Story) 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 → File Integrity. 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.auto_scan_frequency weekly “weekly” 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_integrity.scan_history_limit 10 “10” 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_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. malware.auto_scan yes 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. malware.scan_dirs ["plugins","themes"] “['plugins', 'themes']” 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. malware.scan_profile balanced “balanced” is the shipped baseline and is the closest current code-defined baseline/medium operating point. Use stricter behavior only after reviewing site-specific evidence. Treat the shipped value as the baseline/medium operating point. A stricter profile generally increases sensitivity and may increase false positives or workload; a more permissive profile generally reduces intervention but can allow more unwanted activity. malware.allowlist_hashes [] 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. malware.custom_directories [] 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. 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 When a file alert appears, verify the path, change source, checksum/signature evidence, and recent deployment history before treating the change as malicious. Maintenance, cache, backup, and log files can create high-volume legitimate change patterns. Technical keywords Aegisify Shield Security, 7.4.5, attack, checksum, deep, file, hash, integrity, monitor, quick, scan, story, summaries, file_integrity, auto_scan_frequency, scan_history_limit 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.

How does Enhanced System Health Metrics 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 Enhanced System Health Metrics 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, enhanced, health, metrics, system, 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.

Activity Log Integration for DB Events

FREE: Not available. PRO: Available. What it does: Logs sensitive DB actions. How to use it properly: Use for auditing.

Pagination Options (25 / 50 / 100)

FREE: Not available. PRO: Available. What it does: Controls rows per page. How to use it properly: Increase during investigations.

Prefix Rollback & Restore

FREE: Not available. PRO: Available. What it does: Restores previous DB state. How to use it properly: Roll back immediately if issues occur.

Internal Prefix-Bound Key Updates

FREE: Not available. PRO: Available. What it does: Updates prefix-dependent keys. How to use it properly: Mandatory for prefix changes.

Archives: FAQs | Aegisify - WordPress Tools, Security…

Categories: AegisShield
How does Extended Retention work in Aegisify Shield Security, and what should administrators verify?
read more
Categories: AegisShield
How does Advanced Filtering work in Aegisify Shield Security, and what should administrators verify?
read more
Categories: AegisShield
How does Export Logs (CSV / JSON) work in Aegisify Shield Security, and what should administrators verify?
read more
Categories: AegisShield
How does Pro Module Indicators (CSP Builder, Attack Story, etc.) work in Aegisify Shield Security, and what should administrators verify?
read more
Categories: AegisShield
How does Deep Scan Summaries (Integrity, Quick Scan, Attack Story) work in Aegisify Shield Security, and what should administrators verify?
read more
Categories: AegisShield
How does Enhanced System Health Metrics work in Aegisify Shield Security, and what should administrators verify?
read more
Categories: AegisShield
Activity Log Integration for DB Events
read more
Categories: AegisShield
Pagination Options (25 / 50 / 100)
read more
Categories: AegisShield
Prefix Rollback & Restore
read more
Categories: AegisShield
Internal Prefix-Bound Key Updates
read more

What’s New At Aegisify