Skip to content
Cloud Security DeskSearch
Menu

Evidence search

Search

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

Results for “Caching”

22 publications
Technical guideSource-based analysis

Run AI coding agents in GitHub Actions without exposing secrets

Treat the agent job as an untrusted-input processor. Follow the outside text from the trigger that admits it to the credentials it can reach, then split reading from writing so a successful injection reaches nothing worth stealing.

AI systems · GitHub / Anthropic / Google / Microsoft · By Cloud Security Desk
Technical guideSource-based analysis

Admit MCP servers before agents can call their tools

An MCP server's tool descriptions can change after approval with no new release. Record provenance and execution context, hash the definitions per authorization context, enforce the pin at a gateway or allowlist, and watch for drift.

AI systems · MCP / AWS / Anthropic / GitHub / Microsoft Azure / Google Cloud / OWASP · By Cloud Security Desk
Technical guideSource-based analysis

Find the AWS global control planes in your recovery path

Thirteen AWS control planes run in us-east-1 or us-west-2, and ordinary calls from other Regions still reach them. Audit runbooks, SDK settings and the last exercise, then swap each dependency for a data-plane operation.

Resilience · Amazon Web Services · By Cloud Security Desk
Technical guideSource-based analysis

Plan for an outage at your CDN or edge provider

When the CDN, WAF and edge provider fails, traffic can move to a regional WAF, a second CDN or the origin, and each keeps less protection. Decide early whether a second path is worth securing.

Resilience · Microsoft Azure / Cloudflare / Amazon Web Services / Google Cloud · By Cloud Security Desk
Technical guideSource-based analysis

Use 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 Desk
Technical guideSource-based analysis

Keep semantic response caches inside authorization scope

A semantic cache returns whatever its nearest stored prompt earned. Put tenant, user or entitlement scope, template and model into an exact-match partition, close the write path, and treat thresholds as a correctness setting.

AI systems · Microsoft Azure / Google Cloud / Redis / GPTCache / Amazon Web Services · By Cloud Security Desk
Technical guideSource-based analysis

Compare just-in-time privileged access in AWS, Azure and Google Cloud

Entra PIM and Google Cloud PAM make roles temporary natively, while AWS relies on TEAM or partner tools. All three end elevation by removing an assignment, and sessions, caches and minted tokens can keep running.

Identity & access · Amazon Web Services / Microsoft Azure / Microsoft Entra / Google Cloud · By Cloud Security Desk
Technical guideSource-based analysis

Separate API gateway JWT checks from backend authorization

A gateway that accepts a JWT has checked its signature, issuer, audience and time window. It has not checked token type, revocation, cached decisions or object ownership. This mapping shows which side owns each decision.

Workload security · Amazon Web Services / Microsoft Azure / Google Cloud · By Cloud Security Desk
Technical guideSource-based analysis

Plan the move from ingress-nginx to Gateway API

Ingress-nginx is archived and will not be patched again. Contain the old controller, inventory the behaviors your clients depend on, and cut over to Gateway API with evidence and a rollback path.

Workload security · Kubernetes / Google Cloud / AWS / Azure · By Cloud Security Desk
Technical guideSource-based analysis

Give Kubernetes pods cloud credentials without static keys

EKS Pod Identity, IRSA, AKS Workload ID and Workload Identity Federation for GKE all swap a projected token for short-lived credentials. What leaks if you stop there is the node's own identity.

Identity & access · Amazon Web Services / Microsoft Azure / Google Cloud / Kubernetes · By Cloud Security Desk
Technical guideSource-based analysis

Publish npm packages with trusted publishing instead of long-lived tokens

npm revoked classic tokens and capped write tokens at 90 days. Move CI releases to trusted publishing with staged approval, then protect the workflow, tags and environment that now hold publish authority.

Workload security · npm / GitHub / GitLab / CircleCI / Sigstore · By Cloud Security Desk
Technical guideSource-based analysis

Know where cloud AI services process your prompts

Bedrock inference profiles, Foundry deployment types and Agent Platform endpoints each decide where a prompt is processed, separately from where data rests. Compare what each provider commits to and how to enforce it.

AI systems · Amazon Web Services / Microsoft Azure / Google Cloud · By Cloud Security Desk
Technical guideSource-based analysis

Let AWS workloads call external services with IAM-issued tokens

IAM outbound identity federation lets an AWS role trade its credentials for a signed JWT instead of storing a vendor API key. AWS controls issuance; the receiving service's claim checks decide what the token is worth.

Identity & access · Amazon Web Services / AWS IAM / AWS STS / Microsoft Entra · By Cloud Security Desk
Technical guideSource-based analysis

Remove unnecessary personal data before sending Vertex AI prompts

Reduce personal data in Vertex AI prompts with field selection, Sensitive Data Protection, deliberate transformations, and safe failure handling.

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

Check and stop anonymous access to Azure blobs

Understand account and container settings and prove both anonymous denial and intended app access.

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

Design application authorization before writing Cedar policies

Define business actions, trustworthy entities and tenant boundaries before writing Cedar policies, then make the application responsible for enforcing the resulting decision.

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

Choose who can share an inference prefix cache

Choose the principals allowed to share prefix state, then carry that decision through request routing, offload, transfer and restore.

AI systems · vLLM / NVIDIA · By Cloud Security Desk
Technical guideSource-based analysis

Rotate Entra application certificates with proof of adoption

A renewed certificate can exist in Key Vault while a running client still uses the old key. Define the evidence that makes application rotation complete.

Identity & access · Microsoft Entra / Azure Key Vault · By Cloud Security Desk
Technical guideSource-based analysis

Know when AWS KMS encryption needs an envelope

KMS Encrypt has small plaintext limits. Follow the data key and encrypted-message format when an application needs to protect larger payloads.

Workload security · AWS · 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
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
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