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

Workload federation across clouds needs separate trust decisions

Cross-cloud federation adds trust decisions, not a portable permission system. Map each credential and resource grant before moving a runtime workload.

Identity & access · AWS / Google Cloud / Microsoft Entra · By Cloud Security Desk
Technical guideSource-based analysis

A defensible cloud patch queue starts with exploitation evidence

Join exploitation evidence to affected assets, exposure, ownership and verified remediation without turning CVSS, EPSS or a catalog entry into a complete risk score.

Detection & response · CISA / NIST / FIRST · By Cloud Security Desk
Technical guideSource-based analysis

Choosing isolation for a Kubernetes tenant

A namespace, a virtual control plane and a sandboxed runtime protect different boundaries. Start with tenant authority before choosing the cluster architecture.

Workload security · Kubernetes / gVisor / Kata Containers · By Cloud Security Desk
Technical guideSource-based analysis

Recovery objectives that match the cloud service

Define the business function, outage clock, recoverable data and dependency assumptions before choosing a cloud disaster-recovery architecture.

Resilience · AWS / Azure / Google Cloud / NIST · By Cloud Security Desk
Technical guideSource-based analysis

Entra emergency access that survives normal sign-in failure

A second administrator account does not prove an independent recovery path. Test the credential, workstation, policy and alert dependencies together.

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

Design an outbound fetch service that contains SSRF

A URL check is only the first decision. The fetch worker must contact the approved destination, recheck redirects and limit the authority of every request.

Workload security · OWASP / IANA · By Cloud Security Desk
Technical guideSource-based analysis

Short SSH certificates still need explicit access boundaries

An SSH certificate supplies bounded identity claims. The issuer, server, client and incident operator still make separate access decisions.

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

Certificate renewal under shorter validity limits

Use the public TLS issuance schedule to review authorization, renewal, deployment and independent verification of the certificate an endpoint actually serves.

Resilience · CA/Browser Forum / Let's Encrypt / AWS · By Cloud Security Desk
Technical guideSource-based analysis

The telemetry collector is part of the evidence boundary

Review sender identity, tenant routing, processing and export as separate trust boundaries before treating collected telemetry as dependable evidence.

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

Prepare cloud workloads for hybrid post-quantum TLS

Hybrid support in a library is not proof that every TLS hop uses it. Verify negotiation, compatibility and fallback while keeping certificate authentication separate.

Workload security · IETF / NIST / OpenSSL / Cloudflare · By Cloud Security Desk
Technical guideSource-based analysis

The bottlenecks that shape a cloud DDoS response

Distinguish bandwidth, packet processing, connection state and application work before choosing a DDoS response or assuming the whole service path is protected.

Resilience · AWS / Azure / Google Cloud / Cloudflare · By Cloud Security Desk
Technical guideSource-based analysis

Model output needs its own trust boundary

A model can produce valid JSON containing an unauthorized identifier, an unsafe link or text that a renderer interprets as code. The application consuming that output owns the next trust decision.

AI systems · OpenAI · 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
Technical guideSource-based analysis

Map every connection beyond the private AI endpoint

Trace inference, retrieval, tools, administration, and telemetry separately before describing an AI application as private.

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

Prove Azure Storage private access from DNS to authorization

Check the exact storage subresource, resolve its normal hostname from the application, and test public access and data permissions as separate boundaries.

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

Measure GuardDuty runtime coverage from the resource outward

An enabled protection plan does not describe the health of every workload. Review supported resources, agents, connectivity and the denominator behind coverage.

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

Verify container provenance before admitting a pinned image

Use the digest to identify the artifact, then check who signed it, which builder produced it, and which evidence survived promotion into the deployment registry.

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

Review the authority behind every Entra app consent

The permission name is only part of the decision. Review the access mode, resource scope, consenting authority and people who can change the application.

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

Treat model downloads as software supply chain changes

Review weights, custom code, dependencies, and runtime authority as separate decisions before promoting a downloaded model into a trusted environment.

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

Require EC2 IMDSv2 without breaking container credentials

Separate metadata token requirements from response hop limits, then verify both existing instances and future launches before declaring the migration complete.

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

Test Kubernetes egress policies beyond a successful DNS lookup

Separate DNS resolution, source egress, destination ingress, and application identity when testing Kubernetes network isolation.

Workload security · Kubernetes / Cilium · 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

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