Overview
The supplied literal project configuration contains supported cache backend declarations and no assessed declared backend is file-based. Missing or malformed required evidence remains unavailable. This does not require every backend to be Redis or prove running cache service health.
Why it Matters
The supplied literal project configuration contains supported cache backend declarations and no assessed declared backend is file-based. Missing or malformed required evidence remains unavailable. This does not require every backend to be Redis or prove running cache service health.
This scoped observation supports a focused review. Independent operational evidence is needed for controls outside the declared criterion.
Verification Steps
Manual Verification
- Read the supported cache backend declarations in supplied literal project configuration.
- Determine whether any assessed declared backend is file-based. Missing or malformed required declarations remain unavailable.
- Review actual service health, architecture and running cache behavior separately; Redis is not mandatory for this predicate.
Command / Review Sample
# Review env.php cache.frontend declarations with secrets redacted.
php bin/magento config:show system/full_page_cache/caching_application
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
- Review the exact declared backend/key in app/etc/env.php against the intended deployment baseline. If Redis is used, verify authentication and network/ACL access separately before changing the backend.
- Test cache/session correctness and effective access with the deployed worker configuration. A declaration alone does not prove runtime enforcement.
- Rerun MB-0741 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
An assessed literal cache backend declaration selects a file-based backend.
Pass Example
Supported complete assessed declarations select non-file backends.
No claim of Redis use or running service health.
Scope and Evidence Limits
Rule revision: 2. Target modes: LOCAL.
The supplied literal project configuration contains supported cache backend declarations and no assessed declared backend is file-based. Missing or malformed required evidence remains unavailable. This does not require every backend to be Redis or prove running cache service health.
The supplied literal project configuration contains supported cache backend declarations and no assessed declared backend is file-based. Missing or malformed required evidence remains unavailable. This does not require every backend to be Redis or prove running cache service health.
Catalog coverage describes implementation capability, not a scan outcome. An incomplete manual review cannot establish that the criterion is satisfied.