Skip to content
Cloud Security DeskSearch
Menu

Evidence search

Search

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

Results for “network”

97 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

Respond to an exposed AWS access key beyond the quarantine policy

In a published test, AWS attached its quarantine policy 10 seconds after a key leaked, but the policy denies actions without ending access. This playbook covers what it leaves open, which credentials outlive the key, and the order of containment.

Detection & response · Amazon Web Services / GitHub / 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

Roll out Entra token protection without breaking unsupported clients

Token protection makes Entra ID refuse token requests that a device-bound session does not back. Scope it to supported apps and platforms, triage report-only data by code and platform, and cover what stays unbound.

Identity & access · Microsoft Entra / Microsoft Intune / Microsoft Graph · 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 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

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

Lock down self-hosted model servers before exposing them

Built-in credentials in vLLM, SGLang and Triton cover less than their names suggest, Ollama's local API has none, and vLLM and SGLang leave their internal planes unauthenticated. Here is what stays open and what must sit in front.

AI systems · vLLM / SGLang / Ollama / NVIDIA Triton Inference Server / Kubernetes / nginx · 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

Verify EC2 containment beyond a security group change

Swapping a compromised EC2 instance into an isolation security group stops new connections, not tracked ones. Learn which flows survive, how long idle timeouts let them run, and how to prove the cut happened.

Detection & response · Amazon Web Services · 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

Give a SaaS vendor an AWS role without creating a confused deputy

A vendor's cross-account role is safe only if your trust policy demands an exact external ID, the vendor's backend generates and enforces it per tenant, and your reviews catch drift and offboard the role.

Identity & access · Amazon Web Services · 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

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

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

Pin third-party GitHub Actions and limit what they can reach

A tag can be moved under your workflow overnight. Pin every action to a commit SHA, enforce it across the organization, and cut the token and secret access a malicious action would inherit.

Workload security · GitHub / OpenSSF / CISA · By Cloud Security Desk
Technical guideSource-based analysis

Move cloud logs to cheaper tiers without losing detection coverage

CloudWatch Infrequent Access, the Sentinel data lake and Cloud Logging exclusions all cut ingestion cost by removing real-time detection hooks. Place each source by the rules that read it, then prove the replacements fire.

Detection & response · AWS / Microsoft Azure / Google Cloud · By Cloud Security Desk