One admin path bypasses MFA after tightening Cloudflare Access rules.
A Cloudflare Access policy is tightened and one admin path still bypasses MFA because the service token include stayed above the group rule
The MFA rule exists, but the policy order still allows one legacy service token include to short-circuit evaluation.
Scenario
What to check first
- Identify the primary failure signal in the The New Checkpoint Was Installed at the Main Door and One Side Entrance Still Honored a Service Pass Placed Above the Guard Roster scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect policy order before adding more identity checks.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field