Fail open or fail closed: what vendors publish
Failure mode decides whether an AI action is blocked or allowed when the control breaks. Of 16 vendors read on 16 Nov 2026, Cisco documents a fail-closed default with an operator override, and HiddenLayer documents a timeout setting for one detector. Most others have none found.
Facts read on .
What happens when the control fails?
When a runtime control fails or times out, the system either blocks the action (fail closed) or lets it through (fail open). The choice trades safety against availability, and it should be a decision you made, not a default you found later.
Cisco's Kong plugin for AI Defense fails closed by default: traffic is blocked when inspection is unavailable. An operator can set it to fail open.
Sources: Cisco AI Defense Kong plugin.
Which vendors document their failure mode?
On 16 Nov 2026 the documented cases are few. Cisco publishes its default. HiddenLayer's documentation describes a fail-open or fail-closed timeout for its code detector, but none found for a platform-wide default.
For Bay, Check Point, CrowdStrike, Lasso, Straiker, Zenity and others, the evidence files record fail-open or fail-closed behavior as none found. That is not a statement about the product, only about what is public.
Sources: Cisco AI Defense Kong plugin; HiddenLayer runtime release notes.
What about timeouts?
A timeout is the point where a slow control counts as failed. Palo Alto Networks documents a verdict timeout setting, but none found for the action taken when it expires.
Ask each vendor for the timeout value, the default action on expiry and whether you can set the default per policy or per action.
Sources: Prisma AIRS API Intercept overview; Palo Alto Networks: integrate Anthropic inference hooks.
How should you choose a failure mode?
Choose per action, not per product. Fail closed for actions that cannot be undone, such as credential access or data leaving the company. Fail open, with an alert, for low-risk content checks in a customer path where an outage would stop sales.
Write the choice in the runbook and test it by cutting the control's connection in a staging environment.
What can you ask a vendor?
Ask four questions: what is the default on failure, can I change it, what is the timeout, and what do I see when it happens. Request the answer in public documentation, since a claim without a public source can score at most 7 in this site's method.
On-device decisions avoid a network dependency. Bay says its decisions are made locally with no cloud round trip, though its fail-open or fail-closed behavior is none found.
Sources: Bay agent runtime enforcement.
Why does this matter for AI more than for other tools?
An AI control sits in the path of work that runs continuously and unattended. A fail-closed control that stops can halt a pipeline overnight, and a fail-open control that stops silently removes protection while looking healthy.
Agents act without a person watching each step, so a quiet failure is the worse case. Alert on the failure itself, not only on blocked actions.
How do you test the failure path?
Block the control's network path or stop its process in a staging environment, send test actions of each type and record what the application does. Repeat with a slow response to check the timeout.
Write down what you saw next to the vendor's documentation. A gap between the two is a finding for the vendor, and a reason to set the default yourself.
What does a good public statement look like?
A good statement names the default, the timeout, the way to change each and the log entry written when the control fails. Cisco's plugin README covers the default and the override.
Where a statement is missing, record none found on the read date and ask the vendor to publish it.
Sources: Cisco AI Defense Kong plugin.
Questions about this topic
What happens when the control fails?
The system either blocks the action (fail closed) or lets it through (fail open). Cisco documents a fail-closed default for its Kong plugin, with an operator override.
Sources
- Cisco AI Defense Kong plugin (github.com), read
- HiddenLayer runtime release notes (docs.hiddenlayer.ai), read
- Prisma AIRS API Intercept overview (docs.paloaltonetworks.com), read
- Bay agent runtime enforcement (bay.io), read