Overview
The collected backend.frontName is a valid nonempty route other than admin or backend. Route obscurity is not authentication or access control.
Why it Matters
A predictable Admin route makes routine discovery easier, but a changed path is only an obscurity measure. URLs can still appear in browser history, links and operational records.
Treat the route-name declaration as one small deployment policy alongside enforced authentication, MFA and access restrictions.
Verification Steps
Manual Verification
- Inspect only backend.frontName from the deployed env.php.
- Check that it is a valid nonempty route and is neither admin nor backend.
- Confirm the intended Admin URL with the deployment owner without publishing it.
Command / Review Sample
php -r '$c = require "app/etc/env.php"; echo ($c["backend"]["frontName"] ?? "<missing>"), PHP_EOL;'
Use the assessed Magento project and the appropriate application or read-only review account. Replace example hosts, paths and identifiers with the assessment scope; configuration and source fragments are illustrative.
Remediation / Fix Guidance
- Investigate and change: Choose an uncommon Admin frontName and apply it through the supported Magento deployment configuration workflow. Update proxy access rules, monitoring and administrator bookmarks; retain MFA and network restrictions.
- Validate the change: Confirm the new Admin route works and common admin/backend routes no longer expose the intended login. A renamed route is not access control.
- Rerun MB-0006 against the same release, profile and relevant file/key/package scope; compare the new evidence and inspect any independent collection gaps.
Examples
Illustrative examples only. Interpret them within the current revision criterion above; missing collection evidence is unresolved, never PASS.
Fail Example
backend.frontName = admin
Pass Example
backend.frontName = merchant_control_42, an approved valid route distinct from admin and backend.
Scope and Evidence Limits
Rule revision: 4. Target modes: LOCAL.
The collected backend.frontName is a valid nonempty route other than admin or backend. Route obscurity is not authentication or access control.
The collected app/etc/env.php backend.frontName declaration is a valid non-empty route and differs case-insensitively from admin. This assesses the configured backend route; route entropy and actual public reachability require separate evidence.
Catalog coverage describes implementation capability, not a scan outcome. An incomplete manual review cannot establish that the criterion is satisfied.