Evidence search
Search
Search titles, summaries, topics, providers, authors, and the full open-access corpus.
Results for “fail open”
6 publicationsRoll out configuration changes as carefully as code
Flags, policy rows, generated files and customer settings triggered several global outages between 2024 and 2026. Seven primary incident reports show how each change slipped past its safeguards, and which controls their authors adopted afterward.
Resilience · Amazon Web Services / Microsoft Azure / Google Cloud / Cloudflare / CrowdStrike · By Cloud Security DeskUse DNS egress filtering without mistaking it for a firewall
Resolver-layer filters in AWS, Azure and Google Cloud decide which names a workload can resolve, not where it connects. What each provider says its DNS control misses, and the connection control to pair with it.
Workload security · Amazon Web Services / Microsoft Azure / Google Cloud · By Cloud Security DeskMap the OWASP Top 10 for Agentic Applications to cloud controls
Each OWASP agentic risk mapped to the controls AWS, Microsoft and Google document for their agent platforms, with a plain account of which risks no infrastructure setting can close.
AI systems · OWASP GenAI Security Project / Amazon Web Services / Microsoft Azure / Google Cloud · By Cloud Security DeskDesign health checks that remove broken instances without causing outages
A health check is an automated decision to remove capacity. Keep load balancer checks local, learn what your platform does when every target fails, and set probe timing from documented defaults.
Resilience · Amazon Web Services / Microsoft Azure / Google Cloud / Kubernetes · By Cloud Security DeskGive Kubernetes admission webhooks an explicit failure contract
Treat an admission webhook as a control-plane dependency with explicit behavior for denial, call failure, mutation and the changes needed to repair it.
Workload security · Kubernetes · By Cloud Security DeskQwen3.8-Flash-Next and GLM-5.3-Flash share a 3:1 long-context pattern
Both models replace most conventional attention layers with recurrent state and reserve sparse attention for periodic retrieval. Their differences lie in where they place capacity, how much neural computation they activate, and what their serving stacks must keep trustworthy.
AI systems · Resilience · By Umair Akbar and Ahmed Elshekh