Review XML-RPC, application passwords, public username exposure and dashboard access in one settings area.
Available in the current release.
A practical review of supported hardening controls.
Some publishing tools and integrations rely on this interface.
The administrator enables this control after checking dependencies.
Review other hardening controls according to how your site is used.
Read what the WordPress feature exposes and how your site currently uses it.
Identify connected apps, publishing tools or user roles that rely on that behaviour.
Enable the FluentAuth setting when the restriction fits your site’s requirements.
Verify your integration and account workflows still work as intended.
Default interfaces and account behaviours may stay enabled long after the site’s needs are clear. Reviewing them helps you decide which access paths and exposed information are actually necessary.
FluentAuth provides supported controls for XML-RPC, application passwords, public usernames and dashboard access. Applying the right controls can reduce those particular risks. Check integrations first so a protection does not interrupt a legitimate workflow.
Keep useful WordPress features and deliberately restrict the ones your site does not need.
Get FluentAuth →Available in the current release.
Follow the setup guide →
For example, restricting application passwords can affect an integration that uses them. Limiting dashboard access should be tested with the roles you intend to keep on the front end.
When a site moves from development to regular use, review which accounts and interfaces remain necessary. Combine these settings with login limits and role-based verification for a more complete login policy.
No. These settings control supported WordPress behaviours. FluentAuth does not provide a web application firewall, and hardening does not replace updates, backups or protection supplied by your host.
Review your hardening settings alongside login limits and role-based verification.