Skip to content
Cloud Security DeskSearch
Menu

Evidence search

Search

Search titles, summaries, topics, providers, authors, and the full open-access corpus.

Results for “Resilience”

15 publications
Technical guideSource-based analysis

Recovery objectives that match the cloud service

Define the business function, outage clock, recoverable data and dependency assumptions before choosing a cloud disaster-recovery architecture.

Resilience · AWS / Azure / Google Cloud / NIST · By Cloud Security Desk
Technical guideSource-based analysis

Entra emergency access that survives normal sign-in failure

A second administrator account does not prove an independent recovery path. Test the credential, workstation, policy and alert dependencies together.

Identity & access · Microsoft Entra · By Cloud Security Desk
Technical guideSource-based analysis

A controlled return from the SQS dead letter queue

Repair the failure, check consumer compatibility and return failed work with a bounded rate, observable stop conditions and business reconciliation.

Resilience · AWS · By Cloud Security Desk
Technical guideSource-based analysis

Error budgets for controlled service degradation

Protect essential work under load while counting rejected and degraded requests against the service promise that users were actually given.

Resilience · Google / Envoy · By Cloud Security Desk
Technical guideSource-based analysis

Certificate renewal under shorter validity limits

Use the public TLS issuance schedule to review authorization, renewal, deployment and independent verification of the certificate an endpoint actually serves.

Resilience · CA/Browser Forum / Let's Encrypt / AWS · By Cloud Security Desk
Technical guideSource-based analysis

The bottlenecks that shape a cloud DDoS response

Distinguish bandwidth, packet processing, connection state and application work before choosing a DDoS response or assuming the whole service path is protected.

Resilience · AWS / Azure / Google Cloud / Cloudflare · By Cloud Security Desk
Technical guideSource-based analysis

Where DNS failover loses control of the clock

Separate authoritative routing, resolver caches, stale answers, runtime caching and existing connections when describing what DNS failover can achieve.

Resilience · AWS / Cloudflare / Oracle · By Cloud Security Desk
Technical guideSource-based analysis

Keep database changes compatible with application rollback

Preserve an explicit relationship between old code and migrated state through additive changes, safe backfills, and a defined rollback window.

Resilience · Kubernetes / GitLab · By Cloud Security Desk
Research noteSource-based analysis

Stop retries from amplifying an outage

Count attempts across the complete request path, give retries a finite owner and budget, and define how repeated intent avoids duplicate side effects.

Resilience · AWS · By Cloud Security Desk
Technical guideSource-based analysis

Keep encryption keys recoverable with the data they protect

Trace each encrypted recovery point to its required key, usable lifecycle state, and restore permissions before retiring cryptographic dependencies.

Resilience · AWS / Azure · By Cloud Security Desk
Technical guideSource-based analysis

Make regional failover work without new infrastructure

Prepare capacity, dependencies, and the routing control path before an incident, then measure when clients reach an accepted recovery service.

Resilience · AWS · By Cloud Security Desk
Technical guideSource-based analysis

Measure recovery by the service you can restore

Define application acceptance, recoverable data, and a complete timeline before treating a completed restore job as proof of recovery.

Resilience · AWS / PostgreSQL · By Cloud Security Desk
Technical guideSource-based analysis

Protect backup copies from the account that runs production

Map deletion authority, retention protection, keys, and recovery identities so a surviving backup has a usable path back to service.

Resilience · AWS · By Cloud Security Desk
Research reportDesk publication

Qwen3.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
Technical guideIllustrative analysis

Recover the control plane before you need it

A recovery plan that depends on the compromised identity system is an aspiration. Build and test an independent administrative path.

Resilience · Identity & access · AWS / Azure / Google Cloud · By Umair Akbar and Ahmed Elshekh