Skip to content
Cloud Security DeskSearch
Menu

Evidence search

Search

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

Results for “key”

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

Prepare Azure automation for mandatory MFA on resource management

Azure now requires MFA for user accounts that write through Resource Manager. Find the scripts and pipelines that still sign in as people and move each one to a managed identity or federated credential.

Identity & access · Microsoft Azure / Microsoft Entra / GitHub / Azure DevOps / HashiCorp Terraform · By Cloud Security Desk
Technical guideSource-based analysis

Stop S3 ransomware that encrypts objects with customer-provided keys

SSE-C ransomware rewrites S3 objects under a key only the attacker holds. AWS now blocks SSE-C by default on most buckets; this guide covers what that default misses and the controls that close the gap.

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

Investigate a CI supply chain compromise from workflow logs to rotated secrets

When an action or package in your pipeline turns out to be malicious, scope the response by exposure window and by what each affected job could reach, then revoke together and hunt for use.

Detection & response · GitHub / AWS / npm · 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

Build an inventory of non-human identities across cloud accounts

Find every service account, service principal, role and key across AWS, Entra and Google Cloud, then record the owner, credential type, privilege and last use that turn a list into decisions.

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

Encrypt Kubernetes Secrets at rest with a KMS v2 provider

KMS v2 keeps etcd copies and backups unreadable without an external key, but it does not stop API readers. Configure it, compare what EKS, AKS and GKE already do, and finish key rotations with a rewrite.

Workload security · Kubernetes / Amazon EKS / AWS KMS / Azure Kubernetes Service / Azure Key Vault / Google Kubernetes Engine / Cloud KMS · 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

Normalize cloud security logs with OCSF before writing detections

OCSF puts CloudTrail, Azure Activity Log and Google audit records into the same API Activity fields. Detections still depend on the mapping, the schema version and provider semantics that normalization does not erase.

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

Build a cryptographic inventory for the post-quantum transition

Record where public-key cryptography protects long-lived data and which library, service or vendor must change it. Then rank entries by function and data lifetime, not by how many RSA keys a scanner found.

Workload security · NIST / CISA / Office of Management and Budget / Amazon Web Services / Google Cloud / Microsoft Azure · By Cloud Security Desk
Technical guideSource-based analysis

Choose a multi-region database consistency model before you need failover

The replication model decides which writes survive a Region failure. Compare asynchronous and quorum options in DynamoDB, Aurora, Spanner and Cosmos DB by recovery point, write latency and the reconciliation each one leaves you.

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

Scan uploaded files for malware before your application trusts them

Hold every upload where nothing can read it, promote only files with a clean verdict, and decide in advance what happens to the files GuardDuty, Defender or a ClamAV deployment cannot scan.

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

Back up a Kubernetes cluster so workloads can actually be restored

A Kubernetes backup has to carry definitions, Secrets and volume data, and the restore depends on identity, keys and images it never held. Plan the layers, the restore order and the checks that prove recovery.

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

Defend cloud admin accounts against help desk social engineering

Attackers who talk a help desk into resetting MFA inherit every cloud console behind single sign-on. Verify callers properly, shrink what a reset hands over, and alert on the events it leaves.

Detection & response · Microsoft Entra / Okta / Amazon Web Services / CISA / Mandiant · By Cloud Security Desk
Technical guideSource-based analysis

Limit what Google Cloud principals can reach with principal access boundaries

Allow and deny policies sit on resources. A principal access boundary travels with the identity and limits which projects, folders and organizations it may touch, even where someone else granted it a role.

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

Give AI agents their own identity instead of borrowed user tokens

An agent that replays a user's token is invisible in logs and cannot be revoked on its own. Give it a principal, delegate narrowly through token exchange, and use what Entra, AgentCore and Google now provide.

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

Prepare a cloud exit strategy that satisfies DORA

DORA requires a tested exit plan for every cloud service that supports a critical or important function. This guide turns that duty into dependency maps, measured data exports, staged tests and register entries that agree.

Resilience · European Commission / European Supervisory Authorities / European Central Bank / Amazon Web Services / Google Cloud / Microsoft Azure · By Cloud Security Desk
Technical guideSource-based analysis

Protect and recover your AWS root account

Protect AWS root access with MFA, current recovery contacts, separate daily administration, and a clear plan for Organizations member accounts.

Identity & access · AWS · By Cloud Security Desk