Security

Microsoft Sentinel UEBA Expands AWS Detection

3 min read

Summary

Microsoft Sentinel UEBA now adds richer behavioral analytics for AWS CloudTrail data, giving security teams built-in context like first-time geography, uncommon ISP, unusual actions, and abnormal operation volume. The update helps defenders detect suspicious AWS activity faster and reduces the need for complex KQL baselines and manual enrichment.

Need help with Security?Talk to an Expert

Introduction

Microsoft is expanding Microsoft Sentinel UEBA to strengthen AWS threat detection with richer behavioral analytics. For security operations teams managing hybrid and multi-cloud environments, this matters because AWS CloudTrail events now arrive with built-in context that can speed up investigations and improve detection quality.

Instead of relying on complex KQL queries, static thresholds, or manually maintained baselines, defenders can use precomputed UEBA insights to identify suspicious behavior in AWS activity more quickly.

What’s new in Microsoft Sentinel UEBA for AWS

Microsoft has added broader UEBA support across multi-cloud and identity data sources, including AWS, GCP, Okta, and more authentication logs. For AWS specifically, the key enhancements include:

  • More AWS behavioral enrichments for CloudTrail events at ingestion time
  • Binary insights such as:
    • First-time geography
    • Uncommon ISP
    • Unusual action
    • Abnormal operation volume
  • BehaviorAnalytics table support for AWS activity, exposing user, device, and activity insights
  • Anomalies table with six built-in AWS anomaly detections from Microsoft’s machine learning models
  • Defender portal integration for surfacing UEBA anomalies in user entity pages and incident graphs

Microsoft refers to this approach as binary feature stacking, where analysts combine simple true/false behavioral indicators to quickly spot attacker activity that may otherwise blend into normal AWS operations.

Why this matters for security teams

AWS investigations often depend on raw CloudTrail logs and custom logic to determine whether behavior is actually suspicious. That process can be time-consuming and expensive, especially in fast-changing cloud environments.

With Sentinel UEBA, administrators and analysts get:

  • Faster triage of AWS alerts
  • Less reliance on manually engineered KQL baselines
  • Better context for both human and non-human identities
  • More consistent anomaly detection across hybrid and multi-cloud estates

The update is especially useful for SOC teams that want to reduce alert fatigue while improving visibility into risky AWS actions such as unusual logons, IAM privilege changes, or previously unseen user agents.

Key implementation details

The AWS behavioral context appears in two main tables:

BehaviorAnalytics

This is the main investigation surface for UEBA-enriched AWS activity. It includes fields such as EventSource, ActivityType, and ActionType, plus dynamic insight fields like UserInsights, DeviceInsights, and ActivityInsights.

Anomalies

This table contains Microsoft’s pre-trained anomaly detections for AWS. Records include:

  • MITRE ATT&CK mappings
  • AnomalyScore
  • AnomalyReasons
  • Related behavioral enrichments

What IT and security admins should do next

  • Review current AWS CloudTrail detections in Sentinel
  • Identify analytics rules that rely on heavy baseline logic
  • Test UEBA enrichments in the BehaviorAnalytics and Anomalies tables
  • Use Defender portal hunting workflows to investigate user anomalies faster
  • Update SOC playbooks to take advantage of precomputed AWS behavioral context

For organizations securing AWS alongside Microsoft environments, this update can simplify detection engineering and improve response efficiency.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Microsoft SentinelUEBAAWSCloudTrailthreat detection

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.