Skip to content
Cloud Security DeskSearch
Menu

Research topic

Detection & response

A detection is only as complete as its evidence path.

38 publications

Practical analysis of cloud telemetry, detection coverage, investigation quality, and recovery readiness.

View every topic

From the desk

38 publications
Technical guide · August 28, 2026 · Source-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.

Technical guide · August 28, 2026 · Source-based analysis

What cloud snapshots cannot preserve

Separate live execution, persisted disk and provider records before an authorized containment decision destroys evidence that a snapshot cannot recover.

Technical guide · August 28, 2026 · Source-based analysis

Testing Sigma detections before a backend change

Keep rule structure, field transformations, query conversion and event matching as separate checks when changing a Sigma detection backend.

Technical guide · August 28, 2026 · Source-based analysis

Cloud incident severity needs a service impact model

Connect incident priority to service consequences, scope and time criticality while preserving evidence confidence and the authority to revise the decision.

Technical guide · August 28, 2026 · Source-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.

Technical guide · August 28, 2026 · Source-based analysis

Cloud detection coverage after the ATT&CK data model change

Connect current ATT&CK strategies and analytics to available events, implemented rules and test evidence, while keeping taxonomy counts separate from protection.

Technical guide · Published August 28, 2026 · Source-based analysisSeries August 2, 2026

Build an Azure change record that survives the portal window

Activity Log records and resource logs answer different questions. Preserve the operation outcome, resource context and export scope needed for a later investigation.

Technical guide · Published August 28, 2026 · Source-based analysisSeries June 23, 2026

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.

Research note · Published August 28, 2026 · Source-based analysisSeries May 14, 2026

Find the Google audit logs missing from your evidence window

Audit category, inherited configuration, destination and reader permissions all affect what an investigator can retrieve. Retention is only one part of the record.

Technical guide · Published August 28, 2026 · Source-based analysisSeries April 4, 2026

Investigate an Entra application through grants and sign-ins

A successful service-principal sign-in is one event in a larger sequence. Connect it to credential changes, permission grants and the resource involved.

Technical guide · Published August 28, 2026 · Source-based analysisSeries February 23, 2026

Verify the CloudTrail files behind an incident timeline

Digest delivery and successful validation are different evidence states. Preserve the files, metadata and validation result needed to distinguish them.

Technical guide · Published August 28, 2026 · Source-based analysisSeries January 14, 2026

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.

Visual brief · August 7, 2026 · Illustrative analysis

Cloud logs that never reach the SIEM

A dashboard can be healthy while the evidence behind it is incomplete. Coverage needs to be tested from event creation to searchable record.

Field note · July 21, 2026 · Illustrative analysis

Five Kubernetes events your cloud trail will not explain

Cloud control-plane logs tell you who changed the cluster. They do not fully explain what happened inside it.