Detect (DE): Finding Attacks and Anomalies in Time
Continuous monitoring and adverse event analysis
TL;DR (for busy owners)
- What it is: Detect (DE) means monitoring assets for signs of attack and analyzing unusual events to decide whether something is an incident.
- Why it matters: The longer an intruder goes unnoticed, the more they can reach. In cloud, the audit trail is also the main evidence for deciding what happened and what to tell customers.
- Quick action: Confirm that CloudTrail records every account and region, and that someone is alerted if it is turned off.
The two Detect categories
| Code | Category | In plain English |
|---|---|---|
| DE.CM | Continuous Monitoring | Assets are monitored for anomalies, indicators of compromise and other adverse events |
| DE.AE | Adverse Event Analysis | Anomalies and indicators are analyzed to understand what is happening |
How attackers avoid detection
An attacker with administrator access stops or narrows CloudTrail logging before acting, or works in a region nobody watches. If logs live in the same account, they may delete them too. The CloudTrail impairment scenario shows how organization-level logging and guardrails prevent this.
What to log and watch
Cloud monitoring essentials
Organization-wide, multi-region CloudTrail delivered to a separate log-archive account
Alerts on CloudTrail or GuardDuty configuration changes
Alerts on new access keys, policy attachments, trust changes and root use
Data events on buckets holding sensitive data
Managed threat detection (for example GuardDuty) enabled in every region
Fast checks (15–30 minutes)
Detect quick assessment
- Audit logging covers every account and region, including unused ones (DE.CM)
- Ordinary account administrators cannot stop or modify the audit trail (DE.CM)
- High-risk identity changes generate an alert that reaches a named owner (DE.CM)
- There is a documented way to triage an alert and decide whether it is an incident (DE.AE)
- Logs are retained long enough to investigate an incident discovered weeks later (DE.AE)
Map to frameworks
NIST CSF 2.0 Detect categories and related ATT&CK guidance
Where Securitain fits
Securitain's current product focuses on identity, access and resource-policy configuration; it does not monitor CloudTrail activity or replace a detection service. It can show which identities hold permissions to change logging or detection configuration — useful context when deciding who must be prevented from doing so.
Next steps
Coverage, protection, ownership
Make sure logging covers everything, cannot be switched off by ordinary administrators, and that every alert has an owner. The free Cloud Logging Readiness Checklist turns this into a prioritized list.
Sources & References
- 1.The NIST Cybersecurity Framework (CSF) 2.0 — NIST CSWP 29
Official framework text
- 2.Creating a trail for an organization
AWS guidance for organization-wide logging
- 3.GuardDuty finding types
Managed threat detection on AWS
Free, private checklist with prioritized recommendations. Runs in your browser.
Check your AWS logging readiness