NIST CSF 2.0 Framework

Detect (DE): Finding Attacks and Anomalies in Time

Continuous monitoring and adverse event analysis

8 min read
CTO, Security Engineer, IT Director
Updated 11/18/2026
Intermediate
NIST CSF 2.0DetectMonitoringCloudTrail

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

CodeCategoryIn plain English
DE.CMContinuous MonitoringAssets are monitored for anomalies, indicators of compromise and other adverse events
DE.AEAdverse Event AnalysisAnomalies 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

Medium
1–2 hours
Platform team

Alerts on CloudTrail or GuardDuty configuration changes

Easy
1 hour
Security lead

Alerts on new access keys, policy attachments, trust changes and root use

Medium
2 hours
Security lead

Data events on buckets holding sensitive data

Medium
1 hour
Data owner

Managed threat detection (for example GuardDuty) enabled in every region

Easy
1 hour
Platform team

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

NIST CSF 2.0
DE.CM
Continuous Monitoring
NIST CSF 2.0
DE.AE
Adverse Event Analysis
MITRE ATT&CK
T1685.002
Disable or Modify Cloud Log

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. 1.
  2. 2.
    Creating a trail for an organization

    AWS guidance for organization-wide logging

  3. 3.
    GuardDuty finding types

    Managed threat detection on AWS

Free, private checklist with prioritized recommendations. Runs in your browser.

Check your AWS logging readiness

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain