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”

93 publications
Technical guideSource-based analysis

Stop pull_request_target workflows from running fork code

GitHub blocks pull_request_target in public repositories by default from November 2, 2026. Find the workflows that run fork code with secrets, split them, pin a checkout that refuses unsafe refs, and allow the rest deliberately.

Workload security · GitHub · By Cloud Security Desk
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

Treat a cloud model retirement as a security change

Bedrock and Agent Platform fail closed on a model's retirement date, while Foundry can swap a different model in behind the same deployment name. Read the three calendars, compare the replacement's controls and decide per deployment.

AI systems · Amazon Web Services / Microsoft Azure / Google Cloud · 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

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

Plan for incident reporting clocks that start at different moments

GDPR, NIS2, DORA, the SEC, the US banking agencies and CERT-In each start their reporting clock at a different decision. Plan around those triggers, the evidence each first notice needs and the rules still pending.

Detection & response · European Union / U.S. Securities and Exchange Commission / U.S. federal banking agencies / CISA / CERT-In / UK Parliament / Amazon Web Services / Microsoft Azure / Google Cloud · By Cloud Security Desk
Technical guideSource-based analysis

Investigate a SaaS integration breach through its OAuth tokens

A vendor that stores OAuth tokens for your SaaS tenants has been breached. Confirm from your own logs what the tokens did, revoke them on every platform, and search the exposed records for secrets.

Detection & response · Salesforce / Google Workspace / Microsoft Entra ID · By Cloud Security Desk
Technical guideSource-based analysis

Investigate stolen cloud credentials used to run AI models

When stolen keys run foundation models in your account, the evidence is split between CloudTrail, usage logs that may never have been enabled and a bill that lags by a day or more.

Detection & response · Amazon Web Services / Microsoft Azure / Google Cloud · By Cloud Security Desk
Technical guideSource-based analysis

Find the Kubernetes RBAC permissions that lead to cluster admin

Group RBAC grants by what they yield, not by verb. Then close the nodes/proxy exec path with v1.36 fine-grained kubelet permissions, narrow impersonation, and prove each removal with a negative test.

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

Know what service mesh mTLS proves about the caller

A mesh handshake proves that a peer held a key for a namespace and service account. It says nothing about the user or the operation, and permissive defaults, probes and waypoints open paths around it.

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

Tune managed WAF rules without opening a bypass

Fix a managed WAF false positive by changing one rule for one route, then decide what happens to the request body bytes AWS WAF, Azure WAF and Cloud Armor never inspect.

Workload security · Amazon Web Services / Microsoft Azure / Google Cloud · 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

Find the Entra changes that Backup and Recovery cannot roll back

Microsoft Entra Backup and Recovery rolls listed properties back to a daily backup kept for seven days. Credentials, role assignments, owners and user consent stay in place, and an unscoped recovery can undo your own containment.

Resilience · Microsoft Entra / Microsoft Graph · 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

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

Plan Azure disaster recovery for a region without a pair

Thirteen Azure regions have no pair and eight more pair with a restricted-access region. This guide shows which built-in geo-redundancy disappears, what replaces it service by service, and how to choose the recovery region.

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

Test PostgreSQL row-level security with the application role

Row-level security only filters queries from roles that do not bypass it. Test with the production login role, through the production pooler, with transaction-local tenant context and a patched minor release.

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

Restore EBS volumes at the speed your recovery plan assumes

A restored EBS volume is slow until every block arrives from S3. Price the provisioned initialization rate, fast snapshot restore credits and Regional limits as recovery-time arithmetic before an RTO depends on them.

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

Roll over a SAML signing certificate without an SSO outage

Replacing an identity provider's SAML signing key is a separate contract with every service provider. Classify each one by how it learns keys, overlap where it can hold two and finish by removing the old key everywhere.

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

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

Map cloud incident response to NIST SP 800-61 Revision 3

Revision 3 turned NIST's incident handling guide into a CSF 2.0 profile. Translate its rows into provider contracts, cloud evidence, containment authority and recovery ownership, and fix the log defaults first.

Detection & response · NIST / Amazon Web Services / Microsoft Azure / Google Cloud · 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

Contain failures with cell-based architecture and shuffle sharding

Cells limit a failure to the tenants behind one partition only when routing, data and change delivery are partitioned too. Here is how to choose the key, size cells and check the shuffle-sharding arithmetic.

Resilience · AWS / Microsoft Azure / Slack · 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