Research topic
Detection & response
A detection is only as complete as its evidence path.
Practical analysis of cloud telemetry, detection coverage, investigation quality, and recovery readiness.
View every topicFrom the desk
38 publicationsMove Microsoft Sentinel to the Defender portal without breaking automation
Onboarding a Sentinel workspace to the Defender portal changes incident providers, grouping, fields and automation timing with no documented error. Inventory what depends on them, rehearse safely and cut over before March 31, 2027.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Choose and verify CloudWatch Logs retention
Choose CloudWatch Logs retention from supported values, verify the saved setting, and account for delayed deletion, archives, and log-group ownership.
Make CloudWatch alarms handle missing data correctly
Choose how CloudWatch alarms treat missing data, understand evaluation surprises, test notifications, and preserve useful alarm evidence.
Get an alert when Google Cloud project access changes
Build a Google Cloud log-based alert for project IAM changes, verify the filter and notification channel, and understand incident limits.
Triage a Google Cloud Security Command Center finding
Review a Security Command Center finding, choose repair or a documented exception, and distinguish resource verification from muting and closure.
Get an Azure alert when a role assignment changes
Detect successful RBAC changes and test alert delivery without expanding a production role.
Find why an Azure VM cannot reach a service
Use a specific source and destination with Network Watcher and separate network reachability from app health.
Keep Kubernetes audit records useful without logging secrets
Design a question-led Kubernetes audit policy with explicit body limits, rule precedence, lifecycle stages and provider-specific acceptance checks.
Read VPC Flow Logs without overclaiming network evidence
Interpret aggregation, address translation, skipped records and delivery clocks before turning a VPC flow record into an incident conclusion.
Catch late security events without replaying every alert
Separate event time, ingestion time and execution health so delayed records can be evaluated without turning every broader lookback into a replay.
Find the Purview audit history your investigation can still retrieve
Resolve Purview audit availability at the record level by separating actor eligibility, retention policy, collection status, investigator scope and export limits.
Investigate denied access at an AWS VPC endpoint
Use CloudTrail network activity evidence to distinguish endpoint-policy violations from routing failures and downstream authorization problems.
Keep GitHub audit streaming continuous across maintenance
Plan audit-stream maintenance around native history, pause buffers, receiver acceptance and duplicate-aware evidence receipts.
Questions answered
What does Cloud Security Desk cover under Detection & response?
Practical analysis of cloud telemetry, detection coverage, investigation quality, and recovery readiness.
Supporting context
A detection is only as complete as its evidence path.
Why does the detection & response topic matter to cloud security?
A detection is only as complete as its evidence path. This topic applies that principle to practical control evidence and review decisions.
Which control questions belong to Detection & response?
Research belongs here when its central evidence, failure mode, or operational decision falls within the detection & response boundary described on this page.
How many detection & response publications are available?
This page currently lists 38 publications assigned to Detection & response.
How should readers use the Detection & response research?
Start with the publication closest to the control, platform, or evidence gap under review, then follow its findings, limitations, numbered sources, related work, and downloadable material.
Can detection & response overlap other research topics?
Yes. A publication can appear under several topics when one evidence path crosses multiple control boundaries; each publication page identifies its complete scope.
Supporting context