Hardening Changes Logged

Description: Records hardening setting changes in the Activity Log (Pro). How it works: When hardening settings are saved, AegisShield emits audit events so you can track who changed protections and when. How to access / configure: WP Admin → AegisShield → Activity Log. Filter for Hardening events. Review changes after maintenance windows. Recommended setting: Enable Activity Log retention sufficient to audit hardening changes (30–90 days).

Description: Requires at least one symbol in passwords (when enforcement is enabled). How it works: password_require_symbol adds a symbol check to password validation. How to access / configure: WP Admin → AegisShield → Hardening → Password Policy. Enable symbol requirement. Save changes. Recommended setting: Enable for admins; consider optional for lower roles to reduce support burden.

Description: Requires at least one numeric character in passwords (when enforcement is enabled). How it works: password_require_number adds a numeric check to password validation. How to access / configure: WP Admin → AegisShield → Hardening → Password Policy. Enable number requirement. Save changes. Recommended setting: Enable; but prioritize length over complex rules if users struggle.

Require Lowercase Characters

Description: Requires at least one lowercase letter in passwords (when enforcement is enabled). How it works: password_require_lowercase adds a lowercase check to password validation. How to access / configure: WP Admin → AegisShield → Hardening → Password Policy. Enable lowercase requirement. Save changes. Recommended setting: Enable for admin/editor roles.

Require Uppercase Characters

Description: Requires at least one uppercase letter in passwords (when enforcement is enabled). How it works: password_require_uppercase adds an uppercase check to the password validation routine. How to access / configure: WP Admin → AegisShield → Hardening → Password Policy. Enable uppercase requirement. Save changes. Recommended setting: Enable for admin/editor roles.

Password Minimum Length

Description: Sets the minimum required password length when strong password enforcement is enabled. How it works: password_min_length is checked during password set/reset and weak passwords are rejected. How to access / configure: WP Admin → AegisShield → Hardening → Password Policy. Set minimum length. Save changes. Recommended setting: Use 12+ for admins; 10+ for lower roles if needed.

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.

Archives: FAQs | Aegisify - WordPress Tools, Security…

Categories: AegisShield
Hardening Changes Logged
read more
Categories: AegisShield
Require Symbols
read more
Categories: AegisShield
Require Numbers
read more
Categories: AegisShield
Require Lowercase Characters
read more
Categories: AegisShield
Require Uppercase Characters
read more
Categories: AegisShield
Password Minimum Length
read more
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

What’s New At Aegisify