< ciso
brief />
Tag Banner

All news with #aws guardduty tag

39 articles

How AWS Security Incident Response Triages Your Findings

🛡️ AWS Security Incident Response continuously triages threat findings from Amazon GuardDuty and AWS Security Hub CSPM, yet most of that work never surfaces as a case. A new AWS post explains what happens to each finding, from ingestion to archiving or escalation. It also shows how to verify triage through the Proactive response dashboard and the monthly report. Across customers, fewer than 1 percent of findings result in an escalation.
read more →

Customize GuardDuty to Reduce Alert Fatigue

🔒 Amazon GuardDuty continuously analyzes AWS data sources like CloudTrail, VPC Flow Logs, and DNS logs to surface findings for suspicious activity. The blog explains new customization features—Custom Detection Rules, entity lists, filters, and suppression rules—that help tailor detections to environment-specific behavior and reduce noisy alerts. It also covers dry run evaluation, organization-wide management, and GuardDuty Investigation for automated context and faster triage.
read more →

GuardDuty Runtime optional detection rules now available

🛡️ Amazon GuardDuty now supports optional Runtime Monitoring detection rules covering process, file, and network activity. You can enable over 50 rules across EC2, EKS, and ECS (including Fargate) that map to 13 finding types and MITRE ATT&CK® tactics such as persistence and privilege escalation. Four new finding types are introduced and rules can be enabled in dry-run mode to validate detections before going live.
read more →

GuardDuty adds five indicators to improve detections

🔒 Amazon GuardDuty Extended Threat Detection now attaches five new indicator types — MALICIOUS_PACKAGE, MISCONFIGURATION, REACHABILITY, SENSITIVE_DATA, and VULNERABILITY — to correlated attack-sequence findings. These indicators are sourced from Amazon Inspector, Amazon VPC Reachability Analyzer, Amazon Macie, and AWS Security Hub, and appear in the Indicators tab and GetFindings JSON. The added context helps promote weak runtime signals into higher-confidence CRITICAL findings for Amazon EC2, ECS, and EKS workloads, improving prioritization and reducing noise.
read more →

GuardDuty expands RDS protection to detect exfiltration

🔒 Amazon GuardDuty expands RDS Protection to detect data exfiltration and destruction for Amazon Aurora PostgreSQL and Amazon RDS for PostgreSQL. This new ML-based RDS Protection for data activity monitors query patterns without agents or configuration changes, using anomaly detection and threat intelligence. It can be enabled as an add-on to existing RDS Protection for login activity across an organization via console, APIs, SDKs, CLI, or CloudFormation, with a 30-day trial available.
read more →

AWS Security Hub Adds GuardDuty Runtime Monitoring

🔔 AWS has integrated Amazon GuardDuty Runtime Monitoring into the AWS Security Hub Threat Analytics plan. This runtime capability inspects OS, network, and file activity to detect threats like container escapes, privilege escalation, and cryptomining across Amazon EC2, Amazon EKS, and Amazon ECS on AWS Fargate. Billing for Runtime Monitoring is now consolidated under Security Hub as a single usage type, eliminating separate GuardDuty Runtime Monitoring charges for accounts and regions with Security Hub enabled. Detection behavior, finding types, and GuardDuty agents remain unchanged, and no reconfiguration is required; free-trial terms for Threat Analytics and Security Hub Essentials remain separate.
read more →

GuardDuty organization enablement policies now available

🔒 Amazon GuardDuty now supports AWS Organizations declarative policies to centrally enable threat detection across all accounts and Regions. Using a centrally managed organization policy, you can apply a consistent GuardDuty enablement configuration that automatically extends to existing accounts and to new accounts as they join. The policy allows a default baseline across all Regions where GuardDuty is available, with optional per-Region overrides, and prevents overrides through the GuardDuty console or API. This feature is available in all AWS commercial Regions and AWS GovCloud (US) Regions.
read more →

Amazon GuardDuty adds opt‑in detection rules

🛡️ Amazon GuardDuty now provides Custom Detection Rules, a library of 35 prebuilt, opt‑in rules for CloudTrail management events that produce 26 unique finding types mapped to 10 MITRE ATT&CK® tactics. These rules extend threat coverage without requiring additional log ingestion, normalization, or storage. Administrators can enable rules selectively where activity is unexpected and test in dry‑run mode via the GuardDuty console or API. The feature is available in all AWS commercial Regions and AWS GovCloud (US).
read more →

Agentic Security: Detection and Response at Machine Speed

🔒 AWS outlines how the rise of autonomous AI agents demands a shift in security posture from event-driven to continuous, machine-speed detection and response. The post summarizes a collaborative chapter with the SANS Institute in the 2026 Cloud Security Exchange eBook, emphasizing that existing security principles—identity governance, least privilege, and defense in depth—must be adapted for probabilistic, autonomous workloads. AWS highlights built-in platform services like Amazon GuardDuty, Amazon Inspector, and AWS Security Hub as components to extend trusted controls for agentic AI adoption.
read more →

AWS adds AI toolkit and expanded Automated Security Response

🔒 Today AWS announced four new capabilities for Automated Security Response on AWS (ASR). Customers can use an AI-driven Toolkit to generate custom remediations with built-in safety guardrails. ASR now supports automatic remediation of findings from Amazon Inspector, Amazon GuardDuty, and Amazon Macie, and offers an enhanced web console to centrally configure remediations. New multi-channel notification adapters for Email, Slack, Jira, and ServiceNow include severity filtering and deadline enforcement.
read more →

Detecting Multi‑Stage Attacks on AWS with Correlation

🔍 This post explains how correlating signals across AWS services and your business context reveals multi-stage attacks that single alerts miss. It outlines five attack phases and the three primary log sources—CloudTrail, VPC Flow Logs, and Route 53 Resolver logs—used to surface each phase. The guide emphasizes enabling and tuning AWS detection services such as Amazon GuardDuty, then layering custom queries that encode your environment-specific knowledge. It includes CloudWatch Logs Insights queries and operational guidance for thresholds, multi-account setups, and automating detection pipelines.
read more →

Amazon GuardDuty Investigation Agent Public Preview

🔍 The Amazon GuardDuty investigation agent, now in public preview, delivers on-demand, AI-assisted assessments of GuardDuty findings across AWS accounts and Regions. It returns structured outputs including risk level, confidence scores, MITRE ATT&CK mapping, resource context, and prioritized remediation actions. Accessible via AWS Console, CLI, APIs, SDKs, and the AWS MCP server, it supports natural-language triggers and integrates into existing security pipelines to reduce investigation time from hours to minutes.
read more →

Amazon GuardDuty adds AI Protection for AWS AI

🛡️ Amazon GuardDuty introduces AI Protection to extend threat detection to AWS AI services such as Amazon Bedrock and Amazon SageMaker. The feature continuously monitors AI workloads for threats like anomalous invocations, cost harvesting attacks, and prompt injection, using CloudTrail management and data events to surface suspicious activity. Findings integrate with AWS Security Hub for centralized triage and can be enabled per account or centrally via AWS Organizations, with a 30-day trial available for GuardDuty customers.
read more →

GuardDuty Runtime adds sensitive file modification detection

🛡️ Amazon GuardDuty Runtime Monitoring now includes three new threat detections to alert teams when sensitive files are modified on Amazon EC2 instances and container workloads on Amazon EKS and Amazon ECS. These findings monitor critical system files such as configuration files, authentication settings, and system logs to surface post-compromise activity. The detections map to MITRE ATT&CK® tactics and provide remediation guidance while using correlation analysis to reduce false positives. The capability is available to customers with GuardDuty Runtime Monitoring enabled, with a 30-day trial for new users.
read more →

AI-powered investigations preview for Amazon GuardDuty

🛡️ AWS previewed AI-powered investigations in Amazon GuardDuty to automate analysis of findings and reduce manual investigation time. The capability uses knowledge graphs and threat intelligence to examine 90 days of related activity, affected resources, and indicators, delivering disposition assessments with confidence scores, MITRE ATT&CK classifications, evidence, and remediation recommendations. Available in preview in 10 regions and accessible via the GuardDuty console, CLI, API, or AWS' MCP Server.
read more →

Accelerating AWS security investigations with Kiro CLI

🔐 This post shows how Kiro CLI, an AI-powered command line assistant, speeds AWS security investigations by proposing, explaining, and optionally executing AWS CLI commands while documenting each step. It demonstrates a GuardDuty-driven investigation following the AWS Security Incident Response Guide: triage, EC2 and IAM assessment, CloudTrail analysis, containment, and remediation. The walkthrough highlights benefits like faster triage, automated CloudTrail queries, and guided remediation, while advising human validation and forensic preservation.
read more →

Operationalizing AWS security: a maturity roadmap

🔒 This post outlines a practical, phased maturity roadmap for organizations that have enabled AWS Security Hub and Amazon GuardDuty. It emphasizes moving from enabled tooling to operational security practices by assessing current state, tuning signal quality, routing findings, automating safe remediations, and establishing a recurring operational cadence. Each phase includes goals, timelines, deliverables, and decision criteria to measure progress and reduce alert fatigue.
read more →

Introducing the AWS Customer Incident Response Team

🔒 The AWS Customer Incident Response Team (CIRT) is a 24/7 global team that helps customers during active security events affecting the customer side of the Shared Responsibility Model. The team analyzes AWS service logs and the control plane using sources like AWS CloudTrail, VPC Flow Logs, and GuardDuty, provides triage and containment guidance, and recommends follow-up actions. AWS also publishes tools, workshops, and the Threat Technique Catalog for AWS (TTC) to help customers prepare and detect recurring tactics and techniques.
read more →

GuardDuty malware scanning for S3 continuous backups

🛡️ Amazon GuardDuty Malware Protection for AWS Backup now supports Amazon S3 continuous backups, enabling malware scanning across your continuous backup timeline. You can enable full or incremental scans within your backup plan and run on-demand scans up to any restorable point in time. The new GetPITRMalwareScanResults API lets you query scan status at a specific point in time to confirm a clean recovery point. Support is available in all Regions where GuardDuty Malware Protection for AWS Backup is offered, and you can enable it via the AWS Backup console, API, or CLI.
read more →

Automating identity lifecycle with AWS Directory APIs

🔒 AWS Managed Microsoft AD now supports CRUD operations on users and groups through the Directory Service Data APIs, accessible via the AWS CLI, APIs, and Management Console. This enables automation of identity lifecycle management and tighter security controls by integrating with services like Amazon GuardDuty, AWS Step Functions, and Amazon EventBridge. The blog demonstrates a practical workflow that detects unusual AD user behavior and triggers automated remediation such as disabling accounts and notifying stakeholders.
read more →