Strong Password Enforcement

Description: Enforces password complexity requirements by role (Pro). How it works: When enabled, AegisShield validates new passwords against configured rules (length and character requirements) and rejects weak passwords. How to access / configure: WP Admin → AegisShield → Hardening → Password Policy. Enable strong password enforcement. Configure requirements and Save Changes. Recommended setting: Enforce for administrators and editors at minimum; require 12+ characters with mixed classes.

Description: Blocks requests used to enumerate author usernames via ?author= queries. How it works: block_user_enum_behavior controls whether author enumeration patterns are denied or redirected to reduce username discovery. How to access / configure: WP Admin → AegisShield → Hardening. Enable “Block author scans / user enumeration”. Save changes. Recommended setting: Enable; combine with Login Guard and MFA for strongest account protection.

Hide WordPress Version

Description: Removes WordPress version output where possible to reduce fingerprinting. How it works: AegisShield strips version meta/generator output and related headers to make automated targeting harder. How to access / configure: WP Admin → AegisShield → Hardening. Enable “Hide WordPress version”. Save changes. Recommended setting: Enable on all public sites.

Description: Controls XML-RPC behavior to reduce abuse while keeping compatibility when needed. How it works: disable_xmlrpc_behavior determines whether XML-RPC is allowed, partially restricted, or denied with an error page. How to access / configure: WP Admin → AegisShield → Hardening. Locate XML-RPC behavior dropdown. Choose the desired behavior and Save Changes. Recommended setting: Use “Allow core XML‑RPC but restrict dangerous methods” when compatibility is needed; otherwise deny XML‑RPC on sites that don’t use it.

Disable Editor Screens

Description: Hides/disables editor screens that are commonly abused (Pro/extended behavior depending on configuration). How it works: When enabled, AegisShield removes access to certain edit endpoints and logs the hardening change. How to access / configure: WP Admin → AegisShield → Hardening. Enable “Disable editor screens”. Save changes. Recommended setting: Enable unless you have a specific operational need for in-dashboard editing.

Description: Prevents editing plugin/theme files from the WordPress editor to reduce post-compromise abuse. How it works: Hardening sets the relevant WordPress constant/behavior so attackers can’t use the built-in editor to plant code. How to access / configure: WP Admin → AegisShield → Hardening. Enable “Disable file editing”. Save changes. Recommended setting: Enable on production sites; do code changes via SFTP/Git instead.

File Monitor Email Event Types

Description: Selects which file events should generate email notifications (new/modified/deleted). How it works: email_events determines which event categories trigger email messages when alerts are enabled. How to access / configure: WP Admin → AegisShield → File Integrity → Email Settings. Choose which event types should email. Save changes. Recommended setting: Email only Modified/Deleted for most sites; include New files if you’re frequently targeted.

File Monitor Email Recipients

Description: Defines who receives file integrity/monitor alerts. How it works: AegisShield sends alert emails to the configured recipients list when email events match your thresholds. How to access / configure: WP Admin → AegisShield → File Integrity → Email Settings. Enter recipient email(s) (comma-separated). Save changes. Recommended setting: Use a dedicated security inbox and add a backup recipient for redundancy.

File Monitor Email Mode

Description: Controls when file-monitor events send emails (e.g., off, high-only, all). How it works: email_mode decides whether change events are grouped/suppressed or immediately emailed depending on severity and chosen mode. How to access / configure: WP Admin → AegisShield → File Integrity → Email Settings. Select Email Mode. Save changes and test with a controlled file change. Recommended setting: Use High-only mode to prevent alert fatigue.

File Monitor Interval

Description: Controls how often the File Monitor checks for new/changed files. How it works: interval determines the periodic monitoring cadence so AegisShield can detect bursts of changes quickly. How to access / configure: WP Admin → AegisShield → File Integrity → File Monitor. Set the monitoring interval (minutes). Save changes. Recommended setting: 15 minutes is a solid default; use 30–60 minutes on shared hosting if needed.

News & Events

Categories: AegisShield
Strong Password Enforcement
read more
Categories: AegisShield
Block Author Scans
read more
Categories: AegisShield
Hide WordPress Version
read more
Categories: AegisShield
Disable XML-RPC
read more
Categories: AegisShield
Disable Editor Screens
read more
Categories: AegisShield
Disable File Editing
read more
Categories: AegisShield
File Monitor Email Event Types
read more
Categories: AegisShield
File Monitor Email Recipients
read more
Categories: AegisShield
File Monitor Email Mode
read more
Categories: AegisShield
File Monitor Interval
read more

keep updated & don’t miss anything!

We regularly develop new plugins and release them for free because they’re solutions we trust and use ourselves.

By entering your email, you agreed to our Privacy Policy and Terms & Conditions

Frequently Asked Questions

Support Docs

Ticketing System

password requirements aegisshield passwords configure description enforces complexity role pro works enabled validates new against configured rules length character rejects weak access admin hardening policy enable strong enforcement save changes recommended setting enforce administrators editors minimum require characters mixed classes

Powered by Aegisify Links

2026 - Aegisify.com - Everything Your WordPress Site Needs, One Platform. One Price.

Privacy Policy * Terms of Use * Free Plugin Disclaimer * End User License Agreement