Skip to content
Cloud Security DeskSearch
Menu

Evidence search

Search

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

Results for “Availability”

32 publications
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

Close the AWS sessions that survive identity shutdown

Removing a login does not by itself establish that issued AWS credentials have lost their authority. Build a revocation procedure that accounts for both.

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

Keep private documents out of shared RAG answers

Authorize retrieved documents before they enter model context, preserve permissions on chunks, and make source access changes visible in the retrieval path.

AI systems · Azure · By Cloud Security Desk
Technical guideSource-based analysis

Roll out Kubernetes Pod Security Admission without surprises

Stage namespace enforcement around the Pods a controller will create next, with explicit policy versions, runtime checks, and narrowly owned exceptions.

Workload security · Kubernetes · By Cloud Security Desk
Technical guideSource-based analysis

Choose the S3 object events your investigation will need

CloudTrail event history is not an object-access ledger. Build selectors around the questions an investigation must answer, then test the exclusions.

Detection & response · AWS · By Cloud Security Desk
Technical guideSource-based analysis

Lock GitHub deployment trust to the job you intend

A short-lived token still needs a narrow trust decision. Review the subject, deployment environment, reusable workflow and AWS role together.

Identity & access · AWS / GitHub · 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
Field noteIllustrative analysis

Five Kubernetes events your cloud trail will not explain

Cloud control-plane logs tell you who changed the cluster. They do not fully explain what happened inside it.

Detection & response · Workload security · Kubernetes · By Umair Akbar and Ahmed Elshekh